Changes between Initial Version and Version 1 of Ticket #269


Ignore:
Timestamp:
01/22/09 18:34:40 (15 years ago)
Author:
arango
Comment:

Yes, good catch! I fixed this logic in a more robust way by inquiring the number of tidal constituents for all nested grids in mod_tides.F. I cleaned get_idata.F to use the parallel interface of mod_netcdf.F. Similar logic is done in mod_sources.F to inquire the number of point sources Nsrc(ng) from input NetCDF file.

I also corrected a parallel bug in inp_par.F when either W4DVAR or W4DPSAS is activated. The nTLM(ng)=nHIS(ng) was inside of a code that it is only executed by the master thread. Many thanks to Brian Powell for reporting this problem.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #269

    • Property Resolution → Fixed
    • Property Status new → closed

  • Ticket #269 – Description

    initial v1  
    1010}}}
    1111
    12 The problem seems to be that in ROMS/Nonlinear/get_idata.F at line 101, NTC(ng) (i.e. the number of tidal consttituents) is set to 0
     12The problem seems to be that in '''ROMS/Nonlinear/get_idata.F''' at line 101, '''NTC(ng)''' (i.e. the number of tidal consttituents) is set to 0
    1313{{{
    1414      IF (iic(ng).eq.0) THEN
    … …  
    2525and it never acquires any other value. (In my application it should be 1.) Therefore all the subsequent read requests return 0 data values.
    2626
    27 As an ad hoc fix, setting NTC(ng) to 1 in get_idata.F causes sensible tidal forcing data to be read from the file
     27As an ad hoc fix, setting '''NTC(ng)''' to 1 in '''get_idata.F''' causes sensible tidal forcing data to be read from the file
    2828{{{
    2929    GET_NGFLD   - tidal period
    … …  
    3434                   (Min =  2.47094957E+00 Max =  5.79200999E+00)
    3535}}}
    36 I don't know how NTC(ng) should get its value, however.
     36I don't know how '''NTC(ng)''' should get its value, however.