-
Notifications
You must be signed in to change notification settings - Fork 132
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
capture timing results #49
Comments
In order to post the timings to CDash, we can only have 1 timer logged. We can include the timer information for multiple timers elsewhere (although I'm not sure where). For example, http://my.cdash.org/viewTest.php?onlypassed&buildid=1338795 is what I have been working on today. I've been putting the 'Timer 1: Total' timer into the Time field for the *_run tests for smoke tests only. I could easily change to another timer, but we still have the issue of only a single timing being able to be posted to CDash. |
If we can only choose one, then the best one is TimeLoop. If that one is very different between runs, then we can look more closely at Dynamics, Column, etc. manually. |
I think this was addressed in #125 . The wiki is now showing timings for tests (https://github.com/CICE-Consortium/Test-Results/wiki/3eed537e29.conrad.intel.180418.000150). |
Cool, thank you. |
* Rearrange the calls in ice_dyn_evp.F90 and add some halo updates * Fix spaces
Record timing results as part of the testing procedure, or at least flag them if changes are substantial in comparison tests. Preferably include at least these:
Timer 2: TimeLoop
Timer 3: Dynamics
Timer 5: Column
The text was updated successfully, but these errors were encountered: