IMPORTANT: Updated input multi-file capabities

[arango]

Multi-files are allowed in ROMS for several input fields. That is, the time records for a particular input field can be split into several NetCDF files. For example, we can have in ocean.in:

     BRYNAME == ../../Data/g/gom_nwa_bry_2006_g.nc |
                ../../Data/g/gom_nwa_bry_2007_g.nc |
                ../../Data/g/gom_nwa_bry_2008_g.nc |
                ../../Data/g/gom_nwa_bry_2009_g.nc |
                ../../Data/g/gom_nwa_bry_2010_g.nc |
                ../../Data/g/gom_nwa_bry_2011_g.nc |
                ../../Data/g/gom_nwa_bry_2012_g.nc


     NFFILES == 9                          ! number of unique forcing files

     FRCNAME == ../../Data/Forcing/gom_sms_era.nc    \
                ../../Data/Forcing/gom_shflux_era.nc \
                ../../Data/Forcing/gom_swflux_era.nc \
                ../../Data/Forcing/gom_swrad_era.nc  \
                ../../Data/g/gom_sst_g.nc            \
                ../../Data/g/gom_dqdsst_g.nc         \
                ../../Data/g/gom_rivers_g.nc         \
                ../../Data/g/gom_tides_g.nc          \
                ../../Data/g/gom_waves_2006_g.nc     |
                ../../Data/g/gom_waves_2007_g.nc     |
                ../../Data/g/gom_waves_2008_g.nc     |
                ../../Data/g/gom_waves_2009_g.nc     |
                ../../Data/g/gom_waves_2010_g.nc     |
                ../../Data/g/gom_waves_2011_g.nc     |
                ../../Data/g/gom_waves_2012_g.nc

The multi-file strategy is useful when splitting input data (climatology, boundary, forcing) time records into several files (say monthly, annual, etc). In this case, each multiple file entry line needs to be ended by the vertical bar (|) symbol, as shown above.

In the past, we needed to start the multi-file list with the file that includes or contains the initialization time. This is kind of problematic when restarting the model in a different time period not contained in the first file on the list.

A new routine, check_multifile.F, is introduced to initialize several parameters in the file information structures (BRY, CLM, FRC) so the appropriate file is selected during initialization or restart regardless of the file list. There is no need to edit ocean.in, if restarting on a different time period.

I also included logic in routine lbc_report to check how the user sets periodic boundary conditions. Periodic boundary conditions involve two opposite boundary edges: western and eastern edges for west-east periodic boundary conditions and northern and southern edges for north-south periodic boundary conditions. Recently, a user reported in the forum setting south-east periodic boundary conditions, which is completely wrong.