Opened 3 years ago

Closed 2 years ago

#2191 closed help (fixed)

Reconfiguration problem

Reported by: jfgu Owned by: ros
Component: UM Model Keywords: reconfiguration
Cc: Platform: ARCHER
UM Version: <select version>

Description

My job failed because of the problem of reconfiguration. It is said "um-recon" command is not found. See below:
http://puma.nerc.ac.uk/rose-bush/view/jfgu/u-am753?&no_fuzzy_time=0&path=log/job/20000101T0000Z/atmos_recon/01/job.err
I checked the setup of my suite. It is "um-recon" in my um-command setting. I didn't make any change of it. It runs OK yesterday. I just changed some parameters of run length, cycle length and timestep.
Could someone help me with this problem? Thank you very much!

Jian-Feng

Change History (4)

comment:1 Changed 3 years ago by ros

  • Owner changed from um_support to ros
  • Platform set to ARCHER
  • Status changed from new to accepted

Hi Jian-Feng,

I'm guessing you must have done a rose suite-run --new since you ran yesterday as you have wiped the build directory so there is no recon or model executable or controlling scripts in the ~/cylc-run/u-am753/share directory on ARCHER. You will need to submit the suite again to build the reconfiguration and model executables.

For reference rose suite-run --new deletes the entire ~/cylc-run/<suite-id> directory on both ARCHER and PUMA, and should only be used when you wish to start again from a totally clean slate. Otherwise use rose suite-run to start the suite from the beginning without deleting those directories.

Regards,
Ros.

Last edited 3 years ago by ros (previous) (diff)

comment:2 Changed 3 years ago by ros

That should have said:

Otherwise use rose suite-run to start the suite from the beginning without deleting those directories.

comment:3 Changed 3 years ago by jfgu

Hi Ros,

I did tick the "Build UM" off when I resubmit the job. Thank you for your suggestion!

Jian-Feng

comment:4 Changed 2 years ago by grenville

  • Keywords reconfiguration added
  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.