Ocean Modeling Discussion

Sorry for the slow response--I've tested the model with three amounts of processors: 1 node (40 cpus), 3 nodes (120 cpus), and 6 nodes (240 cpus). The 6 node run crashes as described above. The 1 node run is excruciatingly slow (~2x real time speed), and does not crash in the time I allowed it to ...

Thanks, John! I'll look into changing the bathymetry. I am using the same compilers to compile and for the run itself. I'm going to run a few tests: 1.) Use a smaller number of cores 2.) Run in serial 3.) Use newer versions of openmpi and netcdf. Currently, I'm using openmpi 4.0.3 and netcdf 4.7.0 ...

Thanks for the suggestion--my .in file does include a path to the .yaml file, rather than a non-existent .dat file: ! Input variable information file name. This file needs to be processed ! first so all information arrays can be initialized properly. VARNAME = /dfs6/pub/skastner/ROMS/trunk/ROMS ...

Yes, strangely. I'm attaching the output from the compilation process here, in case that's of use.

A new problem has arisen, though. This seems to be some sort of I/O error with openmpi... although it's occuring in the set_tides.f90 code. Here's the stack trace: [hpc3-21-18][[59635,1],230][btl_openib_component.c:3655:handle_wc] Unhandled work completion opcode is 136 forrtl: error (78): process ...

Ah, of course. This was the issue! Thanks, David.

Yes, sorry, here it is.

Thanks!

Hello, I'm getting an error in the startup process on a model that includes tides. The stack trace looks like this: forrtl: severe (194): Run-Time Check Failure. The variable 'tides_date_$FOUNDIT' is being used in 'tides_date.f90(120,13)' without being defined Image PC Routine Line Source romsG ...

Using ifort, as suggested above, fixed the memory leaks.

Apologies for the slow response. This error came about on a fresh installation of the latest version of ROMS. Nevertheless, I updated the directories involved, and got the same error (see the attached log files). I noticed that the test cases use a version of "varinfo.yaml" stored in the test ...

Thanks for the quick response, David. That was indeed the full output of the dfs build attempt. I had changed the way I was dealing with modules---on the dfs drive, I was loading openmpi and netcdf before compiling. On my home directory, I was not loading these before compiling. I went back to the ...

Hello friendly ROMS forum denizens, I am having an issue with compilation with the latest version of ROMS. More accurately, I have installed ROMS in two places (1) on my HOME directory on the HPC I have been using and (2) in a different dfs drive location that was recommended to me by my IT ...

Hi John and John, Thank you again for the advice. I've gone back and carefully checked the differences between Eli Hunter's TPXO7 code and John Luick's TPXO9 code, and the two do handle time slightly differently. If I understand correctly, John Luick's code, TPXO9v4_ROMS.m, uses the "t0" input given ...

Thanks for helping me troubleshoot this. To respond in turn: The harmonics I get from 33 days of ROMS output w/TPXO9 (evaluated using t_tide, starting the analysis on 4 Aug 2019, after the tidal ramp up period): Same units (amp in m, phase in GMT): Q1: 0.0137 235.98 O1: 0.0679 349.88 K1: 0.1028 6.37 ...

Yes, almost, except I'm using Eli Hunter's code for TPXO7 and John Luick's for TPXO9. Is this possibly the source of the mismatch--do the two codes handle time inputs differently? I've given them both the same date: August 1, 2019. The lines do not overlap with a simple phase shift. I'm attaching a ...

Hi John, John, and Kevin, Thanks for your help. I have done what John Wilkin suggesting; setting DSTART and TIDE_START to 0 while making TIME_REF my desired start time (01 Aug 2019). The result using TPXO9 is below: limon_model_tpxo9_comp.png I extracted a location on the west side of the model ...

Hi John, Thank you for maintaining this exceptionally useful code. I'm having a bit of a hard time successfully implementing tidal forcing in my model domain, which encompasses Bahia Almirante, near Bocas del Toro, Panama, and the surrounding coastal ocean. I've used TPXO9v4_ROMS.m to make my ...

Thanks, Ivica. That was indeed the problem! Lesson learned.

Thanks for catching those abnormalities, John, especially the undefined tracer advection scheme. This was surprising to me, as I include #define TS_MPDATA in my .h file. I'm therefore a little perplexed as to why the advective scheme is undefined in the log file--i'm attaching my .h & .in files here ...

Thanks, Kate. The print commands were helpful; it seems like the tracer fields at nout=3 are all NaNs (at least along the edges), despite no NaNs in any input files. It seems like I may want to turn to a debugger here, and there isn't one on the cluster I'm using as far as I can tell. Would you ...

Hello friendly ROMS forum users, I am having an issue with my tracer boundary read-in as time stepping is about to start. My simulation is intended to be a realistic representation of Bahia Almirante, a bay in Panama. I've interpolated HYCOM u, v, T, S, and sea surface height onto the boundaries of ...