Andrew Kiss

I thought about automatically setting the column width, but I've decided it doesn't suit my purposes, as the gap is too large in MOM input.nml, and auto-width also runs the...

Yes, it's a formatting setting, the same as `sort` and those properties you listed. I could have a look at making `min_colwidth` a property when I have a spare moment...

I don't have an opinion either way re. argument vs. property, just so long as the functionality is available somehow to my application in `nmltab`.

great, thanks @marshallward

There's an attempt to make improved bathymetry underway - see https://github.com/COSIMA/access-om2/issues/158#issuecomment-669624837

Can we close this issue? - this has been fixed in `/g/data/ik11/inputs/access-om2/input_20201022/` - see https://github.com/COSIMA/access-om2/issues/158#issuecomment-698758041

Russ also [commented](https://arccss.slack.com/archives/CC78YM9EE/p1621999024012500) > After the first run it seems to sort itself out. I note that there was a change in outputting surface conservative temp for cycle 2 and...

This issue _doesn't_ occur at the start of cycle 2 `/g/data/cj50/access-om2/raw-output/access-om2-01/01deg_jra55v140_iaf_cycle2/output244/ocean/ocean-2d-surface_temp-1-monthly-min-ym_1958_01.nc` so there's definitely something fishy about the cycle2-3 transition

These min and max dailies from the start of cycle 3 show this `pot_temp` issue affects only the first time sample `/g/data/cj50/access-om2/raw-output/access-om2-01/01deg_jra55v140_iaf_cycle3/output488/ocean/ocean-2d-surface_pot_temp-1-daily-min-ym_1958_01.nc` `/g/data/cj50/access-om2/raw-output/access-om2-01/01deg_jra55v140_iaf_cycle3/output488/ocean/ocean-2d-surface_pot_temp-1-daily-max-ym_1958_01.nc` And there seems to be no problem...

Aha, thanks @russfiedler, sounds like that will fix this issue, and also https://github.com/COSIMA/access-om2/issues/235 I guess from the code that we should leave `field_table` as it is for the standard configurations...