Yes, but I just changed the DSTART according to the ocean_time, it works. Thanks.kate wrote:Are you really running ROMS 3.0? This has been fixed in newer versions.
Search found 39 matches
- Thu Nov 28, 2013 12:36 am
- Forum: ROMS Problems
- Topic: ROMS only runs with NDEFHIS set to zero
- Replies: 7
- Views: 5450
Re: ROMS only runs with NDEFHIS set to zero
- Wed Nov 27, 2013 11:35 pm
- Forum: ROMS Problems
- Topic: ocean_time, DSTART, TIDE_START, TIME_REF
- Replies: 2
- Views: 3252
Re: ocean_time, DSTART, TIDE_START, TIME_REF
You should be able to set NDEFHIS to NHIS, no problem. If you have a problem, something is wrong. You should be able to set the time origin and DSTART as you have below. The tides will depend on how you create your tides file. Thank you very much, kate. I tried I listed above, it works, :) not only ...
- Wed Nov 27, 2013 9:18 pm
- Forum: ROMS Problems
- Topic: ocean_time, DSTART, TIDE_START, TIME_REF
- Replies: 2
- Views: 3252
ocean_time, DSTART, TIDE_START, TIME_REF
Dear all, I am a little confused with the ocean_time, DSTART, TIDE_START and TIME_REF. I prepared all my input files with the time period from 00:00 01/01/2006 to 00:00 10/31/2008, if I want to start the simulating time from 00:00 09/01/2006, so I have to set the ocean_time in the initial condition ...
- Wed Nov 27, 2013 7:52 am
- Forum: ROMS Problems
- Topic: ROMS only runs with NDEFHIS set to zero
- Replies: 7
- Views: 5450
Re: ROMS only runs with NDEFHIS set to zero
Hi, I'm having a problem that ROMS only runs when NDEFHIS=0 in the ocean.in file. This means it produces one very large history file. I would like to produce multiple history files so my model does not encounter problems when it runs for long periods of time. But if I change the value of NDEFHIS ...
- Wed Oct 30, 2013 2:31 am
- Forum: ROMS Problems
- Topic: Blowing up problem
- Replies: 5
- Views: 5649
Re: Blowing up problem
Did you check your initial condition there? If that's clean, I would set up some STATIONS there to see how it goes bad. Is it two isolated grid points or a small area? If your STATIONS write every timestep, you can watch it go bad in time. Are you right on the edge of your timestep stability? Since ...
- Mon Oct 28, 2013 4:21 am
- Forum: ROMS Problems
- Topic: Blowing up problem
- Replies: 5
- Views: 5649
Blowing up problem
Hi Kate, Thank you very much for your suggestion. I have looked into the restart file and found the ranges of the following: Salinity: -0.065-176.729; Temperature: 0.1317-144.412 ℃; Density anomaly: -19.1-210.97 kg/m3; Free surface: -1.145-0.777 m; u : -1.13857-2.08 m/s; v : -2.213-1.2375 m/s. ...
- Fri Oct 18, 2013 8:15 pm
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
Someone once told me that the later a model gets into trouble, the harder it is to figure out. It could be anything. I assume you are running the model with a purpose in mind, involving looking at the model output. It is time to work on those skills. Start with ncview - it's really simple. OK ...
- Fri Oct 18, 2013 5:38 pm
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
Before restarting, you need to find a way to look at your solution. Is it otherwise looking reasonable? Where in the domain did the blowup happen? What sort of blowup is it, anyway? Top, bottom, middle? Velocity or density first? How quickly did things go from good to bad? On restart, check NTIMES ...
- Thu Oct 17, 2013 10:45 pm
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
Hi Kate, It again blew up after 148 days, How could I do? use the smaller time steps?
How to restart with the rst file?
How to restart with the rst file?
- Mon Oct 14, 2013 12:45 am
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
Both DSTART and TIME_REF are set in the ocean.in file. diag.F checks for out-of-bounds values for both density and velocity and reports what you see when it finds such. If it's a velocity problem, you can probably tell that from the last report of this sort (Max speed): STEP Day HH:MM:SS KINETIC ...
- Sun Oct 13, 2013 4:44 am
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
Thank you so much, Kate. It seems that we can set both the DSTART and Time_ref to 0 because I ran a model with them set to 0 succesfully. My own model is just based on that model. It seems there is no report shown it is a velocity or density problem. Yes, the NINFO is 1. I have three output files ...
- Fri Oct 11, 2013 5:24 pm
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
Thank you very much, Kate. I have taken the 1/1/2006 00:00:00 as the starting time for all the time parameters. The units of ocean_time in my initial file is second, the long name is 'time since initialization' and I set it to 0, the model seemed work, but blew up after one day more time with ...
- Fri Oct 11, 2013 5:22 am
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
Re: starting time is greater than the current model time
You have: TDAYS = -24855.1348 What is the time value in your initial conditions file? What is your DSTART and what is your TIME_REF? Do you have the time results from GET_STATE? Here is an example of some times: 40907.000 dstart Time-stamp assigned to model initialization (days). 19000101.00 time ...
- Thu Oct 10, 2013 11:49 pm
- Forum: ROMS Problems
- Topic: starting time is greater than the current model time
- Replies: 12
- Views: 8260
starting time is greater than the current model time
Hi everyone, When I tried to run the model, I got the error message: GET_CYCLE - starting time for variable: river_time is greater than current model time. TMIN = 1.0000 TDAYS = -24855.1348 my river_time is from 1 to 1036, the interval is 15 minutes. Any reply will be highly appreciated! Best
- Wed Sep 04, 2013 4:59 pm
- Forum: ROMS Problems
- Topic: How to interplate observations to model grids
- Replies: 5
- Views: 4651
Re: How to interplate observations to model grids
I am also trying to do the job like this. I am trying to use Matlab to interpolate the 1 degree temperature data (WOA09) onto the open boundary line. It is obvious a kind of 2-D interpolation, but what we want are not the meshgrid data, we need the data on the model grid nodes. But it seems that it ...
- Thu Aug 29, 2013 7:48 pm
- Forum: ROMS Documentation
- Topic: how to prepare the zeta_east data using only two station?
- Replies: 9
- Views: 16890
Re: how to prepare the zeta_east data using only two station
Peter, Yes, that's the basic idea. If you want to force ROMS then you should use the correct input format for tidal forcing. If all you want is the data then you should be able to use TMD to predict the tidal heights at the boundary. I'm quite a patient guy (normally), glad I could help ...
- Wed Aug 28, 2013 7:04 pm
- Forum: ROMS Documentation
- Topic: how to prepare the zeta_east data using only two station?
- Replies: 9
- Views: 16890
Re: how to prepare the zeta_east data using only two station
TMD will extract the tidal elevations and greenwich phase for the tidal constituents you want. It should also be able to make a prediction. Tidal forcing in ROMS is input in terms of the tidal elevations (amplitude and phase) as well as the tidal ellipses (semi-major axis, semi-minor axis, ellipse ...
- Tue Aug 27, 2013 10:56 pm
- Forum: ROMS Documentation
- Topic: how to prepare the zeta_east data using only two station?
- Replies: 9
- Views: 16890
Re: how to prepare the zeta_east data using only two station
Depending on the total size of your domain have you consider using TPXO for the free surface boundary condition? Hey, Patrick, For the free surface boundary condition, Is just only using the TPXO data ok, right? I have looked into the Tidal Forcing documentation and downloaded the TPXO7 and ...
- Tue Aug 27, 2013 6:58 pm
- Forum: ROMS Documentation
- Topic: how to prepare the zeta_east data using only two station?
- Replies: 9
- Views: 16890
Re: how to prepare the zeta_east data using only two station
You may want to review the documentation section on tidal forcing available on the ROMS website and also the "Packages" section for pre- and post-processing packages. There should be a section on tidal forcing if you follow the "Forcing Package" link. There is a TMD toolbox that should be available ...
- Mon Aug 26, 2013 10:13 pm
- Forum: ROMS Documentation
- Topic: how to prepare the zeta_east data using only two station?
- Replies: 9
- Views: 16890
Re: how to prepare the zeta_east data using only two station
Depending on the total size of your domain have you consider using TPXO for the free surface boundary condition? Thank you very much for your kind, ptimko. The zeta_east equals to tidal data (From TPXO) + non-tidal data (subtidal),right? When I look into the TPXO data set, there are three files ...
- Tue Aug 20, 2013 10:10 pm
- Forum: ROMS Documentation
- Topic: how to prepare the zeta_east data using only two station?
- Replies: 9
- Views: 16890
how to prepare the zeta_east data using only two station?
Hi all, I am preparing the boundary file, how can I get the free-surface eastern boundary condition using data from only two NOAA stations, which locate on the coast near the each side of the open boundary, respectively? I am trying to use Matlab to interpolate2D, but it seems not so good. Any reply ...
- Mon May 06, 2013 9:55 pm
- Forum: ROMS Documentation
- Topic: How to start my own case, such as to create input files?
- Replies: 4
- Views: 10813
Re: How to start my own case, such as to create input files?
No, you don't need both. If you like Matlab, go with it. As I said before: I was intentionally vague because you need to build up some tools for manipulating netcdf files that you are comfortable with. I used to use some horrible fortran codes, I then switched to primarily NCL and NCO for these ...
- Mon Apr 01, 2013 10:53 pm
- Forum: ROMS Documentation
- Topic: How to start my own case, such as to create input files?
- Replies: 4
- Views: 10813
Re: How to start my own case, such as to create input files?
This is coming up a lot so I just checked the FAQ: https://www.myroms.org/wiki/index.php/Frequently_Asked_Questions#How_can_I_create_the_initial.2Fboundary.2Fforcing_NetCDF_files_for_ROMS.3F Thank you, kate. Actually, I have downloaded the whole ROMS matlab repository, what's the next step? Do I ...
- Mon Apr 01, 2013 8:14 pm
- Forum: ROMS Documentation
- Topic: How to start my own case, such as to create input files?
- Replies: 4
- Views: 10813
How to start my own case, such as to create input files?
Hello, everyone, How are you doing these days?
I have run the test case successfully, Now I am trying to start my own case, But I have no idea how to create input files? what software or toolkit should I use?
Any help will be highly appreciated!
Peter
I have run the test case successfully, Now I am trying to start my own case, But I have no idea how to create input files? what software or toolkit should I use?
Any help will be highly appreciated!
Peter
- Mon Jan 28, 2013 11:43 pm
- Forum: ROMS Problems
- Topic: Always blowing-up at the same timestep
- Replies: 2
- Views: 2054
Re: Always blowing-up at the same timestep
I would start by looking at the restart file with ncview. If it says it wrote to record 3 while blowing up, focus on record 3. Find out which field went bad and where it went bad. Can you try a serial run? Can you try a different compiler? How about optimized vs. unoptimized? Which compiler are you ...
- Mon Jan 28, 2013 10:29 pm
- Forum: ROMS Problems
- Topic: Always blowing-up at the same timestep
- Replies: 2
- Views: 2054
Always blowing-up at the same timestep
Hi everyone, I am running a Roms-sediment model, but it is always blowing-up at the same timestep with a only message: Blowing-up: Saving latest model state into RESTART file, although I reduce the number of threats and timestep. The same model was run successfully on another machine with mpirun, I ...
- Thu Dec 06, 2012 10:36 pm
- Forum: ROMS Installation
- Topic: Trouble getting mpirun to work
- Replies: 0
- Views: 2016
Trouble getting mpirun to work
Hi everyone, When I use the mpirun, it can not work.The error message is: bash: line 0: cd: /home/wzhu/chesapeake_sed: No such file or directory /usr/bin/env: ./oceanM: No such file or directory bash: line 0: cd: /home/wzhu/chesapeake_sed: No such file or directory /usr/bin/env: ./oceanM: No such ...
- Thu Nov 29, 2012 6:26 pm
- Forum: ROMS Installation
- Topic: After installation of NetCDF3
- Replies: 13
- Views: 11785
Re: After installation of NetCDF3
Hi justina0622,
I am now having the same problem, where is the .bashrc file, I only have a .bash file and I can not find the directory in the file.
Wenwu
I am now having the same problem, where is the .bashrc file, I only have a .bash file and I can not find the directory in the file.
Wenwu
- Thu Nov 29, 2012 4:03 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
The problem was ultimately solved. The server is a single-processor machine, it is not so powerful to run this model. when I changed to a more powerful server, it worked.
Thanks to all the kind people: kate and ckerry.
Best.
Thanks to all the kind people: kate and ckerry.
Best.
- Wed Nov 14, 2012 11:46 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
No, they're in the ocean_upwelling.in. Hi Friends, How are you doing these days? I have not got the problem silved yet, but when I type:sudo tail -f /var/log/syslog to see the syslog: Nov 14 18:33:18 lsvm kernel: [1244276.692068] [22113] 1003 22113 5902 1 0 0 0 bash Nov 14 18:33:18 lsvm kernel: ...
- Fri Nov 09, 2012 4:34 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
I have had this error message before when my set-up files are in a directory which is several sub-directories away from my home directory eg. /home/subdir1/subdir2/subdir3/subdir4/run By copying the exact same set-up files to a folder /home/run for example I no longer got the error. I don't ...
- Thu Nov 08, 2012 9:02 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
No, they're in the ocean_upwelling.in. I have done that, when I double increase the values, it is OK; when I thrice increase the values or more, it says 'Segmentation fault (core dumped)', but does not dispaly 'killed'. Then I compared the 'ocean_upwelling.in' file with my domain 'Lee.in' file, I ...
- Thu Nov 08, 2012 5:25 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
The only thing I see there is the stack size limit, though my experience has been a seg fault, rather than "killed" as the message. One thing you can try with the upwelling problem is simply increasing the values of Lm, Mm, N to see if larger values fail as your domain did. Thank you. But what and ...
- Thu Nov 08, 2012 4:56 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
Thank you for reply. When I typed 'ulimit -a', it displayed: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 55260 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files ...
- Wed Nov 07, 2012 10:43 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
Processes usually get killed for running beyond some limit - time limit, open files limit, memory limit. I can't tell which you ran into. How big is your grid? Did it hang there trying to write for a very long time? Did you get any output file at all? I think the grid is 160x240. The contents in my ...
- Tue Nov 06, 2012 10:46 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
Processes usually get killed for running beyond some limit - time limit, open files limit, memory limit. I can't tell which you ran into. How big is your grid? Did it hang there trying to write for a very long time? Did you get any output file at all? Thank you. It took about several minutes(not ...
- Tue Nov 06, 2012 9:06 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
Sorry, I don't know what's wrong. Have you successfully run ROMS in a simpler domain? Have you tested your NetCDF library in any way? I would investigate this in a debugger, poking to find out what ID is in error - the file ID or the variable ID? You might get the same answer from print statements ...
- Tue Nov 06, 2012 2:29 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
Re: ERROR: Abnormal termination: NetCDF OUTPUT.
Help! Help! I am waiting for you online.
- Mon Nov 05, 2012 11:18 pm
- Forum: ROMS Bugs
- Topic: ERROR: Abnormal termination: NetCDF OUTPUT.
- Replies: 17
- Views: 16030
ERROR: Abnormal termination: NetCDF OUTPUT.
When I run the ROMS model, I got the following informaton: NETCDF_PUT_FVAR_1D - error while writing variable: ocean_time in input file: ./Lee.nc call from: wrt_his.F ROMS/TOMS - Output error ............ exit_flag: 3 ERROR: Abnormal termination: NetCDF OUTPUT. REASON: NetCDF: Not a valid ID Part ...