-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Match with slightly unequal timestep times #94
Conversation
…st for across directions that should have been relative
Looks good, but for some reason the tests are failing... |
Yes the reason of test failing is the same as for PR #91 and maybe issue #92, which are all related to (pynbody/pynbody#503). It has to do with compatibility problems between numpy, cython versions when installing pynbody. I gave a go at isolating it in PR #91 but hadn't had the time to follow it up. |
Oh dear me... I wonder whether @SophiaNasr has any comment, since she managed to fix this bizarre numpy thing in her own installation? |
@Martin-Rey have you tried to pip upgrade cython, followed by numpy, and finally, pynbody? This fixed a problem I was having earlier. You can find the versions I updated to in my thread (which looks like it has been cross-referenced by you, so you may have already seen it) pynbody/pynbody#503 |
Thanks @SophiaNasr and @apontzen! I have done some mix and match of numpy and cython versions and come to the conclusion that it is a pretty inexplicable bug :)
The only difference I can think off is that both in the Tangos automated build and in @SophiaNasr use case, pynbody was installed via pip, rather than clone+python setup.py. |
The thing that I don’t understand is that downgrading cython doesn’t seem to help either, which contributes to making this truly baffling. |
Thanks for your assistance @SophiaNasr! @Martin-Rey if you merge the master branch into this one, travis should now pass... |
PR addressing issue #93
The fraction defining two timesteps as having the same time has been moved to the config file.
The missing factor in the "across" keyword to make the test relative rather than absolute has been added.
Feel free to comment
Martin