Ocean Modeling Discussion

Thank you Kate! The boundary type for free surface I used before was 'Clamp'. If I understand right, the Flather type is for 2D momentum ubar/vbar. So I tested to use real ubar/vbar/uvel/vvel to be my boundary condition, with boundary type: Fla/ Fla/ Cla/ Cla. The initial u, v, ubar, vbar, zeta are ...

Dear all, I am trying to run an idealized test, only having free surface as the boundary condition to drive the water current inside of my domain. The initial conditions are constant all over the domain: u0=0; v0=0; temp0=10; salt0=10; zeta0=0; However, I found that the simulated 'zeta' inside of my ...

Dear all, I am working on a case study of simulating the water current of estuary without wind forcing. The boundary condition and initial condition (including temperature, salinity, ubar, vbar, uvel, vvel, zeta) were interpolated from another hydrodynamic model simulation result. I have complete a ...

Hi Kate,

Thanks for you reply! The minimum depth is the problem. I correct it to 2 meter instead and now ROMS is running!

Best regards
Yifan

Dear all, I am working on a case study of simulation the water current of estuary without wind forcing. I have created my own model grid(by using GridBuilder), boundary and initial condition(by using ROMS matlab tool). The model blew up after 1st step. The standard output showing this: Basin ...

Hello, Check the timestamp on your oceanM or oceanG perhaps your build failed and the executable is an older one from an upwelling test case. Though I don't believe this is contributing to your issue, you might consider setting MY_PROJECT_DIR to ${PWD} so your executable is always written to the ...

Hello everyone, I am facing a problem when I tried to compile oceanM for benchmark case. I did get the executable file, oceanM, after running build script, attached below, but when I run it, I mentioned that the header file's name in the output log (attached below)was not right. It was "upwelling.h ...

Hello everyone, I would like to add some additional information: I tried to compile and run benchmark case with oceanS and everything looked fine. It finished after 167 seconds. Also tried oceanG (compiled with the same build.bash file but opened "USE_DEBUG=on"), which was finished after 1600 ...

Dear all, I have one problem when I run benchmark case with oceanM: It seems the "Header file" and "Header directory" showing in the output log file of running, are immutable... I pasted the content of it: '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Benchmark Test, Idealized ...

You didn't understand at all what I was saying to you, or what WET_DRY does. The wetting and drying option ( WET_DRY ) is modeled in ROMS by changing the associated land/sea masking arrays at every barotropic time-step in step2d , which affect the ocean state variables. The wet/dry mask is a new ...

The WET_DRY option is not adjointed because it not fully differentiable, and because of every time-step of the forward trajectory need to be saved to have a consistent linearization of the tangent linear (TLM) and adjoint (ADM) models. You cannot use such time-depending land/sea masking in any ROMS ...

Hello everyone! I am trying to compile ROMS for my case study of simulating water current of an estuary, without wind force. I have successfully compiled and run the Upwelling case. Attachment is the header file I created for my case study, but when I tried to compile ROMS with the it, I got this ...

-lm is a math library, not matlab. Maybe try putting your junk directory at the front of LD_LIBRARY_PATH instead. Thank you Kate, It seems the warning messages didn't bother me anymore. I found I didn't add the netcdf-fortran library folder into LD_LIBRARY_PATH, so I put netcdf and netcdf-fortran ...

My hdf libraries are a few years old but are version 10.0.x, but that probably has nothing to do with this at all. Do you get a linking error from NetCDF rather than HDF? Thanks for your reply, Kate! When I run oceanS, I did get a error message about netcdf: oceanS: error while loading shared ...

Did you get a warning like that at the compile/linking phase too? It's probably missing the -lnetcdff in the link command. Hello Kate, I am facing the same problem, when I running oceanS for upwelling case: oceanS: symbol lookup error: oceanS: undefined symbol: __netcdf_MOD_nf90_create During ...

- i have not used pgi in awhile, so i did a Google on "Error: no such instruction: `vinserti128 $1,%xmm0,%ymm0,%ymm1'" and found this: https://www.pgroup.com/userforum/viewtopic.php?t=4904&sid=b1ec7d574c2f357163260c5965caa1f6 looks like a pgi issue. - Another thought is that you would not need ...

i am not sure what you mean by a similar problem. How about we start over, and you explain the issue with as much information as you can. the last few lines of stdout saying "#0 0xFFFFFFFFFFFFFFFF" dont really tell me anything. so if you have something similar i would need to see the whole std out ...

There are a couple oddities about your 'nf-config --flibs' output. First, "-O" and "-tp p7" are compiling flags, not linking flags. That would suggest that perhaps NetCDF wasn't configured/compiled quite right. Second, why is -R (I believe being treated as -rpath in this case) used for the C ...

Hi all Did anyone solve this problem in the end? I have a similar issue with coawstM, rather than oceanM, but I am guessing it is the same cause. I have been trying to run the Coupled Inlet Test Case example for COAWST. So far I've built a coawstM.exe, and then I try to use mpirun: cd /home ...

Hello everyone, I am trying to compile ROMS on Linux sever with pgi. The error message I got is like this: ''' ROMS/Utility/checkdefs.F:2822: warning: extra tokens at end of #ifdef directive ar: creating /home/ywang/roms/Projects/Upwelling/Build/libUTIL.a ar: creating /home/ywang/roms/Projects ...