Dear colleagues.
In the latest version of ROMS, sea ice module appeared in /ROMS/Nonlinear/SeaIce.
For successfully compile ROMS, it is necessary to define the following CPP options:
#define AVERAGES /* use if writing out NLM time-averaged data */
#define ICE_MODEL /* to activate sea-ice model ...
Search found 8 matches
- Wed Jan 29, 2025 5:34 am
- Forum: ROMS Ice
- Topic: sea ice in Version 4.3
- Replies: 0
- Views: 5903
- Tue Mar 19, 2024 1:52 am
- Forum: ROMS Problems
- Topic: Vertical velocity
- Replies: 0
- Views: 10327
Vertical velocity
Which direction of vertical velocity is positive?
- Thu Apr 29, 2021 9:56 am
- Forum: ROMS Problems
- Topic: problems with increasing the number of processors
- Replies: 2
- Views: 2904
Re: problems with increasing the number of processors
*.h, *.in and *.bash files are attached.
system info:
Supermicro SYS-6029P-WTRT
Intel® Xeon Gold 6152
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 85
model name : Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz
stepping : 4
microcode : 0x200005e
cpu MHz : 1000.651
cache size : 30976 KB ...
system info:
Supermicro SYS-6029P-WTRT
Intel® Xeon Gold 6152
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 85
model name : Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz
stepping : 4
microcode : 0x200005e
cpu MHz : 1000.651
cache size : 30976 KB ...
- Sun Apr 25, 2021 3:32 am
- Forum: ROMS Problems
- Topic: problems with increasing the number of processors
- Replies: 2
- Views: 2904
problems with increasing the number of processors
Dear Colleagues. Can anyone suggest what the problem might be.
When i use 60 proc or less, for example:
mpirun -np 60 romsM jes.in
it work well.
when i increase the number of processors, for example: mpirun -np 70 romsM jes.in
result is:
Program received signal SIGSEGV: Segmentation fault ...
When i use 60 proc or less, for example:
mpirun -np 60 romsM jes.in
it work well.
when i increase the number of processors, for example: mpirun -np 70 romsM jes.in
result is:
Program received signal SIGSEGV: Segmentation fault ...
- Sun Oct 11, 2015 7:39 pm
- Forum: ROMS Problems
- Topic: no output history files
- Replies: 0
- Views: 3010
no output history files
During the work ROMS write the log file, but do not write restart and historical files.
-.in file is the follow:
! Application title.
TITLE = Okhotsk Sea, 10 km resolution
! C-preprocessing Flag.
MyAppCPP = SAKHALIN3
! Input variable information file name. This file needs to be ...
-.in file is the follow:
! Application title.
TITLE = Okhotsk Sea, 10 km resolution
! C-preprocessing Flag.
MyAppCPP = SAKHALIN3
! Input variable information file name. This file needs to be ...
- Mon Oct 17, 2011 7:23 pm
- Forum: ROMS Bugs
- Topic: error while reading global attribute
- Replies: 2
- Views: 4687
error while reading global attribute
i used ROMS/TOMS Framework: September 23, 2011
when i submit the job i reseived following:
.................................................................
LBC_GETATT - error while reading global attribute: NLM_LBC
in input file: /home/jaguar/data1/pfayman/initial_2008_10_2.nc
call from ...
when i submit the job i reseived following:
.................................................................
LBC_GETATT - error while reading global attribute: NLM_LBC
in input file: /home/jaguar/data1/pfayman/initial_2008_10_2.nc
call from ...
- Wed Aug 31, 2011 5:29 pm
- Forum: ROMS Bugs
- Topic: big barotropic Courant Number
- Replies: 2
- Views: 3046
Re: big barotropic Courant Number
no problem with initial and boundary conditions - all ini and bound data take from netcdf files
next massage after Courant numbers in log files:
NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(File: initial_2008_10_2.nc, Rec=0001, Index=1)
- free-surface
(Min = -1.63539832E-02 ...
next massage after Courant numbers in log files:
NLM: GET_STATE - Read state initial conditions, t = 0 00:00:00
(File: initial_2008_10_2.nc, Rec=0001, Index=1)
- free-surface
(Min = -1.63539832E-02 ...
- Wed Aug 31, 2011 4:53 pm
- Forum: ROMS Bugs
- Topic: big barotropic Courant Number
- Replies: 2
- Views: 3046
big barotropic Courant Number
log file shows
Minimum X-grid spacing, DXmin = 1.73851754E+00 km
Maximum X-grid spacing, DXmax = 2.22556255E+00 km
Minimum Y-grid spacing, DYmin = 2.00000000E+00 km
Maximum Y-grid spacing, DYmax = 2.00000000E+00 km
Minimum Z-grid spacing, DZmin = 3.75000000E-01 m
Maximum Z-grid spacing, DZmax ...
Minimum X-grid spacing, DXmin = 1.73851754E+00 km
Maximum X-grid spacing, DXmax = 2.22556255E+00 km
Minimum Y-grid spacing, DYmin = 2.00000000E+00 km
Maximum Y-grid spacing, DYmax = 2.00000000E+00 km
Minimum Z-grid spacing, DZmin = 3.75000000E-01 m
Maximum Z-grid spacing, DZmax ...