-
Notifications
You must be signed in to change notification settings - Fork 9
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
Another argweaver bug #25
Comments
May be worth posting this (and the argweaver_bug.sites file) to the ARGweaver github repo. |
NB. This causes the following error in the plots.py script:
This is raised as a ValueError on line 241. But we should probably carry on so that any such error doesn't doesn't kill the entire run. For later output, it doesn't matter if the AW run fails. The plots.py script should just omit a row if it can't find the right output files. |
Now hacked around by wrapping in a try-except block - if the error message contains ''src/argweaver/sample_thread.cpp:517", the exception is caught, logged, and the process continues. Otherwise the exception is re-raised and the process should stop. This should be enough to work around this specific bug until we can solve why ARGweaver is complaining. |
Reported at mdrasmus/argweaver#21, so closing |
Sounds good to me @hyanwong. Re the ArgWeaver bug, a possible cause might be differences between GCC and clang, and specifically wrt to default optimisations enabled. It might be worth hacking the makefile to set "CXX = clang++" on holly and seeing if problem persists. I doubt the problem is processor dependent, as all intel processors look very much the same these days, and IEEE float semantics takes nearly all the nastiness out of floats. |
This only fails on holly, though. It works OK on my laptop. Some sort of rounding / maths bug that is processor or C library dependent?
The text was updated successfully, but these errors were encountered: