I have what must be a very basic question about the role played by the
1. I started a branch run from 0265-01 lasting two months after which I had a restart file at 0265-03, consistent with what was in the rpointer.ocn.restart file. For this run, the
2. I then made some changes to the tx0.1v3_tavg_contents file by adding more variables to the daily stream.
3. I ran
4. The code continued from 0265-03 (see #1).
5. Midway into the run, I noticed
6. My question: how did the code continue running from 0265-03 even when there was no indication it should be a continuation run? (because I forgot to change the flag to true after the first 2-month branch run.)
continue_run
flag.1. I started a branch run from 0265-01 lasting two months after which I had a restart file at 0265-03, consistent with what was in the rpointer.ocn.restart file. For this run, the
continue_run
flag was set to false. The branch run had a case name that was different from the case corresponding to the restart file at 0265-01.2. I then made some changes to the tx0.1v3_tavg_contents file by adding more variables to the daily stream.
3. I ran
./case.build --clean-all; ./case.build
followed by ./case.submit --skip-preview-namelist
.4. The code continued from 0265-03 (see #1).
5. Midway into the run, I noticed
continue_run
was still set fo false when I should have changed it to true.6. My question: how did the code continue running from 0265-03 even when there was no indication it should be a continuation run? (because I forgot to change the flag to true after the first 2-month branch run.)