Hi,
I am new to ROMS. I am using ocean_benchmark1.in. My ROMS code is compiled with openmp. I used Intel Compiler. My NtileI is 30 and NtileJ is 6. Lm is 512 and 128.
My output is (tail)
ROMS/TOMS - Output NetCDF summary for Grid 01:
Analytical header files used:
ROMS/Functionals/ana_btflux.h
ROMS/Functionals/ana_grid.h
ROMS/Functionals/ana_initial.h
ROMS/Functionals/ana_nudgcoef.h
ROMS/Functionals/ana_smflux.h
ROMS/Functionals/ana_stflux.h
ROMS/Functionals/ana_vmix.h
ROMS/TOMS - Blows up ................ exit_flag: 1
MAIN: Abnormal termination: BLOWUP.
For ocean_benchmark2.in also, I am getting same output. Do I have to change any values in the input other than NtileI and NtileJ?
Thanks for your help in advance.
-
Ravi
Problem of blowing up.
Re: Problem of blowing up.
I would look further up in the output for possible error messages.
Have you tried other values of NtileI and NtileJ?
Have you tried other values of NtileI and NtileJ?
Re: Problem of blowing up.
Hi Kate,
Sorry for the late reply.
I tried other Tile sizes. Working smoothly.
I have seen some interesting cases, with ocean_benchmark3.in of grid size 2048x256, with NTIMES more than 49 are blowing up abnormally.
I have tried with openmp enabled oceanG binary and oceanO with 32 and 48 Cores with different TILE Sizes( For 48 - 64x4, 48x2, 48x4; For 32, - 16x4, 64x4, 32x2, 32x4 )
How NTIMES parameter matters in this case?
It would be great if you suggest any solution.
Thanks
Ravi
Sorry for the late reply.
I tried other Tile sizes. Working smoothly.
I have seen some interesting cases, with ocean_benchmark3.in of grid size 2048x256, with NTIMES more than 49 are blowing up abnormally.
I have tried with openmp enabled oceanG binary and oceanO with 32 and 48 Cores with different TILE Sizes( For 48 - 64x4, 48x2, 48x4; For 32, - 16x4, 64x4, 32x2, 32x4 )
How NTIMES parameter matters in this case?
It would be great if you suggest any solution.
Thanks
Ravi
Re: Problem of blowing up.
Hi Kate,
I found the root cause of the abnormal termination of my input file. I have changed Vstretching parameter value. This is causing blownup.I do not know, How this parameter effects.
Thanks
ravi
I found the root cause of the abnormal termination of my input file. I have changed Vstretching parameter value. This is causing blownup.I do not know, How this parameter effects.
Thanks
ravi