Some confusion about the boundary file

[Shuaiyiping]

Dear all,
my bry.nc have NaN in the varibales of zeta_east,zeta_north,zeta_south,and zeta_west.
So in my in file,I closed the free-surface.
LBC(isFsur) == Clo Clo Clo Clo ! free-surface
LBC(isUbar) == Clo Fla Fla Fla ! 2D U-momentum
LBC(isVbar) == Clo Fla Fla Fla ! 2D V-momentum
LBC(isUvel) == Clo Cla Cla Cla ! 3D U-momentum
LBC(isVvel) == Clo Cla Cla Cla ! 3D V-momentum
LBC(isMtke) == Gra Gra Gra Gra ! mixing TKE

LBC(isTvar) == Cla Cla Cla Cla \ ! temperature
Cla Cla Cla Cla ! salinity

! Adjoint-based algorithms can have different lateral boundary
! conditions keywords.

ad_LBC(isFsur) == Clo Clo Clo Clo ! free-surface
ad_LBC(isUbar) == Clo Fla Fla Fla ! 2D U-momentum
ad_LBC(isVbar) == Clo Fla Fla Fla ! 2D U-momentum
ad_LBC(isUvel) == Clo Cla Cla Cla ! 3D U-momentum
ad_LBC(isVvel) == Clo Cla Cla Cla ! 3D V-momentum
ad_LBC(isMtke) == Gra Gra Gra Gra ! mixing TKE

ad_LBC(isTvar) == Cla Cla Cla Cla \ ! temperature
Cla Cla Cla Cla ! salinity


But I still get Blowing-up.
TIME-STEP YYYY-MM-DD hh:mm:ss.ss KINETIC_ENRG POTEN_ENRG TOTAL_ENRG NET_VOLUME
C => (i,j,k) Cu Cv Cw Max Speed

0 0001-01-01 00:00:00.00 2.485765E-04 1.401961E+04 1.401961E+04 5.563019E+15
(59,16,04) 1.085449E-01 0.000000E+00 0.000000E+00 2.072265E+00
DEF_HIS - creating history file, Grid 01: ocean_his.nc
WRT_HIS - wrote history fields (Index=1,1) in record = 0000001
DEF_AVG - creating average file, Grid 01: ocean_avg.nc
DEF_DIAGS - creating diagnostics file, Grid 01: ocean_dia.nc
1 0001-01-01 00:45:00.00 NaN NaN NaN NaN
(00,00,00) 0.000000E+00 0.000000E+00 0.000000E+00 NaN
Found Error: 01 Line: 298 Source: ROMS/Nonlinear/main3d.F
Found Error: 01 Line: 298 Source: ROMS/Drivers/nl_ocean.h

Blowing-up: Saving latest model state into RESTART file

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

Elapsed CPU time (seconds):

Node # 0 CPU: 0.351
Node # 1 CPU: 0.352
Total: 0.703

and I checked my log file and find this:
GET_NGFLD - free-surface eastern boundary condition, 0001-12-12 00:00:00.00
(Grid= 01, Rec=0000012, Index=2, File: croco_bry.nc)
(Tmin= 15.0000 Tmax= 345.0000) t = 345.0000
(Min = NaN Max = NaN)
GET_NGFLD - free-surface southern boundary condition, 0001-12-12 00:00:00.00
(Grid= 01, Rec=0000012, Index=2, File: croco_bry.nc)
(Tmin= 15.0000 Tmax= 345.0000) t = 345.0000
(Min = NaN Max = NaN)
GET_NGFLD - free-surface northern boundary condition, 0001-12-12 00:00:00.00
(Grid= 01, Rec=0000012, Index=2, File: croco_bry.nc)
(Tmin= 15.0000 Tmax= 345.0000) t = 345.0000
(Min = NaN Max = NaN)
GET_NGFLD - free-surface eastern boundary condition, 0001-01-16 00:00:00.00
(Grid= 01, Rec=0000001, Index=1, File: croco_bry.nc)
(Tmin= 15.0000 Tmax= 345.0000) t = 15.0000
(Min = NaN Max = NaN)
GET_NGFLD - free-surface southern boundary condition, 0001-01-16 00:00:00.00
(Grid= 01, Rec=0000001, Index=1, File: croco_bry.nc)
(Tmin= 15.0000 Tmax= 345.0000) t = 15.0000
(Min = NaN Max = NaN)
GET_NGFLD - free-surface northern boundary condition, 0001-01-16 00:00:00.00
(Grid= 01, Rec=0000001, Index=1, File: croco_bry.nc)
(Tmin= 15.0000 Tmax= 345.0000) t = 15.0000
(Min = NaN Max = NaN)




Why I closed the free surface,I still get this. Should I fill out the NaN values in the boundary file? Those NaN values are not alone, the whole matrix of zeta_east,zeta_north,zeta_south,zeta_west are NaN.

[kate]

The Flather condition uses zeta in the ubar term. Either fix your zeta or set it to zero.

[Shuaiyiping]

Thank you very much,kate

[Shuaiyiping]

Hello,kate.I set my zeta into zeros.And it running normally untill 9525 steps after it blowing up.



9513 0001-10-25 06:45:00.00 1.541050E-02 1.402140E+04 1.402142E+04 5.562436E+15
(59,17,20) 1.184031E-01 8.302710E-02 1.927002E+00 3.729171E+00
9514 0001-10-25 07:30:00.00 1.540656E-02 1.402140E+04 1.402142E+04 5.562437E+15
(59,17,19) 1.154813E-01 8.222846E-02 1.928615E+00 3.629425E+00
9515 0001-10-25 08:15:00.00 1.540227E-02 1.402140E+04 1.402142E+04 5.562437E+15
(59,17,19) 1.148758E-01 8.070675E-02 1.965517E+00 3.670237E+00
9516 0001-10-25 09:00:00.00 1.540064E-02 1.402140E+04 1.402142E+04 5.562437E+15
(59,17,19) 1.168241E-01 7.946633E-02 2.015523E+00 3.673641E+00
9517 0001-10-25 09:45:00.00 1.539963E-02 1.402140E+04 1.402142E+04 5.562437E+15
(59,17,19) 1.159784E-01 7.627296E-02 2.009265E+00 3.491694E+00
9518 0001-10-25 10:30:00.00 1.539638E-02 1.402140E+04 1.402142E+04 5.562437E+15
(59,17,20) 1.151301E-01 7.967622E-02 2.029614E+00 3.629846E+00
9519 0001-10-25 11:15:00.00 1.539088E-02 1.402140E+04 1.402142E+04 5.562437E+15
(59,17,20) 1.182182E-01 7.575985E-02 2.083018E+00 3.656241E+00
9520 0001-10-25 12:00:00.00 1.538693E-02 1.402140E+04 1.402142E+04 5.562438E+15
(59,17,20) 1.162398E-01 7.412836E-02 2.117487E+00 3.470595E+00
9521 0001-10-25 12:45:00.00 1.538487E-02 1.402140E+04 1.402142E+04 5.562438E+15
(59,17,20) 1.166021E-01 7.383122E-02 2.080710E+00 3.363347E+00
9522 0001-10-25 13:30:00.00 1.538302E-02 1.402140E+04 1.402142E+04 5.562438E+15
(59,17,20) 1.183279E-01 7.371244E-02 2.107115E+00 3.546257E+00
9523 0001-10-25 14:15:00.00 1.537885E-02 1.402140E+04 1.402142E+04 5.562438E+15
(59,17,20) 1.172144E-01 7.334491E-02 2.092832E+00 3.460003E+00
9524 0001-10-25 15:00:00.00 1.537479E-02 1.402140E+04 1.402142E+04 5.562438E+15
(59,17,20) 1.130312E-01 7.129245E-02 2.035680E+00 3.370243E+00
9525 0001-10-25 15:45:00.00 1.537169E-02 1.402140E+04 1.402142E+04 5.562438E+15
(59,17,20) 1.149655E-01 7.355530E-02 2.005018E+00 3.375108E+00
Found Error: 01 Line: 298 Source: ROMS/Nonlinear/main3d.F
Found Error: 01 Line: 298 Source: ROMS/Drivers/nl_ocean.h

Blowing-up: Saving latest model state into RESTART file

WRT_RST - wrote re-start fields (Index=1,2) in record = 0000003

Elapsed CPU time (seconds):



I checked the restart file, and I find out that there is a value in temp that is very low,-67.8517. However the value in my input boundary seems normal. when I close the esat boudary,the model will run a longer time,then blow up. I am a little confused about it.

[kate]

This is where you have to do more detective work. I wrote up what I know here.

[Shuaiyiping]

Thanks,kate.I shortened my time-steps, and it works normally.