[MITgcm-support] strange mnc behavior
ryan.abernathey at gmail.com
Sun Dec 4 15:40:32 EST 2016
Often this types of errors occur when restarting a crashed/aborted
simulation when the target netcdf file is already present in the output
directory. One needs to be sure to erase any existing netcdf files
corresponding with the Iter0.
Have you ruled out this possibility?
On Sun, Dec 4, 2016 at 2:28 PM, Ruth Musgrave <rmusg at mit.edu> wrote:
> when I configure my data.diagnostics to output each variable to a
> different file, I encounter the following error after 53 snapshots have
> already been written to the file phiHyd.0000052596.t001.nc:
> (PID.TID 0000.0001) *** ERROR *** MNC ERROR: dimension 'Z' does not exist
> for file 'phiHyd.0000052596.t001.nc’
> the error is in agreement with ncdump -h, which reports the dimensions
> present in the file phiHyd.0000052596.t001.nc are:
> T = UNLIMITED ; // (53 currently)
> Zmd000020 = 20 ;
> X = 240 ;
> Y = 46 ;
> The vertical dimension is always recorded in my netcdf output as
> “Zmd000020” or “Zld000020”, depending on the variable - I only recall ever
> seeing a dimension “Z” in the “state*.nc” outputs. I am not sure why the
> code suddenly starts looking for that dimension half way through the run.
> The error occurs at the same timestep whether I start the simulation from a
> pickup or from t=0.
> When I configure my data.diagnostics to output all of my variables to the
> same file, it completes my simulation without error.
> This is not critically important as for the time being I’ve found a work
> around, but in case someone knows what’s going on it would be good to
> understand. I’m attaching two versions of my data.diagnostics:
> data.diagnosticsWORKS and data.diagnosticsFAILS. Hopefully the naming
> convention is self explanatory.
> Thanks in advance for any clues.
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MITgcm-support