Opened 3 years ago

Closed 3 years ago

#1880 closed help (completed)

My job will not follow re-submission pattern on a CRUN

Reported by: s.varma13 Owned by: ros
Component: UM Model Keywords: CRUN Re-submission
Cc: Platform: MONSooN
UM Version: 8.4

Description

Hello

I am having problems after I have compiled a run to Monsoon.

The job is xmbxf and is called “cloud reference run 2008 meaning off 10 diags 1 day” and I am running this on version 8.4. I compliled the run successfully and then tries to run a CRUN.

I have a start date of 1 December 2006 with a run time of 2 years and 1 month.
I have selected 10 diagnostics (a mixture of both 2d and 3d).
My time profile is T1H which is every hour for the run time.
My domain profile is either DALLH or DIAG depending on whether it is 2d or 3d.
My usage profile is UPA, stream 60, override size of 32,000, period of 1 day (given the hourly output).
Resubmission pattern is 30 days.

When I submit the run for the first time, it outputs 30 files for December 2006 as requested in the compilation. When I resubmit to do the continuous runs (having changed the compilation and run options to run the model - CRUN), it overrides the previous 30 files produced in the compilation, reproduces these files (December 2006) but then stops.
You can see this here
xcm100 cd /projects/ukca-imp/suvar/xmbxf

The .leave file is xmbxf000.xmbxf.d16137.t133448.leave

Something is causing the job to stop after a month instead of resubmitting for the next 30 days.

I could not see anything in the leave file that helps.

Could you please help?

Many thanks.

Sunil

Change History (11)

comment:1 Changed 3 years ago by ros

  • Owner changed from s.varma13 to um_support
  • Status changed from new to assigned

comment:2 Changed 3 years ago by ros

  • Owner changed from um_support to ros
  • Status changed from assigned to accepted

Hi Sunil,

You appear to have changed the settings in xmbxf since you submitted this query - you've re-run compilation and reconfiguration and have both these turned on in the UMUI now. Please don't make subsequent changes to jobs after raising a query with us as it's then very difficult to help track down problems.

Instructions on how to set your job up for automatic resubmission can be found here:
http://cms.ncas.ac.uk/wiki/Docs/AutomaticResubmission

If you can't get resubmission working after following these instructions please get back to us and we'll take a look.

Cheers,
Ros.

comment:3 Changed 3 years ago by s.varma13

Hi Ros

I am sorry - I forgot to make a copy and re-run the copy. I made one amendment to the run and that was to change the re-submission pattern from 30 days to 1 month instead to see if this was the problem. I will finish the compiling and do a CRUN following that having looked at the above link.

Many thanks

Sunil

comment:4 Changed 3 years ago by s.varma13

Hello

I am still having problems after I have compiled my run to Monsoon and then performed a CRUN. I looked at the instructions above and confirm that I have set up my job for re-submission as required.

The job is xmbxf and is called “cloud reference run 2008 meaning off 10 diags 1 day” and I am running this on version 8.4. I compliled the run successfully and then ran a CRUN.

I have a start date of 1 December 2006 with a run time of 2 years and 1 month.
I have selected 10 diagnostics (a mixture of both 2d and 3d).
My time profile is T1H which is every hour for the run time.
My domain profile is either DALLH or DIAG depending on whether it is 2d or 3d.
My usage profile is UPA, stream 60, override size of 32,000, period of 1 day (given the hourly output).
Resubmission pattern is 1 month.

When I submit the run for the first time, it outputs 30 files for December 2006 as requested in the compilation. When I resubmit to do the continuous runs (having changed the compilation and run options to run the model - CRUN as required), it overrides the previous 30 files produced in the compilation (December 2006), reproduces these files again but then stops - [xcml00]/projects/ukca-imp/suvar/xmbxf.

The run should continue from where the initial run finished and then each of the chunks should submit themselves automatically without further intervention but this is not happening.

The .leave file is [xcml00]/home/suvar/output/xmbxf000.xmbxf.d16138.t170939.leave

Something is causing the job to stop after a month instead of resubmitting for the next month.

I could not see anything in the leave file that helps.

Could you please help?

Many thanks.

Sunil

comment:5 Changed 3 years ago by grenville

Sunil

xmbxf has do no dumps - you must write dumps at least at the automatic resubmission frequency. The model can not continue otherwise.

Grenville

comment:6 Changed 3 years ago by s.varma13

Hi Grenville

Is there a link to explain how to do this or could you please briefly explain?

Thanks

Sunil

comment:7 Changed 3 years ago by ros

Hi Sunil,

It's explained in paragraph c) of the above automatic resubmission document.

As Grenville said you have dumping switched off. You need to go to UMUI window Atmosphere → Control → Post-processing, dumping and meaning → Dumping and Meaning and turn it on. Select Regular frequency dumps with possible meaning sequence.

Your resubmission period (30days in your case) then needs to be a multiple of the restart dump frequency.

For example you could specify 30day dumps or 10day dumps. Basically the model needs a restart dump in order to restart, so you need to make sure a dump is output at the end of each CRUN chunk.

Cheers,
Ros.

comment:8 Changed 3 years ago by s.varma13

Thanks a lot Ros, I have made those amendments and have submitted the job for compiling.

Best wishes

Sunil

comment:9 Changed 3 years ago by ros

Hi Sunil,

For future reference when you change dumping frequency, model run length etc, you don't need to recompile.

Cheers,
Ros.

comment:10 Changed 3 years ago by s.varma13

Ros, thanks for letting me know.

Best wishes

Sunil

comment:11 Changed 3 years ago by ros

  • Resolution set to completed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.