Change history output

[hannay]

You need to do a branch run if you change the history output. You could keep the same name with the variable: 
BRNCH_RETAIN_CASENAME See info at: 
http://www.cesm.ucar.edu/models/cesm1.0/cesm/cesm_doc_1_0_6/x3128.html

 

[hannay]

You need to do a branch run if you change the history output. You could keep the same name with the variable: 
BRNCH_RETAIN_CASENAME See info at: 
http://www.cesm.ucar.edu/models/cesm1.0/cesm/cesm_doc_1_0_6/x3128.html

 

[hannay]

You need to do a branch run if you change the history output. You could keep the same name with the variable: 
BRNCH_RETAIN_CASENAME See info at: 
http://www.cesm.ucar.edu/models/cesm1.0/cesm/cesm_doc_1_0_6/x3128.html

 

[hannay]

You need to do a branch run if you change the history output. You could keep the same name with the variable: 
BRNCH_RETAIN_CASENAME See info at: 
http://www.cesm.ucar.edu/models/cesm1.0/cesm/cesm_doc_1_0_6/x3128.html

 

[hannay]

From user:

I have run CESM for 6 months without writing out history files to speed up the wall time.  Now, for July, I would like to start writing history files.I edited user_nl_cam to reflect this (using a user_nl_cam file which had worked previously), did a rebuild, and ran for one more month. All indications show that the model did run until 07-30 (restart files, etc).  However, the history files I had specified in user_nl_cam were not there. In an online search, I found that the method I executed is valid for POP and CICE, however, for CCSM4.0, one needs to do a branch run in order to change history file frequency.   Is this still true for CAM5? Thank you ahead for your attention to my question. Best regards,

 

[ckuo@lbl_gov]

Thank you,Cecile, for your quick reply.I should have specified that I am using CESM1.2.2, and followed instructions on branch runs for that version.The model run does not finish, running for only ~1 minute. The error reported in the cesm.log file is:"(shr_sys_abort) ERROR: (seq_infodata_Check) : invalid continue restart case name = feedback.B1850C5CN.trial2".  There are no typos in the case name listed.Is this referring to the following lines in env_run.xml?           This case does exist, and there is no typo.  The refcase folder is at the same directory hierarchy level as the branch case.Would you have other suggestions as to why I would be getting this error?Thank you,Kuo 

 

[ckuo@lbl_gov]

Thank you,Cecile, for your quick reply.I should have specified that I am using CESM1.2.2, and followed instructions on branch runs for that version.The model run does not finish, running for only ~1 minute. The error reported in the cesm.log file is:"(shr_sys_abort) ERROR: (seq_infodata_Check) : invalid continue restart case name = feedback.B1850C5CN.trial2".  There are no typos in the case name listed.Is this referring to the following lines in env_run.xml?           This case does exist, and there is no typo.  The refcase folder is at the same directory hierarchy level as the branch case.Would you have other suggestions as to why I would be getting this error?Thank you,Kuo 

 

[ckuo@lbl_gov]

Thank you,Cecile, for your quick reply.I should have specified that I am using CESM1.2.2, and followed instructions on branch runs for that version.The model run does not finish, running for only ~1 minute. The error reported in the cesm.log file is:"(shr_sys_abort) ERROR: (seq_infodata_Check) : invalid continue restart case name = feedback.B1850C5CN.trial2".  There are no typos in the case name listed.Is this referring to the following lines in env_run.xml?           This case does exist, and there is no typo.  The refcase folder is at the same directory hierarchy level as the branch case.Would you have other suggestions as to why I would be getting this error?Thank you,Kuo 

 

[ckuo@lbl_gov]

Thank you,Cecile, for your quick reply.I should have specified that I am using CESM1.2.2, and followed instructions on branch runs for that version.The model run does not finish, running for only ~1 minute. The error reported in the cesm.log file is:"(shr_sys_abort) ERROR: (seq_infodata_Check) : invalid continue restart case name = feedback.B1850C5CN.trial2".  There are no typos in the case name listed.Is this referring to the following lines in env_run.xml?           This case does exist, and there is no typo.  The refcase folder is at the same directory hierarchy level as the branch case.Would you have other suggestions as to why I would be getting this error?Thank you,Kuo 

 

[hannay]

I neer had that error but the fact it says: "invalid continue restart" makes me think that your run is not set as a branch run. How do you specify: env_run.xml:  
env_run.xml:  also, please check the variable CONTINUE_RUN :   


  

 

[hannay]

I neer had that error but the fact it says: "invalid continue restart" makes me think that your run is not set as a branch run. How do you specify: env_run.xml:  
env_run.xml:  also, please check the variable CONTINUE_RUN :   


  

 

[hannay]

I neer had that error but the fact it says: "invalid continue restart" makes me think that your run is not set as a branch run. How do you specify: env_run.xml:  
env_run.xml:  also, please check the variable CONTINUE_RUN :   


  

 

[hannay]

I neer had that error but the fact it says: "invalid continue restart" makes me think that your run is not set as a branch run. How do you specify: env_run.xml:  
env_run.xml:  also, please check the variable CONTINUE_RUN :   


  

 

[fsche@mech_kth_se]

Do you mean env_conf.xlm rather than env_run.xml? For the latter, the specifications of "GET_REFCASE" and "RUN_REFCASE" does not exist according to the variable list. I'm just wondering because I saw somewhere else also env_run rather than env_conf in a user question and my branch run does not work so far (it did not write out the modified output frequency, just the old one).

 

[fsche@mech_kth_se]

Do you mean env_conf.xlm rather than env_run.xml? For the latter, the specifications of "GET_REFCASE" and "RUN_REFCASE" does not exist according to the variable list. I'm just wondering because I saw somewhere else also env_run rather than env_conf in a user question and my branch run does not work so far (it did not write out the modified output frequency, just the old one).

 

[fsche@mech_kth_se]

Do you mean env_conf.xlm rather than env_run.xml? For the latter, the specifications of "GET_REFCASE" and "RUN_REFCASE" does not exist according to the variable list. I'm just wondering because I saw somewhere else also env_run rather than env_conf in a user question and my branch run does not work so far (it did not write out the modified output frequency, just the old one).

 

[fsche@mech_kth_se]

Do you mean env_conf.xlm rather than env_run.xml? For the latter, the specifications of "GET_REFCASE" and "RUN_REFCASE" does not exist according to the variable list. I'm just wondering because I saw somewhere else also env_run rather than env_conf in a user question and my branch run does not work so far (it did not write out the modified output frequency, just the old one).

 

[ckuo@lbl_gov]

Cecile Hannay's response was correct.  She is referring to env_run.xml.  There are specific instructions on how to change the history output files in the middle of a run, in the CESM user guide, actually, and it is very helpful.

 

[ckuo@lbl_gov]

Cecile Hannay's response was correct.  She is referring to env_run.xml.  There are specific instructions on how to change the history output files in the middle of a run, in the CESM user guide, actually, and it is very helpful.

 

[ckuo@lbl_gov]

Cecile Hannay's response was correct.  She is referring to env_run.xml.  There are specific instructions on how to change the history output files in the middle of a run, in the CESM user guide, actually, and it is very helpful.