-
Notifications
You must be signed in to change notification settings - Fork 261
Output precision to statistics file for time and Time Step Size is now 12 #830
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
Conversation
|
These changes are almost certainly going to break every single one of our 310 tests. Let's find out! |
|
Oh pooh! I assume this is because the diff script is comparing digits and the changes produce an additional n digits, which causes the test to fail? |
|
Yes, that's the cause. (We do compare only up to a tolerance, but the relative difference here is larger than the tolerance we compare against :-( ) But you can download a patch file for the differences here: http://www.math.clemson.edu/~heister/aspect-logs/2b8e7463f9659ffea9e00c6b7807ca325be03beb/changes.diff . Just apply it and add the result as a second commit to your pull request. |
|
I assume /run-tests will start automatically? |
|
I guess so ... |
|
You also need to update the output from the PETSc tests (sorry there is no automated way to generate a patch file for that at the moment). |
|
How do I do that? I can see the four tests that failed at http://www.math.clemson.edu/~heister/aspect-logs/757a65550f4e59bac93405c0a90dd2f2e065e522/gccpetsc and the log files from the tests that failed http://www.math.clemson.edu/~heister/aspect-logs/757a65550f4e59bac93405c0a90dd2f2e065e522/gccpetsc but, as you obviously know, the diffs in that log file are incomplete:
Do I need to obtain the file
and the other three *.diff.failed files and create a patch file? If all of this is correct, then
I've read some documentation about creating patches in Git http://makandracards.com/makandra/2521-git-how-to-create-and-apply-patches[](url) However, I'm not sure I have the files I need to COMMIT from which I can generate the patch file. That's assuming I know what I'm doing, which is debatable! :-) |
|
There is no way to get access to the diffs or a patch file right now. I made a patch for you though. Can you please do |
|
Done! |
|
You broke nearly every test by changing the name of the RK2 in source/particle/integrator/rk_2.cc (from "rk2" to "RK2"). |
|
That was foolish of me. Rene warned me about this, but I failed to notice that the change was committed when I committed the change to 12 digit precision. My sincere apologies. Mea culpa ... |
|
On 04/25/2016 01:30 PM, Elbridge Gerry Puckett wrote:
Rule #1: Only one functional change per pull request or commit! :-) |
|
Got it! |
These changes are in response to issue #824 opened 3 days ago by @bangerth and subsequent email correspondence between @bangerth and @egpuckett