GithubHelp home page GithubHelp logo

Comments (4)

yvikhlya avatar yvikhlya commented on July 26, 2024

Hi Nic,

I had this problem with 0.25 model, because large restart files were split into parts and were not read properly when the model restarted. I solved this problem by increasing maximum file size in mpp_parameter.F90

from mom5.

nichannah avatar nichannah commented on July 26, 2024

Hi Yuri, thank you, this is very helpful. Can you elaborate on what you mean by the restart files not being read properly? How do you know this, was there a warning/error? Can you point me to any particular bit of code? If the model is not doing this properly and not throwing an error then it's a bug we should fix.

from mom5.

yvikhlya avatar yvikhlya commented on July 26, 2024

I don't have a version which had this problem under my hand unfortunately. As far as I remember, restarts larger than 4Gb were split into several pieces, with one variable in each, as I recall like
ocean_density.res.nc
ocean_density.res.nc01
ocean_density.res.nc02
...
When model restarted, only first file was read, other variables were bootstrapped. I suspect, it is because of how fms treats these suffixes in file names (did not investigate this actually). The model did not crash. It did printout a warning, but I don't have it now.

from mom5.

marshallward avatar marshallward commented on July 26, 2024

We may not be seeing the issue because we usually use the layout
parameters, which tend to produce much smaller restart files (typically one
per-PE), and whose bit-repro probably handled correctly.

This particular problem might be solvable (or at least avoidable) by
removing the -Duse_netcdf3 declarative, which would allow large restarts.

But I guess it's a problem if MOM's autmatic file-splitting of 32-bit
netCDF files not reproducible?

On Sat, Aug 1, 2015 at 7:09 AM, Yury Vikhliaev [email protected]
wrote:

I don't have a version which had this problem under my hand unfortunately.
As far as I remember, restarts larger than 4Gb were split into several
pieces, with one variable in each, as I recall like
ocean_density.res.nc
ocean_density.res.nc01
ocean_density.res.nc02
...
When model restarted, only first file was read, other variables were
bootstrapped. I suspect, it is because of how fms treats these suffixes in
file names (did not investigate this actually). The model did not crash. It
did printout a warning, but I don't have it now.


Reply to this email directly or view it on GitHub
#114 (comment).

from mom5.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.