Store key binaries on JASMIN

[jpolton]

Figure out what key binaries need to be archived:

• domain_cfg.nc file(s)
• tarball of forcing fields?
• ...

Store them on JASMIN

[jpolton]

I propose:

/gws/nopw/j04/jmmp_collab/CO9_AMM15/DOMAIN/
coordinates.nc
bathymetry.nc
domain_cfg.nc
README << echo "These are the coordinates and bathymetry file that make the Multi Envelope domain_cfg.nc file"

All three of these files are useful for development

[jpolton]

@davbyr I think that you are the /gws/nopw/j04/jmmp_collab/CO9_AMM15 owner so will have to add the files.

[endaodea]

Created SUBDIR to contain GEBCO (EMODNET) 2020 bathymetry files and SF12 51 level config files based on them.
Theses files have negative bathymetry and a reference height of 10 m above MSL.

Bathy Files are under:
/gws/nopw/j04/jmmp_collab/AMM15/GATHER_EXPERIMENTAL_EMODNET_GEBCO_DOMAIN_CFG/INPUT_BATHY

Domain CFG files:
/gws/nopw/j04/jmmp_collab/AMM15/GATHER_EXPERIMENTAL_EMODNET_GEBCO_DOMAIN_CFG

of theses the merge Mostly GEBCO one looks best in tidal results to date.
Its very smooth in the WAD zones which for now is a good thing.

No pre-smoothing has been applied yet which is likely to be a small overall effect though may have some HPG implications.
Also are straight from interpolation of SRC bathy rather then box meaning, though box meaning version didn't produce huge differences.

Will look int Mike's prefilter , it requires having N iterations * M order of filter extra points around the domain to be smoothed and thus needs a wider coordinates file to go with it and them make a final cut out into the AMM15 domain.