Problems with tidal input for a surf zone application

General scientific issues regarding ROMS

Moderators: arango, robertson

Post Reply
Message
Author
nirnimesh
Posts: 27
Joined: Tue Sep 11, 2007 6:57 pm
Location: University of Washington
Contact:

Problems with tidal input for a surf zone application

#1 Unread post by nirnimesh »

Hello Everybody

I am using a coupled ROMS_SWAN application for surf zone.

ROMS Version
240
I know this is an older version and latest svn update is around 470. But the reason to use this version is to compare my model results to a set of older model results from ROMS (Version 240)

Domain Description:
Cross-shore Width- 250m
Alongshore Width- 200m
Depth- -2 - 6m

Cppdefs.h options

Code: Select all

 Activated C-preprocessing Options:

  MYRTLEBEACH        Myrtle Beach Experiment 2005
  ANA_BSFLUX         Analytical kinematic bottom salinity flux.
  ANA_BTFLUX         Analytical kinematic bottom temperature flux.
  ANA_FSOBC          Analytical free-surface boundary conditions.
  ANA_M2OBC          Analytical 2D momentum boundary conditions.
  ANA_SSFLUX         Analytical kinematic surface salinity flux.
  ANA_STFLUX         Analytical kinematic surface temperature flux.
  ASSUMED_SHAPE      Using assumed-shape arrays.
  DIAGNOSTICS_UV     Computing and writing momentum diagnostic terms.
  DJ_GRADPS          Parabolic Splines density Jacobian (Shchepetkin, 2002).
  DOUBLE_PRECISION   Double precision arithmetic.
  EAST_FSGRADIENT    Eastern edge, free-surface, gradient condition.
  EAST_M2FLATHER     Eastern edge, 2D momentum, Flather condition.
  EAST_M3GRADIENT    Eastern edge, 3D momentum, gradient condition.
  EAST_TGRADIENT     Eastern edge, tracers, gradient condition.
  FSOBC_REDUCED      Using free-surface data in reduced physics condtions
  GLS_MIXING         Generic Length-Scale turbulence closure.
  KANTHA_CLAYSON     Kantha and Clayson stability function formulation.
  MASKING            Land/Sea masking.
  MCT_LIB            Using Model Coupling Toolkit library.
  MIX_S_UV           Mixing of momentum along constant S-surfaces.
  MPI                MPI distributed-memory configuration.
  NEARSHORE_MELLOR   Nearshore RAdiation Stress Terms.
  NONLINEAR          Nonlinear Model.
  !NONLIN_EOS        Linear Equation of State for seawater.
  NS_PERIODIC        North-South periodic boundaries.
  N2S2_HORAVG        Horizontal smoothing of buoyancy and shear.
  OUT_DOUBLE         Double precision output fields in NetCDF files.
  POWER_LAW          Power-law shape time-averaging barotropic filter.
  PROFILE            Time profiling activated .
  K_GSCHEME          Third-order upstream advection of TKE fields.
  RAMP_TIDES         Ramping tidal forcing for one day.
  !RST_SINGLE        Double precision fields in restart NetCDF file.
  SOLVE3D            Solving 3D Primitive Equations.
  SPLINES            Conservative parabolic spline reconstruction.
  [b]SSH_TIDES          Add tidal elevation to SSH climatology.[/b]
  SSW_BBL            Styles and Glenn Bottom Boundary Layer - modified.
  SSW_CALC_ZNOT      Internal computation of bottom roughness.
  SWAN_COUPLING      Two-way SWAN/ROMS coupling.
  THREE_GHOST        Using three Ghost Points in halo regions.
  TS_MPDATA          Recursive flux corrected MPDATA 3D advection of tracers.
  UV_ADV             Advection of momentum.
  UV_U3HADVECTION    Third-order upstream horizontal advection of 3D momentum.
  UV_C4VADVECTION    Fourth-order centered vertical advection of momentum.
  [b]UV_TIDES           Add tidal currents to 2D momentum climatologies.[/b]
  UV_VIS2            Harmonic mixing of momentum.
  VAR_RHO_2D         Variable density barotropic mode.
  WAVES_OCEAN        Two-way wave-ocean models coupling.
  WESTERN_WALL       Wall boundary at Western edge.
  WET_DRY            Wetting and drying activated.
The model compiles smoothly, but on executing the code, I get following error:

ERRORS

Code: Select all

 Coupled Input File name = ../RUNFILES/coupling_myrtlebeach.in

 Model Coupling Parallel Threads:

   Ocean Model MPI nodes:   000 - 000
   Waves Model MPI nodes:   001 - 003


   Ocean Export: bath:SSH:Ubar:Vbar
   Waves Export: Wdir:Wamp:Wlen:Wptop:Wpbot:Wdiss:Wbrk:Wubot


 Process Information:

 Node #  0 (pid=   28064) is active.

 Model Input Parameters:  ROMS/TOMS version 3.0  
                          Sunday - June 13, 2010 - 11:32:51 AM
 -----------------------------------------------------------------------------

 Myrtle Beach Experiment 2005

 Operating system : Linux
 CPU/hardware     : x86_64
 Compiler system  : pgi
 Compiler command : /opt/pgi/linux86-64/7.2-3/mpi/mpich/bin/mpif90
 Compiler flags   :  -O3 -tp k8-64 -Mfree

 Input Script  : ../RUNFILES/ocean_myrtlebeach.in

 SVN Root URL  : https://www.myroms.org/svn/src/trunk
 SVN Revision  : exported

 Local Root    : /home/kumar/ROMS/Projects/MyrtleBeach/Camelot/Case1/CODE
 Header Dir    : /home/kumar/ROMS/Projects/MyrtleBeach/Camelot/Case1/RUNFILES
 Header file   : myrtlebeach.h
 Analytical Dir: /home/kumar/ROMS/Projects/MyrtleBeach/Camelot/Case1/RUNFILES

 Resolution, Grid 01: 0140x0039x015,  Parallel Nodes:   1,  Tiling: 001x001

Physical Parameters, Grid: 01
 =============================

     109400  ntimes          Number of timesteps for 3-D equations.
      5.000  dt              Timestep size (s) for 3-D equations.
         20  ndtfast         Number of timesteps for 2-D equations between
                               each 3D timestep.
          1  ERstr           Starting ensemble/perturbation run number.
          1  ERend           Ending ensemble/perturbation run number.
          0  nrrec           Number of restart records to read from disk.
          T  LcycleRST       Switch to recycle time-records in restart file.
        450  nRST            Number of timesteps between the writing of data
                               into restart fields.
          1  ninfo           Number of timesteps between print of information
                               to standard output.
          T  ldefout         Switch to create a new output NetCDF file(s).
        720  nHIS            Number of timesteps between the writing fields
                               into history file.
          1  ntsDIA          Starting timestep for the accumulation of output
                               time-averaged diagnostics data.
        720  nDIA            Number of timesteps between the writing of
                               time-averaged data into diagnostics file.
 5.0000E-02  visc2           Horizontal, harmonic mixing coefficient (m2/s)
                               for momentum.
 5.0000E-06  Akt_bak(01)     Background vertical mixing coefficient (m2/s)
                               for tracer 01: temp
 5.0000E-05  Akv_bak         Background vertical mixing coefficient (m2/s)
                               for momentum.
 5.0000E-06  Akk_bak         Background vertical mixing coefficient (m2/s)
                               for turbulent energy.
 5.0000E-06  Akp_bak         Background vertical mixing coefficient (m2/s)
                               for turbulent generic statistical field.
      3.000  gls_p           GLS stability exponent.
      1.500  gls_m           GLS turbulent kinetic energy exponent.
     -1.000  gls_n           GLS turbulent length scale exponent.
 7.6000E-06  gls_Kmin        GLS minimum value of turbulent kinetic energy.
 1.0000E-12  gls_Pmin        GLS minimum value of dissipation.
 5.4770E-01  gls_cmu0        GLS stability coefficient.
 1.4400E+00  gls_c1          GLS shear production coefficient.
 1.9200E+00  gls_c2          GLS dissipation coefficient.
-4.0000E-01  gls_c3m         GLS stable buoyancy production coefficient.
 1.0000E+00  gls_c3p         GLS unstable buoyancy production coefficient.
 1.0000E+00  gls_sigk        GLS constant Schmidt number for TKE.
 1.3000E+00  gls_sigp        GLS constant Schmidt number for PSI.
   1400.000  charnok_alpha   Charnok factor for Zos calculation.
      0.500  zos_hsig_alpha  Factor for Zos calculation using Hsig(Awave).
      0.250  sz_alpha        Factor for Wave dissipation surface tke flux .
    100.000  crgban_cw       Factor for Craig/Banner surface tke flux.
 3.0000E-04  rdrg            Linear bottom drag coefficient (m/s).
 3.0000E-03  rdrg2           Quadratic bottom drag coefficient.
 5.0000E-03  Zob             Bottom roughness (m).
 2.0000E-02  Zos             Surface roughness (m).
 5.0000E-01  Dcrit           Minimum depth for wetting and drying (m).
 0.0000E+00  theta_s         S-coordinate surface control parameter.
 0.0000E+00  theta_b         S-coordinate bottom  control parameter.
      0.000  Tcline          S-coordinate surface/bottom layer width (m) used
                               in vertical coordinate stretching.
   1025.000  rho0            Mean density (kg/m3) for Boussinesq approximation.
      0.000  dstart          Time-stamp assigned to model initialization (days).
      0.000  tide_start      Reference time origin for tidal forcing (days).
       0.00  time_ref        Reference time for units attribute (yyyymmdd.dd)
 0.0000E+00  Tnudg(01)       Nudging/relaxation time scale (days)
                               for tracer 01: temp
 0.0000E+00  Znudg           Nudging/relaxation time scale (days)
                               for free-surface.
 0.0000E+00  M2nudg          Nudging/relaxation time scale (days)
                               for 2D momentum.
 0.0000E+00  M3nudg          Nudging/relaxation time scale (days)
                               for 3D momentum.
 0.0000E+00  obcfac          Factor between passive and active
                               open boundary conditions.
     10.000  T0              Background potential temperature (C) constant.
     30.000  S0              Background salinity (PSU) constant.
   1027.000  R0              Background density (kg/m3) used in linear Equation
                               of State.
 1.7000E-04  Tcoef           Thermal expansion coefficient (1/Celsius).
 7.6000E-04  Scoef           Saline contraction coefficient (1/PSU).
      1.000  gamma2          Slipperiness variable: free-slip (1.0) or 
                                                    no-slip (-1.0).

 Minimum X-grid spacing, DXmin =  1.50000000E-03 km
 Maximum X-grid spacing, DXmax =  1.50000000E-03 km
 Minimum Y-grid spacing, DYmin =  5.00000000E-03 km
 Maximum Y-grid spacing, DYmax =  5.00000000E-03 km
 Minimum Z-grid spacing, DZmin = -1.67549030E-01 m
 Maximum Z-grid spacing, DZmax =  3.77319840E-01 m

 Minimum barotropic Courant Number =  4.43647023E-02
 Maximum barotropic Courant Number =  1.29657294E+00
 Maximum Coriolis   Courant Number =  7.29000000E-04


 NLM: GET_STATE - Read state initial conditions,             t =     0 00:00:00
                   (File: mbcamelot_init1_06112010.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 =  1.00000000E+01 Max =  1.00000000E+01)
                - sediment median grain diameter size
                   (Min =  1.00000000E-04 Max =  1.00000000E-04)
                - sediment median grain density
                   (Min =  2.65000000E+03 Max =  2.65000000E+03)
                - sediment median grain settling velocity
                   (Min =  5.00000000E-03 Max =  5.00000000E-03)
                - sediment median critical erosion stress
                   (Min =  1.20000000E-01 Max =  1.20000000E-01)
                - bottom ripple length
                   (Min =  1.00000000E-01 Max =  1.00000000E-01)
                - bottom ripple height
                   (Min =  1.00000000E-02 Max =  1.00000000E-02)
    GET_NGFLD   - tidal period
                   (Min =  1.80642857E+04 Max =  5.05800000E+05)

    GET_CYCLE - starting time for variable: tide_period
             is greater than current model time. 
             TMIN =        140.5000  TDAYS =        100.0000

 Elapsed CPU time (seconds):

 Node   #  0 CPU:       0.308
 Total:                 0.308

 Nonlinear model elapsed time profile:

  Reading of input data ............................         0.001  ( 0.3896 %)
  2D/3D coupling, vertical metrics .................         0.003  ( 0.8510 %)
  Omega vertical velocity ..........................         0.002  ( 0.5000 %)
  Equation of state for seawater ...................         0.002  ( 0.7348 %)
                                              Total:         0.008    2.4754

 Nonlinear model message Passage profile:

  Message Passage: 2D halo exchanges ...............         0.000  ( 0.0344 %)
  Message Passage: 3D halo exchanges ...............         0.000  ( 0.0118 %)
  Message Passage: data broadcast ..................         0.000  ( 0.1095 %)
  Message Passage: data reduction ..................         0.000  ( 0.0130 %)
  Message Passage: data scattering..................         0.005  ( 1.4624 %)
                                              Total:         0.005    1.6311

 All percentages are with respect to total time =            0.308

 ROMS/TOMS - Output NetCDF summary for Grid 01:

 ROMS/TOMS - Input error ............. exit_flag:   2


  ERROR: Abnormal termination: NetCDF INPUT.
 REASON: No error   
The model correctly reads my netcdf file for tidal variables as the maximum and minimum tidal periods are correct. The model complains because the starting time of tidal period is 140.5 hours which is greater than 100 hours. What I am not able to understand is that what determines the quantity TDAYS=100 hours, and how can I change it. I followed the code in get_cycle.F, which then relates to get_2dfld.F and get_state.F. It seems that the quantity TDAYS is defined as smday in get_cycle.F, which eventually is derived from get_2dfld.F and get_state.F as tdays(ng) and INPtime, respectively. If someone, can shed some light into the problem, it would be very helpful :) .

Some more information if required:
Tidal Forcing: (This may not correspond to standard tidal components, as this information has been derived using FFT Analysis on sea surface elevation data)


Amp(m) Phase(Deg) Period(Hours)
0.2303 228.9618 140.5000
0.0766 347.4678 70.2500
0.0611 316.0689 46.8333
0.0802 248.1601 35.1250
0.0638 125.4203 28.1000
0.2120 329.5090 23.4167
0.0852 1.2454 20.0714
0.0503 341.5776 17.5625
0.0680 19.3410 15.6111
0.1478 38.6202 14.0500
0.6580 54.8690 12.7727
0.3569 240.2042 11.7083
0.1691 243.7095 10.8077
0.1204 243.0664 10.0357
0.0693 230.6243 9.3667
0.0410 249.1811 8.7813
0.0674 248.5063 8.2647
0.0565 286.3071 7.8056
0.0495 265.3247 7.3947
0.0271 243.4153 7.0250
0.0257 295.2783 6.6905
0.0304 246.4545 6.3864
0.0247 275.4480 6.1087
0.0303 253.8828 5.8542
0.0248 272.1815 5.6200
0.0187 277.0954 5.4038
0.0242 289.7153 5.2037
0.0219 279.7107 5.0179

ncdump -h of my tidal input:

Code: Select all

nc = netcdf('mbcamelot_tide1_06112010.nc', 'noclobber');
if isempty(nc), return, end
 
%% Global attributes:
 
nc.type = ncchar(''Gridpak file'');
nc.gridid = ncchar(''combined grid'');
nc.history = ncchar(''Created by "create_tidal_forcing_modified" on 13-Jun-2010 11:35:24'');
nc.CPP-options = ncchar(''DCOMPLEX, DBLEPREC, NCARG_32, PLOTS,'');
 
%% Dimensions:
 
nc('xi_psi') = 141;
nc('xi_rho') = 142;
nc('xi_u') = 141;
nc('xi_v') = 142;
nc('eta_psi') = 40;
nc('eta_rho') = 41;
nc('eta_u') = 41;
nc('eta_v') = 40;
nc('tide_period') = 28;
 
%% Variables and attributes:
 
nc{'tide_period'} = ncdouble('tide_period'); %% 28 elements.
nc{'tide_period'}.long_name = ncchar(''tide angular period'');
nc{'tide_period'}.units = ncchar(''hours'');
nc{'tide_period'}.field = ncchar(''scalar'');
 
nc{'tide_Ephase'} = ncdouble('tide_period', 'eta_rho', 'xi_rho'); %% 163016 elements.
nc{'tide_Ephase'}.long_name = ncchar(''tidal elevation phase angle'');
nc{'tide_Ephase'}.units = ncchar(''degrees'');
nc{'tide_Ephase'}.field = ncchar(''scalar'');
 
nc{'tide_Eamp'} = ncdouble('tide_period', 'eta_rho', 'xi_rho'); %% 163016 elements.
nc{'tide_Eamp'}.long_name = ncchar(''tidal elevation amplitude'');
nc{'tide_Eamp'}.units = ncchar(''meter'');
nc{'tide_Eamp'}.field = ncchar(''scalar'');
 
nc{'tide_Cphase'} = ncdouble('tide_period', 'eta_rho', 'xi_rho'); %% 163016 elements.
nc{'tide_Cphase'}.long_name = ncchar(''tidal current phase angle'');
nc{'tide_Cphase'}.units = ncchar(''degrees'');
nc{'tide_Cphase'}.field = ncchar(''scalar'');
 
nc{'tide_Cangle'} = ncdouble('tide_period', 'eta_rho', 'xi_rho'); %% 163016 elements.
nc{'tide_Cangle'}.long_name = ncchar(''tidal current inclination angle'');
nc{'tide_Cangle'}.units = ncchar(''degrees'');
nc{'tide_Cangle'}.field = ncchar(''scalar'');
 
nc{'tide_Cmin'} = ncdouble('tide_period', 'eta_rho', 'xi_rho'); %% 163016 elements.
nc{'tide_Cmin'}.long_name = ncchar(''minimum tidal current'');
nc{'tide_Cmin'}.units = ncchar(''meter/second'');
nc{'tide_Cmin'}.field = ncchar(''scalar'');
 
nc{'tide_Cmax'} = ncdouble('tide_period', 'eta_rho', 'xi_rho'); %% 163016 elements.
nc{'tide_Cmax'}.long_name = ncchar(''maximum tidal current'');
nc{'tide_Cmax'}.units = ncchar(''meter/second'');
nc{'tide_Cmax'}.field = ncchar(''scalar'');
 
endef(nc)
close(nc)

User avatar
kate
Posts: 4089
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

Re: Problems with tidal input for a surf zone application

#2 Unread post by kate »

I know you don't want to upgrade, but you should at least download today's ROMS to see if the problem has been fixed in the mean time.

nirnimesh
Posts: 27
Joined: Tue Sep 11, 2007 6:57 pm
Location: University of Washington
Contact:

Re: Problems with tidal input for a surf zone application

#3 Unread post by nirnimesh »

Hi Kate

Thanks for the reply. I did update to latest ROMS(v470) and tried to do a simulation. The error I get in that case is:

Code: Select all

 Maximum barotropic Courant Number =  1.29657294E+00
 Maximum Coriolis   Courant Number =  7.29000000E-04


 NLM: GET_STATE - Read state initial conditions,             t =     0 00:00:00
                   (File: mbcamelot_init1_06112010.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 =  1.00000000E+01 Max =  1.00000000E+01)
                - sediment median grain diameter size
                   (Min =  1.00000000E-04 Max =  1.00000000E-04)
                - sediment median grain density
                   (Min =  2.65000000E+03 Max =  2.65000000E+03)
                - sediment median grain settling velocity
                   (Min =  5.00000000E-03 Max =  5.00000000E-03)
                - sediment median critical erosion stress
                   (Min =  1.20000000E-01 Max =  1.20000000E-01)
                - bottom ripple length
                   (Min =  1.00000000E-01 Max =  1.00000000E-01)
                - bottom ripple height
                   (Min =  1.00000000E-02 Max =  1.00000000E-02)
    GET_NGFLD   - tidal period
                   (Min =  1.80642857E+04 Max =  5.05800000E+05)

 NETCDF_GET_FVAR_0D - error while reading variable:  tide_period
                      in input file:  ../../Forcing/mbcamelot_tide1_06112010.nc
                      call from:  get_cycle.F

 GET_2DFLD   - error while reading variable: tide_period   at TIME index =    0

 Elapsed CPU time (seconds):

 Node   #  0 CPU:       0.360
 Total:                 0.360

 Nonlinear model elapsed time profile:

  Reading of input data ............................         0.000  ( 0.0014 %)
  2D/3D coupling, vertical metrics .................         0.003  ( 0.7168 %)
  Omega vertical velocity ..........................         0.002  ( 0.4283 %)
  Equation of state for seawater ...................         0.003  ( 0.7520 %)
                                              Total:         0.007    1.8985

 Nonlinear model message Passage profile:

  Message Passage: 2D halo exchanges ...............         0.000  ( 0.0229 %)
  Message Passage: 3D halo exchanges ...............         0.000  ( 0.0117 %)
  Message Passage: data broadcast ..................         0.001  ( 0.2170 %)
  Message Passage: data reduction ..................         0.000  ( 0.0106 %)
  Message Passage: data scattering..................         0.005  ( 1.4116 %)
                                              Total:         0.006    1.6738

 All percentages are with respect to total time =            0.360

 ROMS/TOMS - Output NetCDF summary for Grid 01:

 ROMS/TOMS - Input error ............. exit_flag:   2


 ERROR: Abnormal termination: NetCDF INPUT.
 REASON: NetCDF: Index exceeds dimension bound    
I think the error remains same, but the message is presented in a different way.

User avatar
kate
Posts: 4089
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

Re: Problems with tidal input for a surf zone application

#4 Unread post by kate »

It's giving you a better idea of where the problem is. However, we still don't know what problem it's having. What I would do is edit mod_netcdf.F. It already checks the error status after each netcdf call and reports - that's what you are seeing. What is missing is a report on which netcdf error you got. Here's what I would do:

Code: Select all

          IF (status.ne.nf90_noerr) THEN 
            WRITE (stdout,10) TRIM(myVarName), TRIM(ncname),            &
     &                        TRIM(SourceFile)
            PRINT *, trim(nf90_strerror(status))
            exit_flag=2
            ioerror=status
          END IF
where the print statement is new.

I see you have 28 tidal constituents, with a wider range of periods than I have. I kind of remember something about ROMS expecting only semi-diurnal and diurnal tides, but I don't know where that came from. Is it in the detiding software?

nirnimesh
Posts: 27
Joined: Tue Sep 11, 2007 6:57 pm
Location: University of Washington
Contact:

Re: Problems with tidal input for a surf zone application

#5 Unread post by nirnimesh »

Hello Kate

As suggested, I added a print command in mod_netcdf.F. After recompiling and executing the code, I get following error:

Code: Select all

 NLM: GET_STATE - Read state initial conditions,             t =     0 00:00:00
                   (File: mbcamelot_init1_06112010.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 =  1.00000000E+01 Max =  1.00000000E+01)
                - sediment median grain diameter size
                   (Min =  1.00000000E-04 Max =  1.00000000E-04)
                - sediment median grain density
                   (Min =  2.65000000E+03 Max =  2.65000000E+03)
                - sediment median grain settling velocity
                   (Min =  5.00000000E-03 Max =  5.00000000E-03)
                - sediment median critical erosion stress
                   (Min =  1.20000000E-01 Max =  1.20000000E-01)
                - bottom ripple length
                   (Min =  1.00000000E-01 Max =  1.00000000E-01)
                - bottom ripple height
                   (Min =  1.00000000E-02 Max =  1.00000000E-02)
    GET_NGFLD   - tidal period
                   (Min =  1.80642857E+04 Max =  5.05800000E+05)

 NETCDF_GET_FVAR_0D - error while reading variable:  tide_period
                      in input file:  ../../Forcing/mbcamelot_tide1_06112010.nc
                      call from:  get_cycle.F
 NetCDF: Index exceeds dimension bound

 GET_2DFLD   - error while reading variable: tide_period   at TIME index =    0

 Elapsed CPU time (seconds):

 Node   #  0 CPU:       0.408
 Total:                 0.408

 Nonlinear model elapsed time profile:

  Reading of input data ............................         0.000  ( 0.0012 %)
  2D/3D coupling, vertical metrics .................         0.003  ( 0.6312 %)
  Omega vertical velocity ..........................         0.002  ( 0.3758 %)
  Equation of state for seawater ...................         0.003  ( 0.6613 %)
                                              Total:         0.007    1.6696

 Nonlinear model message Passage profile:

  Message Passage: 2D halo exchanges ...............         0.000  ( 0.0263 %)
  Message Passage: 3D halo exchanges ...............         0.000  ( 0.0107 %)
  Message Passage: data broadcast ..................         0.001  ( 0.1876 %)
  Message Passage: data reduction ..................         0.000  ( 0.0088 %)
  Message Passage: data scattering..................         0.005  ( 1.2615 %)
                                              Total:         0.006    1.4949

 All percentages are with respect to total time =            0.408

 ROMS/TOMS - Output NetCDF summary for Grid 01:

 ROMS/TOMS - Input error ............. exit_flag:   2


 ERROR: Abnormal termination: NetCDF INPUT.
 REASON: NetCDF: Index exceeds dimension bound                                           
Killed by signal 2.
Killed by signal 2.
Killed by signal 2.
p0_10306: (468.039062) net_send: could not write to fd=4, errno = 32
The extra output I get after adding print statements is:
NetCDF: Index exceeds dimension bound

I see you have 28 tidal constituents, with a wider range of periods than I have. I kind of remember something about ROMS expecting only semi-diurnal and diurnal tides, but I don't know where that came from. Is it in the detiding software?

I didn't use a tidal analysis (like T_TIDE) on my sea surface elevation data. Since I want an exact representation of sea surface as was observed during data collection period (a near shore experiment in Myrtle Beach, SC), I performed an FFT analysis on the sea surface elevation, and took all the dominant components necessary for exact representation. Thus in other words, I don't have standard K1 and M2 tides.

I have used a similar strategy before too, and that worked fine. So I don't think we necessarily need to provide only diurnal and semi-diurnal tide. The problem here seems to be one of the long term trends with a period of 140.5 hours. If I remove this part of my tidal constituent, the model would not blow up. But in doing so, I will not be able to exactly match my sea surface elevation data (differences of 20 cm). Somewhere there seems to be a limit to maximum possible tide period, which in my case is 100 hours.

Thanks a lot for looking into this problem. Please let me know if i can provide you more details required to figure out this problem.

Nirnimesh

User avatar
kate
Posts: 4089
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

Re: Problems with tidal input for a surf zone application

#6 Unread post by kate »

Please let me know if i can provide you more details required to figure out this problem.
I think the next steps have to be yours. You know there is a dimension mismatch. What are the dimensions it is expecting? Where did it get them? It's time for you to start throwing in more print statements or finding a debugger that works for you.

The purpose of this forum is for us to share information. Maybe I've seen things (or someone else has) and can give a quick fix, but sometimes that's not the case. Sometimes you have to figure it out and report back for the rest of us.

nirnimesh
Posts: 27
Joined: Tue Sep 11, 2007 6:57 pm
Location: University of Washington
Contact:

Re: Problems with tidal input for a surf zone application

#7 Unread post by nirnimesh »

Kate

I am looking into dimension mismatch cause, and will let you know if I can find a fix to the problem.

Thanks
Nirnimesh

Post Reply