problems about UV_TIDES

General scientific issues regarding ROMS

Moderators: arango, robertson

Post Reply
Message
Author
fanzhongya
Posts: 10
Joined: Tue Dec 01, 2009 3:53 pm
Location: SCIES,China

problems about UV_TIDES

#1 Unread post by fanzhongya »

dear all

I run a real case of tide, using tpxo model data as my OBC data. When I add the UV_TIDES to the boundary,it can't run.If using 'undef UV_TIDES',it can work.
the OBC in cpp.h of my simulation as followed

/*Open boundary options*/
#define RAMP_TIDES

#define SSH_TIDES

#define ANA_FSOBC
#define ANA_M2OBC

#define EAST_FSCHAPMAN
#define SOUTH_FSCHAPMAN
#define NORTH_FSCHAPMAN

#define UV_TIDES
#define EAST_M2FLATHER
#define SOUTH_M2FLATHER
#define NORTH_M2FLATHER

please help me!THANKS

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

Re: problems about UV_TIDES

#2 Unread post by kate »

What error do you get?

fanzhongya
Posts: 10
Joined: Tue Dec 01, 2009 3:53 pm
Location: SCIES,China

Re: problems about UV_TIDES

#3 Unread post by fanzhongya »

kate wrote:What error do you get?
Thanks kate! Adding the UV_TIDES to the cpp,the first step is NaN.When I put 'undef UV_TIDES',the model can run regularly.

the log file as followed



INITIAL: Configuring and initializing forward nonlinear model ...


Vertical S-coordinate System:

level S-coord Cs-curve at_hmin over_slope at_hmax

10 0.0000000 0.0000000 0.000 0.000 0.000
9 -0.1000000 -0.1000000 -0.164 -4.029 -7.895
8 -0.2000000 -0.2000000 -0.327 -8.058 -15.789
7 -0.3000000 -0.3000000 -0.491 -12.087 -23.684
6 -0.4000000 -0.4000000 -0.655 -16.117 -31.579
5 -0.5000000 -0.5000000 -0.818 -20.146 -39.473
4 -0.6000000 -0.6000000 -0.982 -24.175 -47.368
3 -0.7000000 -0.7000000 -1.145 -28.204 -55.263
2 -0.8000000 -0.8000000 -1.309 -32.233 -63.157
1 -0.9000000 -0.9000000 -1.473 -36.262 -71.052
0 -1.0000000 -1.0000000 -1.636 -40.291 -78.947

Time Splitting Weights: ndtfast = 5 nfast = 7

Primary Secondary Accumulated to Current Step

1 0.0119306869089341 0.2000000000000000 0.0119306869089341 0.2000000000000000
2 0.0475049776008205 0.1976138626182131 0.0594356645097547 0.3976138626182131
3 0.1047629417620785 0.1881128670980491 0.1641986062718331 0.5857267297162622
4 0.1760826281731955 0.1671602787456334 0.3402812344450286 0.7528870084618955
5 0.2416469636634478 0.1319437531109943 0.5819281981084765 0.8848307615728898
6 0.2602974116474964 0.0836143603783047 0.8422256097559728 0.9684451219511945
7 0.1577743902440273 0.0315548780488054 1.0000000000000000 0.9999999999999999

ndtfast, nfast = 5 7 nfast/ndtfast = 1.40000

Centers of gravity and integrals (values must be 1, 1, approx 1/2, 1, 1):

1.000000000000 1.084198606272 0.542099303136 1.000000000000 1.000000000000

Power filter parameters, Fgamma, gamma = 0.28400 0.00000

Minimum X-grid spacing, DXmin = 9.97024264E-02 km
Maximum X-grid spacing, DXmax = 1.26877789E+01 km
Minimum Y-grid spacing, DYmin = 3.82419589E-02 km
Maximum Y-grid spacing, DYmax = 1.04691316E+01 km
Minimum Z-grid spacing, DZmin = 1.63638680E-01 m
Maximum Z-grid spacing, DZmax = 7.89465720E+00 m

Minimum barotropic Courant Number = 2.91297304E-02
Maximum barotropic Courant Number = 9.71812920E-01
Maximum Coriolis Courant Number = 4.83202820E-03


NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(File: yz_4.5_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 = 1.50000000E+01 Max = 1.50000000E+01)
- salinity
(Min = 3.00000000E+01 Max = 3.00000000E+01)
GET_NGFLD - tidal period
(Min = 4.30820424E+04 Max = 9.67260960E+04)
GET_2DFLD - tidal elevation amplitude
(Min = 0.00000000E+00 Max = 1.54013845E+00)
GET_2DFLD - tidal elevation phase angle
(Min = 2.80177559E-05 Max = 6.28314944E+00)
GET_2DFLD - tidal current inclination angle
(Min = 0.00000000E+00 Max = 6.28316976E+00)
GET_2DFLD - tidal current phase angle
(Min = 0.00000000E+00 Max = 6.28317597E+00)
GET_2DFLD - maximum tidal current, ellipse major axis
(Min = 0.00000000E+00 Max = 3.56873957E+00)
GET_2DFLD - minimum tidal current, ellipse minor axis
(Min = -1.79233992E-02 Max = 6.56115950E-03)
GET_NGFLD - river runoff XI-positions at RHO-points
(Min = 1.00000000E+00 Max = 1.00000000E+00)
GET_NGFLD - river runoff ETA-positions at RHO-points
(Min = 1.15000000E+02 Max = 1.22000000E+02)
GET_NGFLD - river runoff direction
(Min = 0.00000000E+00 Max = 0.00000000E+00)
GET_NGFLD - river runoff mass transport vertical profile
(Min = 2.00000000E-02 Max = 1.50000000E-01)
GET_NGFLD - river runoff flag
(Min = 2.00000000E+00 Max = 2.00000000E+00)
GET_NGFLD - river runoff mass transport, t = 0 00:00:00
(Rec=0001, Index=2, File: yz_4.13_rvr.nc)
(Tmin= 0.0000 Tmax= 120.5000)
(Min = 3.71700000E+03 Max = 3.71700000E+03)
GET_NGFLD - river runoff salinity, t = 0 00:00:00
(Rec=0001, Index=2, File: yz_4.13_rvr.nc)
(Tmin= 0.0000 Tmax= 120.5000)
(Min = 1.00000000E+00 Max = 1.00000000E+00)

Maximum grid stiffness ratios: rx0 = 1.189571E-01 (Beckmann and Haidvogel)
rx1 = 2.260186E+00 (Haney)


Initial basin volumes: TotVolume = 6.89161401944466E+12 m3
MinVolume = 1.90331673766976E+04 m3
MaxVolume = 9.61658699965394E+08 m3
Max/Min = 5.05254160241746E+04

NL ROMS/TOMS: started time-stepping: (Grid: 01 TimeSteps: 00000001 - 00086400)
GET_NGFLD - river runoff mass transport, t = 0 12:00:00
(Rec=0002, Index=1, File: yz_4.13_rvr.nc)
(Tmin= 0.0000 Tmax= 120.5000)
(Min = 3.71700000E+03 Max = 3.71700000E+03)
GET_NGFLD - river runoff salinity, t = 0 12:00:00
(Rec=0002, Index=1, File: yz_4.13_rvr.nc)
(Tmin= 0.0000 Tmax= 120.5000)
(Min = 1.00000000E+00 Max = 1.00000000E+00)

STEP Day HH:MM:SS KINETIC_ENRG POTEN_ENRG TOTAL_ENRG NET_VOLUME

0 0 00:00:00 0.000000E+00 2.482132E+02 2.482132E+02 6.960395E+12
DEF_HIS - creating history file: cjk_in/output/cjk_his.nc
WRT_HIS - wrote history fields (Index=1,1) into time record = 0000001
1 0 00:01:00 NaN NaN NaN NaN



Elapsed CPU time (seconds):

Node # 0 CPU: 1.168
Node # 2 CPU: 1.229
Node # 1 CPU: 1.235
Node # 4 CPU: 1.232
Node # 9 CPU: 1.228
Node # 5 CPU: 1.229
Node # 10 CPU: 1.237
Node # 6 CPU: 1.227
Node # 12 CPU: 1.226
Node # 11 CPU: 1.229
Node # 13 CPU: 1.229
Node # 14 CPU: 1.226
Total: 19.612

Nonlinear model elapsed time profile:

Initialization ................................... 8.920 (45.4805 %)
Reading of input data ............................ 3.838 (19.5718 %)
Processing of input data ......................... 0.067 ( 0.3416 %)
Computation of vertical boundary conditions ...... 0.009 ( 0.0459 %)
Computation of global information integrals ...... 0.086 ( 0.4384 %)
Writing of output data ........................... 3.491 (17.8027 %)
Model 2D kernel .................................. 0.812 ( 4.1397 %)
Tidal forcing .................................... 0.070 ( 0.3569 %)
2D/3D coupling, vertical metrics ................. 0.209 ( 1.0655 %)
Omega vertical velocity .......................... 0.117 ( 0.5965 %)
Equation of state for seawater ................... 0.312 ( 1.5906 %)
GLS vertical mixing parameterization ............. 0.978 ( 4.9860 %)
3D equations right-side terms .................... 0.139 ( 0.7086 %)
3D equations predictor step ...................... 0.222 ( 1.1318 %)
Pressure gradient ................................ 0.108 ( 0.5506 %)
Harmonic mixing of tracers, S-surfaces ........... 0.083 ( 0.4231 %)
Harmonic stress tensor, S-surfaces ............... 0.076 ( 0.3875 %)
Corrector time-step for 3D momentum .............. 0.199 ( 1.0145 %)
Corrector time-step for tracers .................. 1.302 ( 6.6378 %)
Total: 21.038 107.2700

Nonlinear model message Passage profile:

Message Passage: 2D halo exchanges ............... 0.364 ( 1.8558 %)
Message Passage: 3D halo exchanges ............... 0.487 ( 2.4828 %)
Message Passage: 4D halo exchanges ............... 0.262 ( 1.3357 %)
Message Passage: data broadcast .................. 6.956 (35.4679 %)
Message Passage: data reduction .................. 0.034 ( 0.1733 %)
Message Passage: data gathering .................. 1.041 ( 5.3071 %)
Message Passage: data scattering.................. 3.872 (19.7449 %)
Message Passage: boundary data gathering ......... 0.020 ( 0.1020 %)
Total: 13.036 66.4695

All percentages are with respect to total time = 19.612

ROMS/TOMS - Output NetCDF summary for Grid 01:
number of time records written in HISTORY file = 00000001

Analytical header files used:

ROMS/Functionals/ana_btflux.h
ROMS/Functionals/ana_fsobc.h
ROMS/Functionals/ana_m2obc.h
ROMS/Functionals/ana_smflux.h
ROMS/Functionals/ana_stflux.h

ROMS/TOMS - Blows up ................ exit_flag: 1


MAIN: Abnormal termination: BLOWUP.
Node # 3 CPU: 1.235
Node # 8 CPU: 1.239
Node # 15 CPU: 1.233
Node # 7 CPU: 1.213
Last edited by fanzhongya on Wed Apr 14, 2010 1:41 am, edited 1 time in total.

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

Re: problems about UV_TIDES

#4 Unread post by kate »

It's not obvious to me what's wrong. Have you tried a shorter timestep?

fanzhongya
Posts: 10
Joined: Tue Dec 01, 2009 3:53 pm
Location: SCIES,China

Re: problems about UV_TIDES

#5 Unread post by fanzhongya »

kate wrote:It's not obvious to me what's wrong. Have you tried a shorter timestep?
I tried it in dt and ndtfast,but it still didn't run in the first time step.

! Time-Stepping parameters.

NTIMES == 86400
DT == 1.0d0
NDTFAST == 10

How can I search the reasons for this?

kate,thanks for your advance.

wuhe
Posts: 15
Joined: Mon Dec 22, 2008 5:29 pm
Location: national ocean techniqual centre

Re: problems about UV_TIDES

#6 Unread post by wuhe »

1、did you add obc by changing ANA_* files? you d better make a forcing file with cdl
2、i have encountered the problem before, cause some NaN is included in OBC, maybe you have the same problem, i guess.

fanzhongya
Posts: 10
Joined: Tue Dec 01, 2009 3:53 pm
Location: SCIES,China

Re: problems about UV_TIDES

#7 Unread post by fanzhongya »

wuhe wrote:1、did you add obc by changing ANA_* files? you d better make a forcing file with cdl
2、i have encountered the problem before, cause some NaN is included in OBC, maybe you have the same problem, i guess.
thanks wuhe,you are right!

I examined the data in OBC, finding some NaN is included.I changed it, then it can run well.

Post Reply