Is there any files named 01deg_jra55_ryf.e* or access-om2.err in the run directory?
Yes, its access-om2.err with the same error as before:
Error - from NetCDF library
ncvar opening /g/data/x77/amh157/JRA55-do/RYF/v1-3/RYF.rsds.1990_1991.nc
No such file or directory
That error doesnât really make sense if youâve altered the config.yaml and forcing.json files. Is that maybe a residual file? Did you try payu sweep before you re-ran?
Just for clarity - can you post your atmosphere/forcing.json file here as well? (Or open up permissions so we can see your run directory?)
Hi @AndyHoggANU
Thanks for the comment. It was a misunderstanding. I thought forcing.json will get updated once I do this:
I have changed both now and the previous error has gone. Now facing a new one!!
Error:
remap_runoff_new: can't open weights file: INPUT/rmp_jrar_to_cict_CONSERV.nc
No such file or directory
Error: remap_runoff_mod, ncheck failed.
Anyway I have changed the permissions, could you please check if you can access the run directory: /home/581/sb4233/access-om2/my_new_exp
Thanks!
Sorry, still canât get into that directory as I canât get into /home/581/sb4233/ âŚ
But, the file it is now asking for is sitting in /g/data/ik11/inputs/access-om2/input_08022019/yatm_01deg which would probably be your original input file in config.yaml. Can you try reverting that line?
1 Like
Thank you!! I kept both of the inputs in config.yaml. I think now its running fine -
(base) [sb4233@gadi-login-08 my_new_exp]$ grep cur_exp-datetime work/atmosphere/log/matmxx.pe00000.log
{ "cur_exp-datetime" : "2180-01-01T00:00:00" }
{ "cur_exp-datetime" : "2180-01-01T03:00:00" }
{ "cur_exp-datetime" : "2180-01-01T06:00:00" }
{ "cur_exp-datetime" : "2180-01-01T09:00:00" }
{ "cur_exp-datetime" : "2180-01-01T12:00:00" }
{ "cur_exp-datetime" : "2180-01-01T15:00:00" }
{ "cur_exp-datetime" : "2180-01-01T18:00:00" }
{ "cur_exp-datetime" : "2180-01-01T21:00:00" }
{ "cur_exp-datetime" : "2180-01-02T00:00:00" }
{ "cur_exp-datetime" : "2180-01-02T03:00:00" }
{ "cur_exp-datetime" : "2180-01-02T06:00:00" }
{ "cur_exp-datetime" : "2180-01-02T09:00:00" }
{ "cur_exp-datetime" : "2180-01-02T12:00:00" }
{ "cur_exp-datetime" : "2180-01-02T15:00:00" }
{ "cur_exp-datetime" : "2180-01-02T18:00:00" }
{ "cur_exp-datetime" : "2180-01-02T21:00:00" }
{ "cur_exp-datetime" : "2180-01-03T00:00:00" }
{ "cur_exp-datetime" : "2180-01-03T03:00:00" }
{ "cur_exp-datetime" : "2180-01-03T06:00:00" }
{ "cur_exp-datetime" : "2180-01-03T09:00:00" }
{ "cur_exp-datetime" : "2180-01-03T12:00:00" }
{ "cur_exp-datetime" : "2180-01-03T15:00:00" }
{ "cur_exp-datetime" : "2180-01-03T18:00:00" }
{ "cur_exp-datetime" : "2180-01-03T21:00:00" }
{ "cur_exp-datetime" : "2180-01-04T00:00:00" }
{ "cur_exp-datetime" : "2180-01-04T03:00:00" }
{ "cur_exp-datetime" : "2180-01-04T06:00:00" }
{ "cur_exp-datetime" : "2180-01-04T09:00:00" }
though I got some warnings:
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_pot_rho_1
WARNING from PE 0: diag_util_mod::opening_file: module/field_name (ocean_model/u_surf) NOT registered
WARNING from PE 0: diag_util_mod::opening_file: module/field_name (ocean_model/v_surf) NOT registered
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_wt
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_uhrho_et
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_vhrho_nt
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_dzt
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_temp
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_salt
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_u
WARNING from PE 0: diag_util_mod::opening_file: one axis has auxiliary but the corresponding field is NOT found in file ocean_daily_3d_v
2 Likes
I think those warnings should be fine - but worth checking the output when it finishes its first segment.
1 Like