I updated my ROMS to the newest version recently, with file /Utility/inquiry.F But it could not read in multiple boundary files correctly. Which previously works fine. And the older version has file /Utility/inquire.F
The inquiry.F file could not update the ncid to the second boundary.nc file, it only updates the file name. My current solution is modifying according to the old inquire.F file with the boundary file sections. The climate files may have same situation.
In addition, when restart with the newst version. The model seeks forcing data 1-dt (dt of the forcing data) before the restart time, even there is a data at the restart time. To avoid this, again I modified get_cycle.F according to the old version.
Yan
Could not read in multiple boundary files correctly
- arango
- Site Admin
- Posts: 1367
- Joined: Wed Feb 26, 2003 4:41 pm
- Location: DMCS, Rutgers University
- Contact:
Re: Could not read in multiple boundary files correctly
You need to provide more information. The new inquiry.F was modified to provide the correct transition between annual files.
Re: Could not read in multiple boundary files correctly
According to the log file, the model loaded in the next boundary file name correctly. But the Tmin, Tmax, and ntime reported from get_cycle.F are still from the first boundary file. I noticed this because my next boundary file should have a longer ntime. Chasing down this, I found the ncid used by get_cycle.F still points to the first file.
Yan
Yan