Opened 9 months ago

Closed 9 months ago

#2704 closed help (fixed)

"Could not find metadata"

Reported by: ChrisWells Owned by: ros
Component: UM Model Keywords:
Cc: Platform:
UM Version:

Description

Hi,

whenever I open a suite I get errors saying "Could not find metadata" for several sections,

and when I try and run a suite I get:

ConfigProcessError?

I ran these suites a few weeks ago - has something changed which means I can no longer run them?

Cheers,
Chris

Change History (11)

comment:1 Changed 9 months ago by ChrisWells

the suites are e.g. u-bd343; all copies of the same suite. Other suites seem to open OK.

comment:2 Changed 9 months ago by ros

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

Hi Chris,

Can you try this again please? The suite u-bd343 opens up fine in rose edit for me. It also submits successfully too.

Regards,
Ros.

comment:3 Changed 9 months ago by ChrisWells

Hi Ros,

Cheers - it must have been temporary as it now submits OK for me too. However, I have another general question:

I was trying to just continue u-bd343 (and u-bd342) from where they had finished. They had ran up to the end of May 2020, but I seem to have restart files (in moose:/crum/u-bd343/ada.file) up to 20200301. So I tried to run them from there - I've done this on Puma with vn8.2, and tried to do it here by:

  • changing um → namelist → model input and output → dumping and meaning → astart, to the 20200301 ada.file
  • changing um → namelist → reconfiguration and ancillary control → general technical options → ainitial, to the same 20200301 ada.file
  • changing the start time to 20200301

This didn't work for me, and I tried to then do the above but change the start time to 20190901, but this didnt work either - the model couldn't find /History_data files that it looked for.

What other steps should I take to get the model to continue where it left off?

Many thanks,
Chris

comment:4 Changed 9 months ago by ros

Hi Chris,

The error you have indicates that there is a mismatch between the model_basis_time you have specified and the date of the start file.

You have specified a model basis time of 20200301 and supplied start data for 20200901.
And you currently have a similar wrong set up for 2019.

For future reference should you need to extend a run, again all you need to do is change the run length and do a rose suite-run --restart and the suite will pick up from where it previously finished and run to the new run length. This is covered in the UM Training course practicals for reference.

Regarding the data in MASS, suites will only archive data when it is no longer needed by the run (ie. for the next cycle to complete or to restart it). So in your original case May's data wasn't archived as it was left in the data/History_Data directory to enable the run to be continued.

You should also turn off compilation & reconfiguration - there is no need to recompile as you already have an executable and you don't need to reconfigure the dump either.

Regards,
Ros.

comment:5 Changed 9 months ago by ChrisWells

Hi Ros,

Thanks for all the info. The restart method hasn't worked on u-bd343, presumably because I have tried to change it manually, so I'm looking to run a simulation using the output restart files.

I'm not sure where I have set the times differently - in u-bd342 for example, model basis time is 20190901, and the astart file is the same time, as is the dumping and meaning file, yet it fails on atmos_main with

???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
?  Error code: 2
?  Error from routine: GLUE_CONV_6A
?  Error message: Deep conv went to model top at point           15 in seg   1 on call  1
?  Error from processor: 239
?  Error number: 40

Do you know how I can get this to run?

Many thanks,
Chris

comment:6 Changed 9 months ago by ros

Hi Chris,

I only looked at u-bd343 and it is this suite I was referring to as having times set inconsistently. If you change the model basis to 20190901 the suite will run as I tried it. The message inferred you were having the same problem with both suites so I didn't bother looking at the other one. As you say you can only do a rose suite-run --restart if you have not since tried to run in some other way.

The error with u-bd342 usually indicates some instability in the model. I am now away until the New Year, but I will see if one of my colleagues can look at this for you.

Regards,
Ros.

comment:7 Changed 9 months ago by ChrisWells

Hi Ros,

I've experimented with the input times (now I'm using 20200601, and referring to the start file in /History_data), and if I have the times different I do indeed get an error telling me that, but if they are the same I get the error above - more detail:

???????????????????????????????????????????????????????????????????????????????
???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
?  Error code: 3
?  Error from routine: GLUE_CONV_6A
?  Error message: Mid conv went to the top of the model at point           13 in seg on call  1
?  Error from processor: 37
?  Error number: 38
????????????????????????????????????????????????????????????????????????????????

[37] exceptions: An non-exception application exit occured.
[37] exceptions: whilst in a serial region
[37] exceptions: Task had pid=67754 on host nid05403
[37] exceptions: Program is "/home/d00/chwel/cylc-run/u-bd343/share/fcm_make_um/build-atmos/bin/um-atmos.exe"
Warning in umPrintMgr: umPrintExceptionHandler : Handler Invoked
?  Error code: 3
?  Error from routine: GLUE_CONV_6A
?  Error message: Mid conv went to the top of the model at point           16 in seg on call  2
?  Error from processor: 392
?  Error number: 41

Have a good holiday! Hopefully someone else can help me with this before then.

Many thanks,
Chris

comment:8 Changed 9 months ago by grenville

Chris

You have the input file to the reconfiguration (ainitial) and its output file (astart) set to the same file - the reconfiguration claims to have succeeded, but I'd be a suspicious of the file now.

I suggest you get a new start file and set the file naming correctly and try again.

Grenville

comment:9 Changed 9 months ago by ChrisWells

Hi Grenville,

Thanks for the reply - I was unsure which of those I needed to change - should I be leaving astart as what it was (if it is output) and just be changing ainitial to the file I want the model to start with?

Many thanks,
Chris

comment:10 Changed 9 months ago by ChrisWells

Hi Grenville,

I changed the astart to the default, and made sure to just change the ainitial, using a different start dump, and it seems to be working fine.

Thanks both for your help,

Chris

comment:11 Changed 9 months ago by grenville

  • Resolution set to fixed
  • Status changed from accepted to closed

Chris

Glad you have sorted it out.

Grenville

Note: See TracTickets for help on using tickets.