#2332 closed help (fixed)

Problem creating ancillary file

Reported by: nfreychet Owned by: um_support
Component: UM Tools Keywords:
Cc: Platform: ARCHER
UM Version: 8.5



I am trying to create an aerosol emission ancillary file to replace the original one.
The ones I used before (and working) is (on ARCHER):
What I want to do is to create the same kind of file, but instead of having evolving emission it would just be a same year repeating itself.

So I converted the ancillary to netcdf, created the repeating year, and now using xancil to put it back in ancillary form. The output are in: /work/n02/n02/nfreyche/INPUTFILES/

For my first attempt, I got an error message:

IO: Open: /work/n02/n02/nfreyche/INPUTFILES/SO2_AllYears1981.anc on unit 110
IO: from environment variable SULPEMIS
 ******** Error in INANCILA ********
 Wrong calendar setting in Ancillary File   12
 Model run is set up for 365 day calendar.
 Ancillary File is for 360 day calendar.
 Rerun with correct ancillary file.
 INANCCTL: Error return from INANCILA  112
 INANCILA : Wrong calendar set in Ancillary File
 Failure in call to INANCCTL

???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: INITIAL_4A
? Error Code:   112
? Error Message: INANCILA : Wrong calendar set in Ancillary File
? Error generated from processor:     0
? This run generated  52 warnings

What surprises me is that the ancillaries I used before are also on 360 calendar. Plus, it is monthly output so it shouldn't change anything.

So I created new files with the option "gregorian" in xancil, but this time I got another error and I'm not sure how to interpret it:

  Information used in checking ancillary data set: position of lookup table in dataset: 559
  Position of first lookup table referring to data type  3
  Interval between lookup tables referring to data type  4  Number of steps 139
  STASH code in dataset  58   STASH code requested  58
 'start' position of lookup tables for dataset in overall lookup array  26869
 READFLDS: start address = 0

???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: UP_ANCIL
? Error Code:   139
? Error Message: REPLANCA :I/O ERROR
? Error generated from processor:     0
? This run generated  52 warnings

(the full log is: /home/n02/n02/nfreyche/output/xnbre000.xnbre.d17332.t121318.leave )

Also, I noticed that when using the gregorian option, the day are tags with hour 12 (like 1970/01/16:12.00) whereas with 360 calendar it is tag with hour 00 (not sure if it is important or not here).

Change History (8)

comment:1 Changed 19 months ago by nfreychet

I forgot to say that before that, I tried to simply create a 12 months climatology file using "periodic in time" option, but I had some error too.
And my job code is: xnbre

Last edited 19 months ago by nfreychet (previous) (diff)

comment:2 Changed 19 months ago by jeff


In xancil there is an option to make the ancillary file calendar independent, "Make generalised ancillary file 1 calendar independent", select this and the 360 day calendar. Using a 12 month climatology is the best way to do this, so try this again and let me if there are any errors.


comment:3 Changed 19 months ago by nfreychet

Hi Jeff,

I cannot find this option in xancil. In which section is it?


comment:4 Changed 19 months ago by jeff

It is in the panel where you specify all the options for the particular ancillary type. What version of xancil are you using? This option is only available for versions ≥ 0.55.

comment:5 Changed 19 months ago by nfreychet

Ah yes I see it now (I'm using version 0.57), but it is inactive, I cannot select Yes or No.

comment:6 Changed 19 months ago by jeff

It will only be active for ancillary file versions ≥ 8.5, so change the version number to 8.5 in the General Configuration panel.

comment:7 Changed 19 months ago by nfreychet

Hi Jeff,

I did as you suggest and it seems to work fine now. So I think the problem is solved for now.


comment:8 Changed 19 months ago by jeff

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