Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Error in porting CESM2

jedwards

CSEG and Liaisons
Staff member
In the module paths you need to have init_path and cmd_path entries for lang="python" . I think that they would be:      /usr/share/Modules/init/python.py /usr/bin/modulecmd python
 

jedwards

CSEG and Liaisons
Staff member
In the module paths you need to have init_path and cmd_path entries for lang="python" . I think that they would be:      /usr/share/Modules/init/python.py /usr/bin/modulecmd python
 

jedwards

CSEG and Liaisons
Staff member
In the module paths you need to have init_path and cmd_path entries for lang="python" . I think that they would be:      /usr/share/Modules/init/python.py /usr/bin/modulecmd python
 

jedwards

CSEG and Liaisons
Staff member
Looking at the content of the file - lets just work with a single compiler for now and remove the other one - you also only need to add changes to the default settings from cime/config/cesm/machines/config_compilers.xml  don't repeat settings that are already there. 
 

jedwards

CSEG and Liaisons
Staff member
Looking at the content of the file - lets just work with a single compiler for now and remove the other one - you also only need to add changes to the default settings from cime/config/cesm/machines/config_compilers.xml  don't repeat settings that are already there. 
 

jedwards

CSEG and Liaisons
Staff member
Looking at the content of the file - lets just work with a single compiler for now and remove the other one - you also only need to add changes to the default settings from cime/config/cesm/machines/config_compilers.xml  don't repeat settings that are already there. 
 

botto@usf_edu

New Member
I added the lines in that you specified into config_machines.xml, and re-ran: it's still failing with 5 errors, as show in the output attached. Thank you for all of your help so far!
 

botto@usf_edu

New Member
I added the lines in that you specified into config_machines.xml, and re-ran: it's still failing with 5 errors, as show in the output attached. Thank you for all of your help so far!
 

botto@usf_edu

New Member
I added the lines in that you specified into config_machines.xml, and re-ran: it's still failing with 5 errors, as show in the output attached. Thank you for all of your help so far!
 

jedwards

CSEG and Liaisons
Staff member
Your config batch file seems to be empty - you need at least the following:       sbatch                              regular       Modified appropriately for your queueing system 
 

jedwards

CSEG and Liaisons
Staff member
Your config batch file seems to be empty - you need at least the following:       sbatch                              regular       Modified appropriately for your queueing system 
 

jedwards

CSEG and Liaisons
Staff member
Your config batch file seems to be empty - you need at least the following:       sbatch                              regular       Modified appropriately for your queueing system 
 

botto@usf_edu

New Member
Thanks for the info! I now have J_TestCreateNewcase running correctly with no errors. Unfortunately, now L_TestSaveTimings is throwing errors. Attached are the outputs and config files used in ~/.cime.
 

botto@usf_edu

New Member
Thanks for the info! I now have J_TestCreateNewcase running correctly with no errors. Unfortunately, now L_TestSaveTimings is throwing errors. Attached are the outputs and config files used in ~/.cime.
 

botto@usf_edu

New Member
Thanks for the info! I now have J_TestCreateNewcase running correctly with no errors. Unfortunately, now L_TestSaveTimings is throwing errors. Attached are the outputs and config files used in ~/.cime.
 

botto@usf_edu

New Member
I apologize: there was a leading character in the config_batch_04-01-19.xml file that caused web browsers to not render it. I have fixed it, so it now displays correctly.
The only difference between mine and the one you posted is the "" statement: I will add then and then try.

 
Top