-
Notifications
You must be signed in to change notification settings - Fork 38
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
Potential inconsistency of diagnostics generation after update DATA and version #86
Comments
So I am looking at your "After updates" and I am noticing some strange things in the logfile: If you poke through that, you will see that the only biomass variables that run are NBCD2000 and Thurner. If one of the others failed, it would have an entry in the logfile, like the NOAA emulated CO2 one, with details of the failure. In fact, most of your grey boxes don't seem to have run at all. This could mean that they are failing in a way that I do not log. Did you happen to capture the screen output? If none of these comments are help, let's jump on zoom tomorrow and figure this out quickly. |
Thank you for troubleshooting! Attached is the logfile i captured during the run. Most of the other grey boxes are caused by missing variables, I believe. The biomass case is particularly interesting. I notice that the two successful runs (NBCD2000 and Thurner) have the directory names unchanged between DATA updates. Not sure if it helps, but below are the before and after directory names of DATA.
Happy to schedule a zoom meeting if none of above is useful.. |
In the tests, ILAMB version is updated to v2.7 and DATA directory is updated with ilamb-fetch. This update does resolved #83, but I also noticed some inconsistencies.
Results:
Before updates
After updates
It looks like only a subset of Biomass results (2 out of 5) are showing up. And runoff, permafrost diagnostics are not shown.
And I did see name changes in directory structure in DATA, for instance: runoff directory is renamed as mrro, and sub folders of biomass are renamed, ect. Not sure if that is the cause. Pinging @nocollier , any insights are appreciated!
The text was updated successfully, but these errors were encountered: