Ocean Modeling Discussion

Thank you for your quick reply,

I tried both methods and both produced the same error, with ROMS unable to find the wind forcing input files.

Additionally, I should say that I have been running this application successfully for several months and I also scoured by ocean.in file for errant characters like tabs, etc.

Hi all, I have several yearly forcing files for SUSTR and SVSTR. The model runs fine with an individual year ( the first file ) but will not run when I introduce the continuation mark ( | ) and the next two years of files. I follow the syntax for multiple time-split files in ocean.in but It still do...

Just to follow up I think it was indeed a problem with SWAN's real*4 type interger. The SWAN dt starts to shift by 4 seconds back and forth as the computation time in seconds reaches the limits of accuracy for the real*4 (7 sig. digits). In my current set up, I solved this by treating the restart in...

John- Thank you for getting back to me. To answer your questions and concerns: I'm using the Rutgers code, not COAWST. The app is restarted at 20080101.00000 and produces bad results. I have tested it again with everything the same except that I remove the HOTSTART command and let SWAN initialize an...

I'm running into something curious during an extended period runs of ROMS & SWAN. If you have a moment can you please make a suggestion about the following? Let me say first that I am trying to run a coupled ROMS/SWAN application over a 7 year period. To make SWAN output manageable, I've opted t...

Hi All, I've been working with a coupled ROMS/SWAN application. I had initially tested the application for over a 1 month period forcing ROMS with river, tide, and wind while forcing SWAN with wind at 2hr intervals. This worked fine on 6,12, & 24 cpu's for each model. I recently moved on to exte...

Is there a possible work around for this? I attempting the same thing using openmpi and having the same error. ROMS/Bin/cpp_clean /lustre/work/kukulka_lab/rjenkins/projects/inlet_test/Build/mp_exchange.f90 cd /lustre/work/kukulka_lab/rjenkins/projects/inlet_test/Build; /opt/shared/openmpi/1.4.4-pgi/...

After much trial and error, The error disappeared once I swapped the gfortran compiler in favor of pgi.
Although, I have no idea why.

Hi All, I'm attempting to set up and run a realistic application of my own using the most recent version of ROMS. I have all of the necessary netcdf files for grid and forcing (tide, winds & river discharge). The build goes smoothly but upon running I receive the following error: Model Input Par...

Hi mashinde,

Did you ever find and solve this problem?

Update: I combed through my ocean.in pretty carefully. I wasn't making that simple, silly mistake but I really wish I had. NFFILES == 3 ! number of unique forcing files FRCNAME == delbayfrc2006.nc\ ! forcing file 1, grid 1 delriv7_frc.nc\ delwnd_frc9.nc I am now getting a new error. By changing NRRE...

Good Evening, ROMS users, I've had some success running cases with different individual forcing files. I've also been able to restart simulations in the past. This restart is the first time I've tried using more than 1 forcing file. The original run only has a river forcing NetCDF file. The restart ...

That is possibly insightful.... Adjusting the time step down get's me an extra step or two before blowing up. I can try adjusting it lower than 200s. However My grid is (41,80,16) (arbitrary; same as upwelling case) so the point at which it is blowing up (20,38,16) is near the center of the grid. My...

(20, 38, 16) would be a point on the vertical boundary only 16, is the number of vertical levels. This however wouldn't be a boundary that the BC are concerned with.

Sorry, didn't see your second post.

Time step was another concern that I had. Is it possible to set a dynamic time step only to the beginning? I thought time step was fixed in ocean_upwelling.in

In your speculation or experience, do poorly defined boundary conditions often cause blowing up errors? Also, I made a slight edit, allowing the stress to increase gradually from zero to full stress over a two hour time period. Now it blows up at the 4th time step( about 20 minutes in to the full 12...

Minor update: I managed to get the build to go through with no errors. Execution blew up on the first time step. I'm going to read the forum for others with this problem but wanted to post that update here. No values jump out at me as being to large or too small in anything I've changed. Could this ...

Great! That information has prompted me to find another, simpler way to describe my stress analytically. I'm going to attempt to pass along dx & dy from ana_grid.h to ana_smflux.h as we discussed was possible for other arrays above and then I'll finally have been able to describe the stress in q...

That is more information from angler than I would have expected. 2 value from one point. Your description of that variable suggests to me that angler for the upwelling channel would be zero everywhere as the i direction and j direction are aligned to east and north for this case throughout three dom...

Thanks for those tips. I see what you mean about passing variables to ana_smflux_tile subroutine, which is shown in the code just below the part you highlighted. From reading through ana_smflux, and looking at the grid design according to the ROMS wiki, I'm wondering also if it matters weather the s...

Thanks for the corrections and advice.I was able to see in the output the priority given to the analytical files located in my working directory once MY_ANALYTICAL_DIR was defined accordingly.Since then I've been successful in playing with the test case and running the model with sensible outputs. T...

I've done some playing around and now I have a new sort of problem. ROMS compiled fine but the execution blew up after one time step and stops. A plot of that time step shows stratification, no bathymetry (okay for my purposes) and my new domain. Is it likely that this blowing up is because of the p...

Hi Again. I think I see what you mean about MY_APPLICATION being defined "higher up" and so I've tried something new. This time I copied ana_grid.h and made an ana_grid2.h where in I change the domain just as described above and place this file under the ROMS/functionals directory. I also ...

I've been playing around now with definitions and analytical files for a while and I still feel like I'm missing something fundamental. If I simply build and run the test case, I can see what analytical header files are used. Next, I tried two seemingly equivalent arrangements but saw two different ...

Thanks, I did notice this fact and moved ahead accordingly.

So I simply changed #define ANA_GRID to define ANA_GRID and set some values in ana_grid.h not too far off from the original ones for the test case. I typed ./build.bash into the command line and it complains: $ ./build.bash rm -f -r core *.ipo /home/Robert/software/roms/Projects/Upwelling2V/Build /h...

Okay that's wonderful!
I feared the "???" was something far more cryptic and horrible.

What I'll try to do now is to define "ANA_GRID" in upwelling.h, then set some different domain for the upwelling case in ana_grid.h. I'll post the results here.

Thanks again!

Thanks for responding, Kate. Your direction to the FAQ's is helpful and it reaffirms everything I've read elsewhere. I would like to ask another question just to make sure I'm understanding this process correctly. Setting the cpp flags/options only tells the compiler where to look for some certainin...

Hi All, I'm still relatively new to using ROMS and I have some thoughts on taking little strides to get familiar with the model by modifying existing cases. I've been reading a lot of the literature and opening up the include and ana_XXX files etc, to get an idea of how things work but I'm still rea...

Hi, lalvarez Did you ever manage to correct this linking problem and get ROMS to compile? I'm just a beginner and I've just run up on the same issue. Not really sure where to begin. Upon, entering the build.bash command I got the same compilation ending in the error. (Which I believe is the same bit...

M.hadfield, Thanks again, with your instructions and with the heads up about the 'oc' errors I was able to successfully install netCDF!

Now on to the next errors in compiling ROMS

I have not and I noticed this in your earlier posts. This might seem like a silly question (I'm very new to all of this), but does this require that I uninstall cygwin and reinstall with the appropriate packages or is there a simpler way to handle this?

Hi all, I've been starting to install ROMS via Cygwin, but I've gotten stuck on installing NetCDF. Following the tutorial instructions here: https://www.myroms.org/wiki/index.php/ROMS_Cygwin The only exception I made to these steps was to replace the download link for netcdf-3.6.2 with that of netcd...