Search found 13 matches
- Mon May 03, 2021 4:35 am
- Forum: ROMS Discussion
- Topic: Blow up ( River run off)
- Replies: 7
- Views: 17806
Re: Blow up ( River run off)
HI, does your model blowup coincide with large freshwater flux from the river ? What are your salinity/ temperature values in the river forcing file ? It is possible that a large freshwater flux leads to problems with the tracer advection scheme due to strong horizontal gradients, this leads to ...
- Fri Dec 06, 2019 3:24 am
- Forum: ROMS Bugs
- Topic: typo in distribute.F
- Replies: 1
- Views: 2041
typo in distribute.F
I belive there is a typo in distribute.F (svn Revision: 990)
1620 # ifdef BOUNDARY_ALLGAHTER
--> should be
# ifdef BOUNDARY_ALLGATHER
Same in lines
1677
1710
1620 # ifdef BOUNDARY_ALLGAHTER
--> should be
# ifdef BOUNDARY_ALLGATHER
Same in lines
1677
1710
- Mon Feb 11, 2019 10:33 pm
- Forum: ROMS Tools and Techniques
- Topic: Soundspeed for ROMS output
- Replies: 4
- Views: 3843
Re: Soundspeed for ROMS output
Thanks guys ! Hernan - OK - I remember having problems with compiling the plotting package in the past due to ncarg library. I'll give it another go. Generally I think it would be nice to decouple the soundspeed calculation from the actual plotting routines and be able to write it into the average ...
- Sun Feb 10, 2019 11:39 pm
- Forum: ROMS Tools and Techniques
- Topic: Soundspeed for ROMS output
- Replies: 4
- Views: 3843
Soundspeed for ROMS output
Hi all,
just wondering if anyone has some code that calculates the soundspeed from ROMS output files ?
Cheers
Frank
just wondering if anyone has some code that calculates the soundspeed from ROMS output files ?
Cheers
Frank
- Tue Sep 11, 2018 5:45 am
- Forum: ROMS Bugs
- Topic: bug in mod_tides.F
- Replies: 1
- Views: 2223
bug in mod_tides.F
mod_tides.F when AVERAGE_DETIDE
line 288
Dmem(ng)=Dmem(ng)+REAL((N(ng)*(2*MTC+1),r8)*size2d
needs
Dmem(ng)=Dmem(ng)+REAL(N(ng)*(2*MTC+1),r8)*size2d
same for line 296, 305
ROMS:
Revision: 921
line 288
Dmem(ng)=Dmem(ng)+REAL((N(ng)*(2*MTC+1),r8)*size2d
needs
Dmem(ng)=Dmem(ng)+REAL(N(ng)*(2*MTC+1),r8)*size2d
same for line 296, 305
ROMS:
Revision: 921
- Wed May 10, 2017 3:38 am
- Forum: ROMS Problems
- Topic: question about detiding
- Replies: 0
- Views: 2001
question about detiding
Hi all, I have been running a ROMS simulation including tides utilizing the ROMS detiding algorithm When I run the simulation over 1.5 month the detided fields display an offset that depends on the averaging period (see attached images). This is mostly visible for temperature. For example when I run ...
- Tue May 09, 2017 5:47 am
- Forum: ROMS Discussion
- Topic: zgrid boundaries in floats output file
- Replies: 1
- Views: 1645
zgrid boundaries in floats output file
Hi all, we are running a ROMS simulation with define FLOATS define FLOAT_VWALK we have 30 vertical layers defined and hence values for zgrid should be between 0, 29. However, the model computes values below zero (up to -400) and greater than 30. This happens mostly in shallow areas related to river ...
- Sun Mar 06, 2016 10:41 pm
- Forum: ROMS Discussion
- Topic: roms river LwSrc problem
- Replies: 8
- Views: 6863
Re: roms river LwSrc problem
thanks - this is very helpful! My simulations using LuvSrc are now very stable. What is the reason of default max_speed set to 20m/s?
- Tue Mar 01, 2016 7:52 pm
- Forum: ROMS Discussion
- Topic: roms river LwSrc problem
- Replies: 8
- Views: 6863
Re: roms river LwSrc problem
Hi Kate thanks for your reply - for the LuvSrc case: I would have thought the model blew up due to violating the speed limit which is caused by large river runoff (btw does roms has a hard-coded speed limit ?). I was able to handle this by increasing river depth (and methods similar as you describe ...
- Tue Mar 01, 2016 7:11 am
- Forum: ROMS Discussion
- Topic: roms river LwSrc problem
- Replies: 8
- Views: 6863
roms river LwSrc problem
Hi all, I am currently experiencing some model behavior associated with LwScr which I dont understand. I am using LwSrc option to include a point river source. This works fine in terms of inflating the cell (as set in step2d_LF_AM3.h). However, the associated vertical tracer flux does drive the ...
- Sat Jun 27, 2015 5:47 am
- Forum: ROMS Discussion
- Topic: weird problem with forcing file
- Replies: 10
- Views: 10887
Re: weird problem with forcing file
Have you checked that the coordinates in your forcing file are sorted from low to high values (i.e. increasing) ?
- Tue Jun 18, 2013 12:37 am
- Forum: ROMS Problems
- Topic: ROMS only runs with NDEFHIS set to zero
- Replies: 7
- Views: 5598
Re: ROMS only runs with NDEFHIS set to zero
Hi all, has there been a solution to this problem ? I am currently having a similar issue with roms-3.6. I can use multiple output files with NDEFHIS=360 (for my particular setting) but not any other number (!), it then gives me the same error as indicated in the thread above. ROMS is trying to ...
- Tue Apr 03, 2012 1:41 am
- Forum: ROMS Discussion
- Topic: forrtl: severe (174): SIGSEGV, segmentation fault occurred
- Replies: 11
- Views: 11096
Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr
Yes, I had the same problem with the Intel 11.x compiler recently. Needed to switch to Intel 10.x or Intel 12.x. The segmentation error only occurred when "define AVERAGES" and writing into average file.
Everything worked fine with other compiler versions...
Everything worked fine with other compiler versions...