Opened 4 years ago

Closed 4 years ago

#1502 closed help (answered)

Extract fail, svn cannot locate config file

Reported by: dsergeev Owned by: um_support
Component: FCM Keywords: fcm, ext.out, extract fail
Cc: Platform: ARCHER
UM Version: 8.5

Description

Hi,
I'm trying to run a reconfiguration of a global version of UM8.5, but stuck in the FCM extract settings. During submit the extract script produces the following error:
"UMATMOS base repository failed
See extract output file
/home/dsergeevumui_extracts/xlceb/baserepos/UMATMOS/ext.out
MAIN_SCR: Extract failed".

And ext.out output is:
"Config file (ext): svn://puma/UM_svn/UM/trunk/src/configs/bindings/container.cfg@13123
Config file (ext): svn://puma/UM_svn/UM/trunk/src/configs/bindings/UMATMOS_repos.cfg@13123
Config file (ext): svn://puma/UM_svn/UM/trunk/src/configs/machines/init_options.cfg@13123
[FAIL] svn://puma/UM_svn/UM/trunk/src/configs/machines/cray-xc30-cce-archer/machine.cfg@13123: cannot locate config file, abort at /home/fcm/fcm-2014.12.0/bin/../lib/FCM1/ConfigSystem.pm line 539."

In FCM Options for UM Atmosphere and Reconfiguration is UM_SVN_URL=fcm:um-tr
UM_SVN_BIND=$UM_SVN_URL/src/configs/bindings
UM_CONTAINER=$UM_SVN_BIND/container.cfg

So I can't figure out why a number 13123 appears in the extract call. Could you please help me?

Thanks,
Denis

Change History (11)

comment:1 Changed 4 years ago by ros

Hi Denis,

In order to run on ARCHER you need to go to window FCM Options for atomsphere and reconfiguration and change the following;

UM_SVN_BIND=fcm:um_br/dev/um/vn8.5_machine_cfg/src/configs/bindings
UM_CONTAINER=$UM_SVN_BIND/container.cfg@vn8.5_cfg

This will enable the job to find the cray-xc30-cce-archer config file which is not on the Met Office trunk. All jobs on ARCHER must include the appropriate configuration branch.

You will also need to add the NCAS branch to the modifications table in the same window, with a Y in the last column:

fcm:um_br/pkg/Config/vn8.5_ncas/src

This branch adds in all the script changes required to run on ARCHER. And to answer you question about the number in the extract call…. the setup you had originally means that version vn8.5 of the trunk is being used which equates to r13123. Once you change this to the settings above this number will change to r16642.

Regards,
Ros.

comment:2 Changed 4 years ago by dsergeev

Thank you. Now it is extracted successfully.

However, compilation fails for files

tstmsk.f90
readlsta.f90
readlsta_4a.f90

with these errors:

ftn -o type_dep_var_mod.o -I/work/n02/n02/dsergeev/xlceb/umatmos/inc -I/work/n02/n02/dsergeev/xlceb/baserepos/JULES/inc -I/work/n02/n02/dsergeev/xlceb/baserepos/JULES/inc -I/work/n02/n02/dsergeev/xlceb/baserepos/UMATMOS/inc -O3 -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom4.5/archer_cce_mpp/inc     -h omp -c /work/n02/n02/dsergeev/xlceb/umatmos/ppsrc/UM/atmosphere/AC_assimilation/type_dep_var.f90


ftn-732 crayftn: ERROR TSTMSK, File = ../../../../xlceb/umatmos/ppsrc/UM/control/top_level/tstmsk.f90, Line = 61, Column = 36
  "L_SICE_MULTILAYERS" is not in module "SWITCHES".


ftn-732 crayftn: ERROR TSTMSK, File = ../../../../xlceb/umatmos/ppsrc/UM/control/top_level/tstmsk.f90, Line = 61, Column = 56
  "L_TOP" is not in module "SWITCHES".


ftn-732 crayftn: ERROR TSTMSK, File = ../../../../xlceb/umatmos/ppsrc/UM/control/top_level/tstmsk.f90, Line = 62, Column = 21
  "L_CTILE" is not in module "SWITCHES".

Cray Fortran : Version 8.2.x.x (u82093f82212i82224p82394a82022e82011z82394)
Cray Fortran :                 (x8232r82023w82008t8213b82042k82020)
Cray Fortran : Fri Mar 06, 2015  10:24:59
Cray Fortran : Compile time:  0.1920 seconds
Cray Fortran : 1353 source lines
Cray Fortran : 3 errors, 0 warnings, 0 other messages, 0 ansi
Cray Fortran : "explain ftn-message number" gives more information about each message.
fcm_internal compile failed (256)
gmake: *** [tstmsk.o] Error 1

ftn-732 crayftn: ERROR READLSTA, File = ../../../../xlceb/umatmos/ppsrc/UM/control/top_level/readlsta.f90, Line = 15, Column = 42
  "L_SSICE_ALBEDO" is not in module "SWITCHES".

Cray Fortran : Version 8.2.x.x (u82093f82212i82224p82394a82022e82011z82394)
Cray Fortran :                 (x8232r82023w82008t8213b82042k82020)
Cray Fortran : Fri Mar 06, 2015  10:24:59
Cray Fortran : Compile time:  0.2200 seconds
Cray Fortran : 1393 source lines
Cray Fortran : 1 errors, 0 warnings, 0 other messages, 0 ansi
Cray Fortran : "explain ftn-message number" gives more information about each message.
fcm_internal compile failed (256)
gmake: *** [readlsta.o] Error 1


ftn-732 crayftn: ERROR READLSTA_4A, File = ../../../../xlceb/umatmos/ppsrc/UM/control/top_level/readlsta_4A.f90, Line = 27, Column = 27
  "L_SSICE_ALBEDO" is not in module "SWITCHES".

Cray Fortran : Version 8.2.x.x (u82093f82212i82224p82394a82022e82011z82394)
Cray Fortran :                 (x8232r82023w82008t8213b82042k82020)
Cray Fortran : Fri Mar 06, 2015  10:24:59
Cray Fortran : Compile time:  0.2720 seconds
Cray Fortran : 1409 source lines
Cray Fortran : 1 errors, 0 warnings, 0 other messages, 0 ansi
Cray Fortran : "explain ftn-message number" gives more information about each message.
fcm_internal compile failed (256)
gmake: *** [readlsta_4a.o] Error 1

Is this related to my previous mistakes?

Thanks,
Denis

comment:3 Changed 4 years ago by ros

Hi Denis,

It's difficult to advise here, as I know nothing about the provenance of the job. As there are no branches then it can't be code changes that are causing problems. Where did this job come from? Has it been run successfully before? If so where? Have you made any changes to it, from the original, other than those above?

Regards,
Ros.

comment:4 Changed 4 years ago by dsergeev

Hi Ros,

I copied the job from another user and I haven't made it run yet.
The original job was a forecast job, that was run after a separate reconfiguration job, I assume.
So I copied only the forecast job and changed it. The main changes I made included switching on the compilation and reconfiguration. And also I had to switch off User hand edits and bottom and top script inserts in Script Inserts and Modifications, since I don't have them on my machine.

Could you recommend me what to do, please?
Denis

Last edited 4 years ago by dsergeev (previous) (diff)

comment:5 Changed 4 years ago by ros

Hi Denis,

Having looked at your job a bit more, I can see that this job was a nesting suite job - indicated by all the hand-edits. It is very unlikely that you can take this job and just switch these off. Can you give me the id of the job you copied please? I'm also wondering if it is a job that is part of the Parallel suite? Is there a particular reason why you have taken this particular job? We are wondering if there is another job that would be more suitable and that is already set up to run on ARCHER. We do have other UM8.5 N512 jobs that we know run ok on ARCHER.

Regards,
Ros.

comment:6 Changed 4 years ago by dsergeev

Hi Ros,

The original job id is xkql-b, I thought it would suite my needs. I'm basically trying to run the global UM and then a regional version for the region of the Norwegian Sea with LBCs from the global model. The regional run settings are from the experiments done by Mark Weeks at the Met Office and I have the job imported in the same experiment (xlce-a).
So I would really appreciate if you can suggest a more suitable global job for my case. I'd prefer the same resolution (N512) and any version higher than 8.2.

Thank you for your time.
Denis

comment:7 Changed 4 years ago by grenville

Denis

xjlej is an N512 GA6 Endgame job as in xkql. You could try this.

Grenville

comment:8 Changed 4 years ago by dsergeev

Hi again,

I am sorry, I still can't run the job that you suggested in the previous comment. The UMRECON build passes successfully, but during the reconfiguration different errors emerge, mostly connected with various ancillary files, which I don't have on my account. And I can't trace the files either, since as I understand, the environmental variables - paths to files - are not set explicitly via umui.
Although I switched off the input of some of the ancillary files, the errors still appear, and I am not sure if I'm doing the right thing. For example, one of the latest errors was due to the fact that I switched off the option "The ancillary Land-Sea_mask to be configured" (because I don't have $UM_ANCIL_MASK_DIR/$UM_ANCIL_MASK_FILE), and in the .rcf.leave file there was the following error:

???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: Setup_LSM_Out
? Error Code: 50
? Error Message: Number of land points does not agree with input namelist!
? Error generated from processor: 0
? This run generated 1 warnings
????????????????????????????????????????????????????????????????????????????????

Could you please guide me through these settings? Maybe there is another job that is not "climate" job and has fewer additional ancillary files for input?

Thank you,
Denis

Last edited 4 years ago by dsergeev (previous) (diff)

comment:9 Changed 4 years ago by annette

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

comment:10 Changed 4 years ago by dsergeev

While waiting for help I managed to fix the problem with the number of land points, but now the reconfiguration gives me another error:

????????????????????????????????????????????????????????????????????????????????
???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: Rcf_Set_Data_Source
? Error Code: 30
? Error Message: Section 0 Item 101 : Required field is not in input dump!
? Error generated from processor: 0
? This run generated 1 warnings
????????????????????????????????????????????????????????????????????????????????

I tried to run Willie McGuinty?'s utilities (http://cms.ncas.ac.uk/ticket/1538) for checking the start dump, but they do not give me any complaints. I also tried switching off the initialisation of user diagnostics as was suggested in the related tickets, but with the error still appears.

Can you tell me what to do?

Regards,
Denis

comment:11 Changed 4 years ago by dsergeev

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