Ocean Modeling Discussion

Dear feroda,
May I have a look at your modified code files that have been modified to include Bv ?
I struggled for a long time and don't know how to do it.

Thank God and you If get reply from you! If Ok, send it to my Gmail joe211010@gmail.com. Thank you again.
Best wishes!
Joe

Yes, it's done by Wang et al., JGR 2010 based on Qiao et al, JPO 2004. I added it as a one of the switches (option) for vertical turbulent mixing :arrow: (lmd_vmix) to the CPP options list (ROMS 3.7), and is running now for the Mid-Atlantic Bight application :idea: . To extract wave induced mixing ...

Dear, How to output SST from ROMS ? I am confused with SST from ROMS, because I didn't see the option to output SST in the roms.in. The only option I see is Aout(idTvar) == T T ! temp, salt temperature and salinity. If I have output temp(lon,lat,vertical_level) with vertical_level=35, is temp(:,:,35 ...

Looking back at the original post, i see that the SST from NCEP and the SST from ROMS are very different. So the 'coupling' is not the issue. It seems that the issue is "how did you set up the initial conditions for ROMS?" If ROMS is starting out 2-3 degrees cooler, then you cant expect similar ...

I have interpolated forcing, initial, boundary and climatological file into roms grid. The key point is whether rotate wind and ocean current velocity.

Dear arango, Kate, and wilkin, I have looked into many discussions about the grid angle and the rotation of wind and ocean current velocity , but got more confused ! 1. When I prepare the wind forcing, should I rotate the wind direction from geometrical eastward/northward to grid xi/eta in my ...

Hello,
The ROMS blowing up after about 44days. I tried #define WET_DRY, but it did not work. I uploaded my .h, .in, and log file. Could you please help me out?

Dear Kate, I noticed that you have ever tried METROMS. When I build and run roms standalone , everything gose well. But If I mpirun oceanG after build ROMS coupled with CICE (i.e. the METROMS https://github.com/metno/metroms), it turned forrtl: severe (174): SIGSEGV, segmentation fault occurred ...

kate wrote: > Just had a segmentation fault that I can't figure out at all: > [code]forrtl: severe (174): SIGSEGV, segmentation fault occurred > Image PC Routine Line Source > > oceanG 00000000035D46E5 Unknown Unknown Unknown > oceanG 00000000035D2307 Unknown Unknown Unknown > oceanG ...

Recompile your code in debug mode (un-comment the USE_DEBUG line in your build_roms.sh or build_roms.csh ), then run your model again with the resulting romsG (instead of romsM or romsS) executable. That will hopefully give you an idea where in the code the segfault is coming from to narrow down ...

Hello everyone, I got an error in the terminal, while I running the MetROMS. However, the log file does not contain any error massage. The following error massage are showing in the terminal: MPI_ABORT was invoked on rank 26 in communicator MPI_COMM_WORLD with errorcode 128. NOTE: invoking MPI ...

Inside ROMS, each variable can have its own time, no problem. The preferred method (last I was aware) is that each variable in the netcdf file should point to the appropriate time variable through the time attribute. This will override the varinfo.dat file. In terms of units, I wouldn't count on ...

This one is not the fault of the Makefile, but rather a bug. Looking at mod_forces, I have: # ifdef SHORTWAVE real(r8), pointer :: srflx(:,:) # ifndef ANA_SRFLUX real(r8), pointer :: srflxG(:,:,:) # endif # ifdef ALBEDO real(r8), pointer :: albedo(:,:) # ifdef ICE_MODEL real(r8), pointer :: albedo ...

I think you are confusing dimensions and coordinate variables. It does not matter whether a variable is dimensioned salt_time or mud_time. That conveys no information to ROMS about the time coordinate . Which time coordinate to use to interpret the index into the time dimension can be specified ...

Hi, I also had the same problem when building the ROMS-Ice code, but only with the multi processor building: (./build_bash -j 8 ) I believe as Kate mentioned, the dependency order has to be taken care of. However, if I use single process to build, I get no problems with building. I chose not to ...

So the dependency list is wrong and doesn't include the needs of the ice model. I never used Hernan's build system, so there must be something missing in his Makefile. I looked in his makefile and he's pointing to sea ice modules under ROMS/Nonlinear/SeaIce. Maybe if you move the ice routines to ...

You need to rebuild the dependency list. Some things need to be compiled before other things. The easiest way to do this is "make clean" or removing the build directory or whatever works for how you build the model. Dear Kate, I set "clean=1" in the build_roms.bash file. I also removed the ...

Is this what you are asking about? read_icepar.f90: remark #5133: The input stream is empty Are you sure you turned on the ice model? I checked and my boundary file only has ocean_time. That's how I set up my varinfo.dat: 'zeta_west' ! Input 'free-surface western boundary condition' 'meter' ! [m ...

What is more, dose the following output (while compile in debug mode) matter? ./build_roms.bash -j 24 > build.log svn: '.' is not a working copy svn: '.' is not a working copy svn: '.' is not a working copy svn: '.' is not a working copy svn: '.' is not a working copy svn: '.' is not a working copy ...

I forgot to tell you that the boundary file is prepared well, and the variable: ocean_time is present in the boundary. romsG couldn't find ocean_time because we comment out FFLAGS += -heap-arrays . But I don't know how to solve it. Thank you in advance ! $ ncdump -v ocean_time roms_bry.nc netcdf ...

get_data_ 218 get_data.f90 What is it reading here? Are you sure it's the boundary file? It just read salinity climatology - should it read temperature climatology next? I would run it in the debugger or add a print statement to that line you highlighted. I don't know what's going on. Note: all the ...

The way ROMS is compiled, you view the .F file, then an intermediate .f90 file is created off in some build directory. It is those line numbers you need to look at: read_phypar_ 1839 read_phypar.f90 You need to make sure you have an ocean.in that's compatible with the github ROMS, also varinfo.dat ...

1. I'm not really supporting that code any more. 2. Yes, turning on the ice cpp flag is all that's needed. 3. You'll get a more useful model output on seg fault if you recompile in debug mode. 4. Your problem is probably in the ocean.in, with the ice code needing different options. 5. I suspect you ...

1. I'm not really supporting that code any more. 2. Yes, turning on the ice cpp flag is all that's needed. 3. You'll get a more useful model output on seg fault if you recompile in debug mode. 4. Your problem is probably in the ocean.in, with the ice code needing different options. 5. I suspect you ...

Help: Hello everyone, especially Kate, could you please help me? I run my case using the ROMS from svn well. Now, I want to using the SeaIce, so I download ROMS with SeaIce from github as Kate suggested. Before the ice module was added, I tested ocean module alone first (the version from github ...

Dear users I try to run ROMS in my domain. I run ROMS with rivers, fluxes, and also the initial conditions in the upwelling test case. Now I try to add ice into the model but I do not understand how to do it although I review this forum. In this case, I have some questions. Firstly, ROMS have this ...

what did you do to solve the problem ?I am faced with the same problem too question about seagrid and mex first of all, I added "matlab" (downloaded from https://www.myroms.org/svn/src/matlab) folder to the work path in matlab. Second, I added "mexrect","mexinside","mexsepelid" path again. third ...