cosima/1deg_jra55_iaf

One degree ACCESS-OM2 experiment using JRA55-do IAF forcing.

1deg_jra55_iaf's Issues

missing parameters in cice_in.nml

@pwongpan and I were looking at the CICE diagnostics, and noticed that at least six of them were absent in cice_in.nml. Four of these are set to 'm' by default (src/cice5/source/ice_history_shared.F90), and therefore they have been outputted in most of our runs, including OMIP2.

The missing parameters are:

       f_alvdf     = 'x', f_alidf      = 'x', &
       f_alvdr_ai  = 'm', f_alidr_ai   = 'm', &
       f_alvdf_ai  = 'm', f_alidf_ai   = 'm', &

This issue appears to be present also in https://github.com/COSIMA/01deg_jra55_iaf/blob/master/ice/cice_in.nml, so fixing this should save up some disk space for diagnostics particularly in high-res runs.

sync_data.sh does not concatenate and copy daily ice output

When I do 'qsub sync_data.sh', it successfully copies the output/restart over, except that 'ice/OUTPUT' in the destination is empty.

In the output file (sync.o19960106), there is this message that might prevent from using cdo commands:

"Fatal error: modules not available."

Any idea what is wrong?

My control directory is: /scratch/v45/hh0162/access-om2-iamip2/control/1deg_jra55_iaf_iamip2_pro

And the destination is: /g/data/ik11/outputs/access-om2/1deg_jra55_iaf_iamip2_pro

master+bgc

@aekiss I'm opening up a new issue to report any changes I make while I try to create the master+bgc branch.

My first test run suggests that I need to increase max_files in diag_manager_nml of ocean/input.nml.

/scratch/v45/hh0162/access-om2-cycle4/control/1deg_jra55_iaf_bgc/archive/error_logs/access-om2.30703854.gadi-pbs.err:

FATAL from PE   184: diag_util_mod::init_file:  max_files exceeded, increase max_files via the max_files variable in the namelist diag_manager_nml.

In 1-deg, max_files = 200. I changed to 400.

After this change, I got this error next (/scratch/v45/hh0162/access-om2-cycle4/control/1deg_jra55_iaf_bgc/archive/error_logs/access-om2.30738106.gadi-pbs.err):

FATAL from PE     1: diag_axis_mod::diag_axis_init: num_axis_sets (**) exceeds max_num_axis_sets (**).  Increase max_num_axis_sets via diag_manager_nml.

I'm not really sure what this means. I think we can tell how many files will be produced from diag_table, but can we tell also what value to set for max_num_axis_sets?