I have run a long forecast and want to re-start it. I have the srf files and the rcf file. When I try to restart the forecast (without making any changes to fort.4 or rcf) nothing seems to happen - i.e. no more timesteps are calculated and thus no additional output is produced. The simulation does not fail though. Do I need to change something in either fort.4 or rcf? I have attached the NODE file.

NODE.001_01.gz

5 Comments

  1. Unknown User (nagc)

    Hi Victoria,

    When you run the restart do you increase the value of NSTOP? Otherwise the model will read the restart files and not progress because it thinks all the timesteps are complete.

      Glenn

  2. Unknown User (nagc)

    Thanks - I'm fairly sure this is the problem. I did change NSTOP but assumed that the start of the restart was time 0 again. Clearly I need to add the restart forecast length to NSTOP at the end of the first forecast. I'll let you know if it works - the job is currently in a queue.

    Victoria

  3. Unknown User (nagc)

    When I have set NSTOP to an appropriate value, I get this error in my restart forecast:

    GRIB_API ERROR : grib_set: missingValue Invalid grib id

    Any idea what the problem is? Interesting the simulation did not fail - it just seemed to hang and not produce any output. 

    Victoria

  4. Unknown User (nagc)

    Hi Victoria,  I'm not sure what's causing that. I don't recall seeing that before. Can you send the NODE file?

    Thanks,  Glenn

  5. Unknown User (nagc)

    Here is the Node file. I'm not sure it is helpful as the job does not fail - it just hangs without producing output. In this case I've killed the job so there is no trace back

    Victoria

    NODE.001_01_2.gz