Missing input files for test cases? ie estuary_test, weddell

General scientific issues regarding ROMS

Moderators: arango, robertson

Post Reply
Message
Author
Oceansifter
Posts: 3
Joined: Fri Mar 04, 2011 6:16 am
Location: UNSW

Missing input files for test cases? ie estuary_test, weddell

#1 Unread post by Oceansifter »

Hi there,

I am a reasonably new user to ROMS. I have the Upwelling testcase working fine as desribed on:
https://www.myroms.org/wiki/index.php/ROMS_Cygwin
This page was very useful so my thanks to the authors.

So I am now trying further test cases which I checked out of the repository. DAMEE is working also (although taking a long time to run) as it comes nicely packaged with input data (.nc files). inlet_test, shoreface, and test_head all come with data too so should pose no problems. But the other test cases do not seem to have any nice premade input files...

Am I missing something or do i need to create the .nc files to run the other apps? If so can someone point me to a tutorial or example for doing this, or can i download sample files from somewhere? Any help would be greatly appreciated.


Some more details below:

For instance the estuary_test stops here:

...
rrays -O3 -ffast-math -ffree-form -ffree-line-length-none strings.f90
cd /home/roms/Projects/estuary_test/Build; /usr/bin/gfortran-4 -c -frepa
rrays -O3 -ffast-math -ffree-form -ffree-line-length-none mod_netcdf.f90
cd /home/roms/Projects/estuary_test/Build; /usr/bin/gfortran-4 -c -frepa
rrays -O3 -ffast-math -ffree-form -ffree-line-length-none mod_sources.f90
cd /home/roms/Projects/estuary_test/Build; /usr/bin/gfortran-4 -c -frepa
rrays -O3 -ffast-math -ffree-form -ffree-line-length-none analytical.f90
analytical.f90:420.14:

ana_grid.h: no values provided for Xsize, Esize, depth, f0, beta.
1
Error: 'ana_grid' at (1) is not a variable
analytical.f90:1171.18:

ana_sediment.h: no values provided for bed, bed_mass, bottom.
1
Error: 'ana_sediment' at (1) is not a variable
make: *** [/home/roms/Projects/estuary_test/Build/analytical.o] Error



The Weddell testcase stops here:

...
Output/Input Files:

Output Restart File: ocean_rst.nc
Output History File: ocean_his.nc
Output Averages File: ocean_avg.nc

READ_PHYPAR - could not find input file: ocean_clm.nc

Elapsed CPU time (seconds):

Thread # 0 CPU: 0.094
Total: 0.094

Nonlinear model elapsed time profile:

Total: 0.000 0.0000

All percentages are with respect to total time = 0.094

ROMS/TOMS - Output NetCDF summary for Grid 01:

ROMS/TOMS - I/O error ............... exit_flag: 4


ERROR: I/O related problem.


In this case I seem to be missing all of the following files (below copied from .in file)

! Input NetCDF file names, [1:Ngrids].

GRDNAME == ocean_grd.nc
ININAME == ocean_ini.nc
ITLNAME == ocean_itl.nc
IRPNAME == ocean_irp.nc
IADNAME == ocean_iad.nc
CLMNAME == ocean_clm.nc
BRYNAME == ocean_bry.nc
FWDNAME == ocean_fwd.nc
ADSNAME == ocean_ads.nc

User avatar
kate
Posts: 4088
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

Re: Missing input files for test cases? ie estuary_test, wed

#2 Unread post by kate »

There are some tutorials on the ROMS wiki.

What are your ultimate goals? Most people want to jump right into some particular application and not waste time with all these other domains.

Oceansifter
Posts: 3
Joined: Fri Mar 04, 2011 6:16 am
Location: UNSW

Re: Missing input files for test cases? ie estuary_test, wed

#3 Unread post by Oceansifter »

Hi Kate,

Thanks for reply. Ive had a look through these tutorials but Im still hazy on creating and assigning data to appropriate forcing files.

Im working on a model in an estuary and having problems with the input. My thinking is that by getting some of the testcases working I will gain insight into what is going wrong with my own domain. In particular, I'd like to understand how the estuary_test forcing files are created and implemented. I'd also like to get the estuary_test working to see how mixing processes and sediment dynamics respond to changes in input conditions in a simple basin allowing comparison to a more realistic case at a later stage.

Cheers.

User avatar
m.hadfield
Posts: 521
Joined: Tue Jul 01, 2003 4:12 am
Location: NIWA

Re: Missing input files for test cases? ie estuary_test, wed

#4 Unread post by m.hadfield »

Hi Oceansifter

Are you referring to the ROMS source area

https://www.myroms.org/svn/src/trunk/

or the test cases

https://www.myroms.org/svn/src/test/

If the latter, then I have successfully run a bunch of these, including estuary_test, though not yet weddell.

Your estuary_test failure occurs at compilation time, so is a model configuration problem, not related to lack of data files. Check your preprocessor options in estuary_test.h and build.bash. You might want to look at the output I got--attached.

The weddell case does appear to be incomplete. It is a 3D run with open western and eastern boundaries, but there are no boundary-condition preprocessor symbols for tracers or M3 and no boundary or climatology files.
Attachments
estuary_test.log
Estuary_test output.
(4.33 MiB) Downloaded 265 times

Oceansifter
Posts: 3
Joined: Fri Mar 04, 2011 6:16 am
Location: UNSW

Re: Missing input files for test cases? ie estuary_test, wed

#5 Unread post by Oceansifter »

Nice one. I am referring to the latter - the testcases. Im glad to know you got it working. Ill have a look at your log and see if I can get the configuration right. Cheers.

Post Reply