Open aekiss opened 8 months ago
Are you saying this behaviour is new with 1.0.19
?
I believe the problem occurs because you're specifying directories and expecting payu
to recursively descend the directory tree, which though it does seem to do this (incorrectly) I'm not sure we should support it
In the ACCESS-OM2 config.yaml
you have this:
https://github.com/COSIMA/01deg_jra55_iaf/blob/master/config.yaml#L25-L35
input:
- /g/data/ik11/inputs/access-om2/input_20201102/yatm_01deg
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hr/rsds/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hr/rlds/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hr/prra/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hr/prsn/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hrPt/psl/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/land/day/friver/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hrPt/tas/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hrPt/huss/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hrPt/uas/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/atmos/3hrPt/vas/gr/v20190429
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/landIce/day/licalvf/gr/v20190429
whereas the config you're referencing has this:
input:
- /g/data/ik11/inputs/access-om3/0.x.0/1deg/share # shared grids and topography
- /g/data/ik11/inputs/access-om3/0.x.0/1deg/mom # grids, ICs etc
- /g/data/ik11/inputs/access-om3/0.x.0/1deg/cice # grids, ICs etc
- /g/data/ik11/inputs/access-om3/0.x.0/share/meshes/JRA55do-ESMFmesh.nc # mesh for JRA55-do stream
- /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0 # datm and drof JRA55-do streams data
In your case you definitely need to use a path to JRA55 with the specific version encoded (e.g. v20190429
), otherwise who knows what you'll end up with as the forcing.
payu setup
v1.0.19 produces mis-formattedmanifests/input.yaml
in the MOM6-CICE6 iaf config: https://github.com/COSIMA/MOM6-CICE6/blob/1deg_jra55do_iaf/manifests/input.yaml#L19-L20