Conversion period in netCDF files does not equal model resubmission period

The pt file (from which the netCDF conversion runs) - I think the conversion happens on the frequency of this file renewal (currently 1 month), but this could be different from the model resubmission period, and then it becomes difficult to tie together the model timestep and the data. It would be better if the pt file has the same renewal as the resubmit period, but I don't know how to automate that.

Start by tracing how renewal of the pt file currently triggers netCDF conversion and how the model resubmission period is configured. Define how these schedules should be linked, then verify that the conversion uses the resubmission period and that model timesteps remain traceable in the resulting data.

Written by the indexing model from the issue text.