You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In each $case, the option to run to resubmit to the queue after a successful submission and run is changed by increasing the "RESUBMIT" value to > 0 in the env_run.xml file. In the $case.run file, the parameter $islastjob was being given a value of FALSE from the perl subroutine resubmitCheck() to the perl subroutine ACME/cime/utils/perl15lib/Batch/BatchUtils.pm doResubmit(). The line :
if($islastjob eq 'TRUE' && $resubmit > 0 && defined $sta_ok)
should be:
if($islastjob eq 'FALSE' && $resubmit > 0 && defined $sta_ok)
There is a few more steps after this, but at least sbatch is being envoked again.
The text was updated successfully, but these errors were encountered:
That might work. I've got it to resubmit and count-down the # of submissions, but it's a hack. There's redundant subroutines for Base and then for Mira....
I'll wait for CIME5.
Add fix to config_archive.xml for DART, mosart, rtm
and ww3 element values for filename pattern matching.
Update case_st_archive.py to correctly
archive DART v1 files.
Test suite: ERR.f19_g16.B1850.yellowstone_intel.allactive-defaultio
Fixes [Github issue #]: #1129 and #1124
User interface changes: None
Input data changes: None
Code review:
In each $case, the option to run to resubmit to the queue after a successful submission and run is changed by increasing the "RESUBMIT" value to > 0 in the env_run.xml file. In the $case.run file, the parameter $islastjob was being given a value of FALSE from the perl subroutine resubmitCheck() to the perl subroutine ACME/cime/utils/perl15lib/Batch/BatchUtils.pm doResubmit(). The line :
if($islastjob eq 'TRUE' && $resubmit > 0 && defined $sta_ok)
should be:
if($islastjob eq 'FALSE' && $resubmit > 0 && defined $sta_ok)
There is a few more steps after this, but at least sbatch is being envoked again.
The text was updated successfully, but these errors were encountered: