I am trying to introduce a cluster of floats into my model. I am not sure how the Fdx, Fdy, Fdz parameters in floats.in work? Can somebody tell me what range of values might be used for these parameters, and what sort of clusters will result?

On the last line of floats.in a routine called 'init_floats.F´is mentioned - I don't have this routine in ROMS 2, though I see it was used in ROMS 1. Has this now been omitted from ROMS 2?

It is telling you what the problem is: the input to ROMS should be a file, not a directory. Run it like:

Code:

./oceanS <External> output

Code:

./oceanS <External_ocean_floats2d_in> output

or use whatever input file makes sense. This is the case for serial ROMS and OpenMP ROMS, but MPI ROMS needs to be run like:

Code:

./oceanM External/ocean_floats2d.in > output

Actually, I typed what I wanted to type for the serial case and it isn't showing up the way I meant it to - perhaps that happened elsewhere too! The real input file is External/ocean_floats2d.in (or your file of choice).

Did you look through the ROMS output to see if there is any mention of floats? Did you tell ROMS to output to the floats file every step or five? So you say ROMS ran without any floats output being nonzero? But you do get floats?

First look closely at all the values in your floats file. Are you releasing the floats inside the domain? (When floats go outside the domain, their position is reported as 1.E35.) Are your initial float locations consistent with your coordinate type C (the second entry in each float-position line)?

If you don't see any problems there, you're going to have to do it the slow way. Run your code in debugging mode and work through the relevant routines, checking the float status at the critical locations. Some people do this with a debugger, but I use print statements in the code (the .f90 files), rebuild and rerun, etc. You *will* eventually find the problem this way and you *will* be surprised by how simple it is.

Some debugging tips: You might want to modify the floats file to cause the floats to be released earlier and/or reduce the number, or to find some settings that *do* work before you work out why your original ones *don't*. Debugging in serial, single-tile mode, where possible, simplifies things. Oh and the usual one: enable bounds-checking!

Everithing is ok with the model. My problem was reading the netCDF files. I'm reading them in Matlab using netCDF_toolbox, on Windows. As the first values are 1e35, before the floats are released, matlab show just 1e35 and 0e35 instead of the real values. So first you need to clear the large values with something like:

It's surprisingly easy to make mistakes like this. (If I had $0.01 for every time I've done it, I'd have ... well, a dollar or too anyway.) The best solution is to have independent ways of scanning through your data files. The ncdump utility is useful for this. It's particularly good at giving you a view of the overall structure of your file, but it can dump data too. Another useful set of tools is NCO:

I am new in ROMS. I tried to run the lake_signell test case.After the compilation, when i tried to run, it gives ocean_his.nc, ocean_avg.nc and ocean_flt.nc but ocean_flt.nc is completely empty. Along with these I received following error.

MuhammadAbdurRouf@ROUF /roms/test/lake_signell$ ./oceanS < ocean_lake_signell.in> lake_signellout.datAt line 282 of file def_floats.f90Traceback: not available, compile with -ftrace=frame or -ftrace=fullFortran runtime error: Expected CHARACTER for item 1 in formatted transfer, gotREAL. If you want to make character descriptors typeless, compile with -fsloppy-char(6x,'DEF_FLOATS - inquiring history file: ',a)

$ ./oceanS < ocean_lake_signell.in> lake_signellout.datAt line 282 of file def_floats.f90Traceback: not available, compile with -ftrace=frame or -ftrace=fullFortran runtime error: Expected CHARACTER for item 1 in formatted transfer, gotREAL. If you want to make character descriptors typeless, compile with -fsloppy-char(6x,'DEF_FLOATS - inquiring history file: ',a)

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum