Ocean Modeling Discussion

You said that you haven't been able to compile oceanM yet, so what are you running with mpiexec command in your job file? Notice that you called for ./oceanM, which you claim is not built.

What error message are you getting when trying to build oceanM?

Hi, I've been working with setting up ROMS for a few weeks now. I'm using builds with ifort/mpiifort (Intel 14) and gfortran/mpif90 (Intel 14) and they produced consistent tracer results for the BENCHMARK 1 and 3 test cases for various tile sizings, #'s of cpus, #'s of nodes. However, when I attempt ...

My mistake! Sorry for the N/A post.

When trying to build oceanM I'm getting an error that says that zkeep has no implicit type. When I check the file it called the error from, t3dbc_im.f90 in the Build directory (scratch dir), there is only one line that references zkeep, and it's type is not defined. IF (zkeep.lt.0.0_r8) THEN t(i ...

My mistake! I am new to ROMS and had chosen to use UPWELLING due to the boundary conditions and I wasn't aware that I should choose the number of cpus in a way that corresponds to the grid dimensions.

Thank you for the response and I will play around with the benchmark tests.

Oo, I forgot to mention that the ifort build will run for 001x016 (I'm running on 16 cpus) but will blow-up if I try to partition the 16 differently. I'm not sure if this gives any clues...

I tried running the ifort build with -r8 and I tried running the gfortran build with -fdefault-real-8 and the results were the same as before (the results for either did not change as a result of adding the flags). As for what I said about the segmentation fault using -O3 with ifort. That was ...

I have been using the ocean_upwelling.in file in order to test an issue I was having with a more complicated model, in which switching between different fortran compilers is significantly impacting my results. For the upwelling case I am using ifort/mpiifort with one build and gfortran/mpif90 with ...