error reading forcing file for second grid

[nma]

Dear friends,

Not very sure if the latest version of roms supports the Ngrids=2 option now?
However, I tried a test case and found that it could read all input files related to both grid-01 and grid-02, except the forcing file for grid-02.

Output/Input Files:

Output Restart File: /home/nan7/output_files/rst.nc
Output History File: /home/nan7/output_files/his.nc
Output Averages File: /home/nan7/output_files/avg.nc
Output Diagnostics File: /home/nan7/output_files/dia.nc
Input Grid File: /home/nan7/input_files/sp12_grd41.nc
Input Nonlinear Initial File: /home/nan7/input_files/sp12_ini41.nc
Input Forcing File 01: /home/nan7/input_files/frc.nc
Input Forcing File 02: /home/nan7/input_files/frc5.nc
Input Boundary File: /home/nan7/input_files/sp12_bry.nc
..........................................................................
.........................................................


Output/Input Files:

Output Restart File: /home/nan7/output_files/rst1.nc
Output History File: /home/nan7/output_files/his1.nc
Output Averages File: /home/nan7/output_files/avg1.nc
Output Diagnostics File: /home/nan7/output_files/dia1.nc
Input Grid File: /home/nan7/input_files/nz_grd41.nc
Input Nonlinear Initial File: /home/nan7/input_files/nz_ini.nc

It is clear from above that I could not write distinctly the forcing file for grid-02 and now it is being read as the second forcing file for grid-01.

NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(File: nz110_ini.nc, Rec=0001, Index=1)
- free-surface
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- vertically integrated u-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- vertically integrated v-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- u-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- v-momentum component
(Min = 0.00000000E+00 Max = 0.00000000E+00)
- potential temperature
(Min = 0.00000000E+00 Max = 2.40488720E+01)
- salinity
(Min = 0.00000000E+00 Max = 3.58429680E+01)

NETCDF_OPEN - unable to open existing NetCDF file:
! ! ! �
call from: inquire.F

In ocean.in file, this is how I mentioned the two forcing files corresponding to two different grids:

NFFILES == 2 ! number of forcing files


FRCNAME == /home/nan7/input_files/frc.nc \ ! forcing file for grid-01
/home/nan7/input_files/frc5.nc ! forcing file for grid-02

What changes in above lines could make it read the second grid's forcing file..

Thanks.

[kate]

I reported this bug over here You need to change inp_par.F.

[arango]

Kate, your posting about this is kind of confusing. You are talking about several unrelated things and it was not clear to me what are you taking about it. I read your posting several times. I put this in my to do list. I need to go into the debugger and actually confirm that this is the case. The logic for the multiple files is complicated. I hope to have some time to look at this soon. I am very busy now and involved in a very complex coding... I did not have enough information to accept your patch...

[kate]

Fine, let's see if I can explain it again. I ran into two problems. One described here was solved with my patch. The other is what I was mostly talking about in my post - and I didn't attempt a solution.

[arango]

Yes Kate, you were correct. We need to have the .lt. in IF-conditional in routine load_s2d. I corrected the repository, check the following ticket. Please update.

[nma]

Thanks to Kate and Hernan....After updating, I could make a trial run for atleast few steps...

1 0 00:13:20 8.966520E-05 2.084210E+04 2.084210E+04 2.350473E+17
(158,047,32) 2.678985E-04 1.590547E-02 0.000000E+00 9.298896E-01
1 0 00:02:40 1.532622E-06 1.336160E+04 1.336160E+04 5.187304E+15
(022,008,32) 2.877198E-04 5.197665E-04 0.000000E+00 3.181553E-02
2 0 00:26:40 1.742765E-04 2.084175E+04 2.084175E+04 2.350437E+17
(010,122,32) 1.915468E-03 7.887116E-04 2.492519E+00 1.847082E+00
2 0 00:05:20 8.896836E-06 1.336151E+04 1.336151E+04 5.187304E+15
(059,223,32) 9.544467E-05 9.554407E-05 1.172378E-01 7.451513E-02
3 0 00:40:00 2.557471E-04 2.084144E+04 2.084144E+04 2.350402E+17
(009,123,32) 1.227168E-04 2.498313E-03 1.926935E+00 2.529098E+00
3 0 00:08:00 8.143865E-03 1.336154E+04 1.336154E+04 5.187304E+15
(125,187,32) 3.930792E-05 1.153748E-04 1.388061E-01 2.438632E+00
4 0 00:53:20 3.483751E-04 2.084116E+04 2.084116E+04 2.350370E+17
(009,124,32) 9.831013E-05 1.918998E-03 2.350523E+00 3.066895E+00
4 0 00:10:40 2.482032E-02 1.336145E+04 1.336148E+04 5.187304E+15
(002,002,32) 3.065274E-02 2.864309E-02 4.547360E+00 7.045903E+00
5 0 01:06:40 4.436820E-04 2.084090E+04 2.084090E+04 2.350339E+17
(008,124,32) 9.304311E-05 1.990789E-03 2.622848E+00 2.869953E+00
5 0 00:13:20 1.504767E+00 1.336146E+04 1.336296E+04 5.187304E+15
(002,002,32) 1.202074E-02 3.591759E-02 3.137413E+00 5.762157E+01

Blowing-up: Saving latest model state into RESTART file

WRT_RST - wrote re-start fields (Index=1,2) into time record = 0000001

Blowing-up: Saving latest model state into RESTART file

WRT_RST - wrote re-start fields (Index=2,2) into time record = 0000001

Probably now I need to smoothen the bathymetry for second grid.
regards,
nma

[kate]

I hope you know that the two grids don't currently talk to each other. You can debug them as two independent problems.

[nma]

yes Kate, I recently came to know about the same.
I found that the second grid does not need any boundary data...would you like to comment on that, as we know until now they don't communicate even one-way!
thanks.

[kate]

How are you going to run it without boundary information? You can:

1. Wait for Hernan's nesting.

2. Contact John Warner about his nested option.

3. Run in one-way offline nesting, like we've been doing for years, requiring that you prepare a boundary file from grid one to be used when running grid two. There are Matlab and Python tools for this.

[nma]

..thanks Kate, I got my answer.
regards