Custom Query (3366 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (67 - 69 of 3366)

Ticket Resolution Summary Owner Reporter
#1823 answered modify_CICE_header no longer working annette dilshadshawki
Description

Hi Annette,

For some reason, the modify_CICE_header tool gives me the error message 'Illegal instruction' and this happens after I enter the new value for time. It has been working fine up until now, but for some reason it no longer works :-( Do you know what could be going on? See below the procedure I have always taken but now with the error message:

[dshawk@exppostproc01:~/startdumps/xlzcj]$ /home/aospre/bin/modify_CICE_header
 Enter input file name:
xlzcji.restart.2321-09-01-00000
 Enter output file name:
xlzcji.restart.2321-09-01-00000_reset

 Please enter the name of the grid used in this file
 choose from ORCA2, ORCA1, ORCA025, CUSTOM (note case)
ORCA1

 Enter the value of oceanmixed_ice 'T' or 'F'
T
 oceanmixed_ice = .true.

 Time header variables:
 istep0:  183360
 time:  518400000.
 time_forc:  0.

 Enter new value for istep0 [N for no change]:
0
 Enter new value for time [N for no change]:
23328000
Illegal instruction

Many thanks, Dill

#1839 fixed Odd compilation error annette simon.tett
Description

Hi,

I'm getting the following error when I try and compile my job xlwt#s. I've done a full extract build and deleted the um directory so all is as clean as I can manage.

Partial output from the comp.leave file: # Start: 2016-03-21 09:49:54⇒ ftn -o max_calls.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/max_calls3z.f90 ftn-3121 crayftn: LIMIT MAX_CALLS_, File = ../../../../../../../../home2/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/max_calls3z.f90, Line = 1

There is a problem with a temp file being used in compilation.

fcm_internal compile failed (256) # Time taken: 2 s⇒ ftn -o max_calls.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/max_calls3z.f90 gmake: * [max_calls.o] Error 1

I wonder if this might be called by having a flush(6) in a piece of code. Added in an attempt to get some more output out of the model to understand why it is crashing..

So when I remove the flush(6) I still get compilation errors of the form: /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s: Assembler messages: /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s: Warning: end of file in string; '"' inserted /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:45: Error: junk at end of line, first unrecognized character is `"' /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:60: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:61: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:64: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:65: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:66: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:67: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:69: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:70: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:71: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:72: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:74: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:75: Error: invalid character (0x9) in mnemonic /work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:80: Error: invalid character (0x9) in mnemonic

and then.. # Start: 2016-03-21 10:09:07⇒ ftn -o lwrdiag_mod.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/lwrdiag_mod.f90 fcm_internal compile failed (256) # Time taken: 5 s⇒ ftn -o dust_parameters_mod.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/aerosols/dust_parameters_mod.f90 gmake: * [dust_parameters_mod.o] Error 1

If I compile dust_parameters_mod.f90 on the front end it works fine..

stett2@eslogin003:~/um> ftn -o dust_parameters_mod.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/aerosols/dust_parameters_mod.f90 stett2@eslogin003:~/um>

So help….

Simon

#1848 answered Model write error annette michmcr
Description

My model xlelm is running on ARCHER, however on Sunday night (Mar 27th) it failed to write out data for roughly two months (October and November in 2013) and yet continued to run and then write out files after this point (for 2014) until it ran out of time. Would you have any idea as to why the model would fail to write some files but continue running and then write other files after this?

Thanks Michelle

Note: See TracQuery for help on using queries.