Scheduled Downtime
On Wednesday 09 March 2022 from 6am to 10am MT, the website will be down for maintenance

Changing history files affects runtime

aelkouk

ahmed elkouk
New Member
Hi Keith

I have this issue which may be related to the one you helped me with earlier (
branch_tags/PPE.n12_ctsm5.1.dev030 case runs indefinitely). The model works when I save a couple of variables but runs forever when saving all variables. Could you please check when you can.

I have setup the following case to demonstrate the problem: /glade/work/elkoukah/cases/PPEn12CTSM51_I2000Clm50Sp_nldas2_0.125SWUS_001.debug

The run finishes when you uncomment the two lines user_nl_clm. I appreciate your help, thanks so much!
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I'm not sure what is going on.
I cloned your case and the model ran for three days, writing out daily average history files, but it took 2 hours.
I did a one day run and the model finished successfully but that took about 1 hour.
I upped the processors (30 cores instead of 15) but that didn't help.
Even when running with the default history output (monthly average history files) the model ran very slowly.
The timing file indicates that the model is spending all of its time in "clm_drv_io" which is the section of code that finalizes and writes the history files.
Do you have code mods of your own in this branch_tags/PPE.n12_ctsm5.1.dev030 tag?
 

aelkouk

ahmed elkouk
New Member
Thank you very much for checking up this. No it is the original branch, I didn't do any code modifications.
Do you think the domain file has something to do with this? I have another case which is essentially a subset of that domain, and runs with no problems (/glade/work/elkoukah/cases/PPEn12CTSM51_I2000Clm50Sp_nldas2_0.125UCRB_001.eval).
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Maybe. I guess you could try substituting in your domain file and fsurdat from the eval case into the debug case and see if it is related to that.
 
Top