-
Notifications
You must be signed in to change notification settings - Fork 320
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
Cn matrix v3 #640
Cn matrix v3 #640
Conversation
Some things I remember from our last discussion. These are things that need to be done, I'm not assigning who will work on them.
|
Just to note, the second assignment from Erik's comments can be done by turning off "is_outmatrix" in clm_varctl.F90 (is_outmatrix = .false.) |
@negin513 - I am happy to leave the review of this to you and Erik. |
We discussed this today, and the new plan is the following:
|
Added a simple 3-month restart test with matrix on and it passes... PASS ERS_D_Lm3.f09_g17.I1850Clm50BgcCrop.cheyenne_intel.clm-ciso_monthly_matrixcn |
New round of testing
so I have submitted the test with on izumi: |
@ekluzek @samsrabin Do we envision keeping the setting as .true. for matrixcn or does it possibly not matter? |
Continuing the thread: |
That... is really surprising. |
This is the test directory, though note that I last ran the test with |
Could you resubmit it so I see what the failure looks like? |
The failure is still available to look at in the earlier .log files: Same location under /run directory. This is what you will find in the cesm .log file:
|
Really, really weird. For now, try changing <hillslope_fsat_equals_zero >.true.</hillslope_fsat_equals_zero> to <hillslope_fsat_equals_zero use_hillslope=".true.">.true.</hillslope_fsat_equals_zero> |
Relax tolerance for truncating small snocan values in CanopyFluxes See the PR ESCOMP#2457 for details.
on derecho
OK on izumi |
slevis resolved conflicts: bld/unit_testers/build-namelist_test.pl
derecho testing OK testing on derecho and izumi |
Anyone following the cnmatrix PR (#640), feel free to comment on the contents of the ChangeLog. System testing is in progress and is unlikely to finish soon enough for me to merge this PR before Friday. |
Description of changes
Specific notes
Contributors other than yourself, if any:
Yuanyuan Huang, Zhenggang Du and Yiqi Luo from Professor Yiqi Luo's EcoLab at Northern Arizona University
CTSM Issues Fixed (include github issue #):
Fixes #903
Fixes #2450
Fixes #2621
Are answers expected to change (and if so in what way)?
Answers should be generally the same but slightly changes. The slight changes of the answer is due to C pool size updating order change. Eg. Default model updates vegetation C pool size in three steps: 1) X = X + I + AphKph * X; 2) X = X + AgmKgm X; 3) X = X + AfiKfi X. The matrix model updates C pool size all at once: X = X + I + (AphKph + AgmKgm + AfiKfi) X. Because the AK*X is smaller than X by several magnitude at each time step, the difference in most cases are small.
Any User Interface Changes (namelist or namelist defaults changes)?
Add four switches:
Testing performed, if any:
(List what testing you did to show your changes worked as expected)
Scientific tests running global 4x5 resolution (f45_g37), history simulation (IHistClm50Bgc) for 150 years including 2 resubmits at every 50 years.
Results from default code (four switches .false.) and matrix code (use_matrxcn, use_soil_matrixcn and is_outmatrix are all .true., isspinup is .false.) do not show significant difference.
(This can be manual testing or running of the different test suites)
Differences between default code and matrix code are manually tested.
(Documentation on system testing is here: https://github.com/ESCOMP/ctsm/wiki/System-Testing-Guide)
We have used create_test for system testing.
(aux_clm on cheyenne for gnu/pgi and hobart for gnu/pgi/nag is the standard for tags on master)
We used create_test with aux_clm. the cime folder is detached from cime5.7.5