I am in the midst of doing a long restart run on my university cluster. Here are some relevant details:
resolution: TL319_t13
compset: 2000_DATM%JRA_SLND_CICE_POP2_DROF%JRA_SGLC_SWAV
cesmtag: cesm2.1.4-rc.08
Recently, my university computing center started requiring explicit project allocation numbers to submit batch jobs (they were "free" for a short while). I added this line to my env_batch.xml file, with the actual value of $PROJECT itself being set in another xml file.
When I execute
, I see two jobs in the queue, one is the actual simulation and the other is the dependent archiving job which is supposed to wait until the simulation is over. This was how things were before I made the above modification. I have made many successful restarts on the same cluster. For some reason, after the modification shown above, the archiving job starts to run before the actual simulation even starts. I am not even sure what is it archiving as the simulation has not started generating any new output. There is even a block of code in my xml file which appears to specify the archiving job depends on case.run or case.test finishing first.
Any ideas on what might be going on here? Thanks.
resolution: TL319_t13
compset: 2000_DATM%JRA_SLND_CICE_POP2_DROF%JRA_SGLC_SWAV
cesmtag: cesm2.1.4-rc.08
Recently, my university computing center started requiring explicit project allocation numbers to submit batch jobs (they were "free" for a short while). I added this line to my env_batch.xml file, with the actual value of $PROJECT itself being set in another xml file.
Code:
<arg flag="--account" name="$PROJECT"/>
When I execute
Code:
./case.submit
Code:
<group id="case.st_archive">
<entry id="prereq" value="$DOUT_S">
<type>char</type>
</entry>
<entry id="dependency" value="case.run or case.test">
<type>char</type>
</entry>
Any ideas on what might be going on here? Thanks.