ocean_vgrid.nc at 1 and 0.25 not compatible with single precision topog.nc

[aekiss]

Related to #161,
/g/data/ik11/inputs/access-om2/input_20200530/mom_1deg/ocean_vgrid.nc and
/g/data/ik11/inputs/access-om2/input_20200530/mom_025deg/ocean_vgrid.nc
(which are identical) are only suitable for use with double-precision topography.

/g/data/ik11/inputs/access-om2/input_20200530/mom_1deg/topog.nc and
/g/data/ik11/inputs/access-om2/input_20200530/mom_025deg/topog.nc are double-precision, so this doesn't cause problems in practice with the current configuration, but would be worth fixing with /scratch/v45/raf599/bathymetry/tools/float_vgrid to avoid problems in case single-precision topography is used in future configurations.

[aekiss]

Closing - fixed in /g/data/ik11/inputs/access-om2/input_20201022.

/g/data/ik11/inputs/access-om2/input_20201022/mom_1deg/topog.nc and
/g/data/ik11/inputs/access-om2/input_20201022/mom_025deg/topog.nc
are now single-precision, but their generation scripts
https://github.com/COSIMA/make_1deg_topo/tree/db7b546 and
https://github.com/COSIMA/make_025deg_topo/tree/37274b2
have automatically generated compatible ocean_vgrid.nc files
/g/data/ik11/inputs/access-om2/input_20201022/mom_1deg/ocean_vgrid.nc and
/g/data/ik11/inputs/access-om2/input_20201022/mom_025deg/ocean_vgrid.nc