Skip to content
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

Record compile-time parameters to restart files #14

Open
gnwong opened this issue Mar 2, 2020 · 1 comment
Open

Record compile-time parameters to restart files #14

gnwong opened this issue Mar 2, 2020 · 1 comment

Comments

@gnwong
Copy link
Contributor

gnwong commented Mar 2, 2020

During my tracer particle run (for the Ma-0.94 384x192x192), I noticed that the evolution seemed to differ from the original library run. It's possible that this is due to different versions of the code having been used to run the tracer particles and the original library run.

I started from restart_00000240.h5 and dumped for 1k M, but the different should be noticeable even in images before ~20M.

@bprather
Copy link
Contributor

This is impossible to track down at this point, and likely not that useful, since a number of (beneficial) changes have been made to how iharm3d applies floors since the library files were run originally.

However, the feature here would be recording the floor values and other compile-time parameters to restart files and checking them on load -- that would give an indication of when evolution is expected to be different or not.

@bprather bprather changed the title possibly inconsistent evolution after restart Record compile-time parameters to restart files Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants