I found that the problem was with allocating large arrays. So I wrote the "S.def_v3d" variables into a separate file by running the script d_climatology.m and this time setting S.def_temp and S.def_salt to zero
Ratnam
Search found 10 matches
- Wed May 08, 2013 9:02 am
- Forum: ROMS Tools and Techniques
- Topic: Error using c_climatology.m...
- Replies: 1
- Views: 2486
- Tue May 07, 2013 4:40 am
- Forum: ROMS Tools and Techniques
- Topic: Error using c_climatology.m...
- Replies: 1
- Views: 2486
Error using c_climatology.m...
I am trying to use d_climatology.m script to create a climatology file for ROMS. However, when I switch on the flag S.def_v3d to 1. I get an error >> d_climatology NC2 Error Error using c_climatology (line 848) C_CLIMATOLOGY: ENDDEF - unable to leave definition mode. Error in d_climatology (line 121 ...
- Tue Jun 19, 2007 1:30 pm
- Forum: ROMS Problems
- Topic: ROMS with monthly levitus climatology..
- Replies: 4
- Views: 4314
Hi I found the problem for the blowing of the model to be in the monthly climatology I created. Actually the problem was in the .hdat files read by the OA program. The .hdat files have levels as 0 9 99.....149999 instead of 0 10 100....150000. I made the change in the .hdat files then the OA program ...
- Tue Jun 19, 2007 9:29 am
- Forum: ROMS Problems
- Topic: ROMS with monthly levitus climatology..
- Replies: 4
- Views: 4314
Dear Dr. Hadfield I am running ROMS for the domain 20s-40N, 40E-120E with a resolution of 60Km. When I change from annual levitus to monthly levitus I am getting the following output: Process Information: Thread # 0 (pid= 21443) is active. Model Input Parameters: ROMS/TOMS version 2.2 Tuesday - June ...
- Mon Jun 18, 2007 4:43 pm
- Forum: ROMS Problems
- Topic: ROMS with monthly levitus climatology..
- Replies: 4
- Views: 4314
ROMS with monthly levitus climatology..
Hi I made a run of nearly 10 years with Levitus annual climatology. Now, when I am trying to use Levitus monthly climatology for further runs, the model is blowing up. Can someone please suggest how to get around this problem. I tried changing the time step but still the model blows up. Thanks Ratnam
- Mon May 21, 2007 10:24 am
- Forum: ROMS Results
- Topic: ROMS output on regular lat/lon
- Replies: 2
- Views: 12384
ROMS output on regular lat/lon
HI
I want to convert the ROMS output on Spherical grid to a regular lat-lon grid. Is there any utility available for this.
Thanks
Regards
Ratnam
I want to convert the ROMS output on Spherical grid to a regular lat-lon grid. Is there any utility available for this.
Thanks
Regards
Ratnam
- Thu Apr 12, 2007 10:41 am
- Forum: ROMS Discussion
- Topic: Help Required in preparing SSS forcing file....
- Replies: 1
- Views: 2021
Hi My problem is solved. There was a bug in the get_grid.F file. After fixing it I am able to properly generate the forcing file. The change is to be made in line 200 of get_grid.F get_grid.F from: status=nf_get_vara_FTYPE(ncgrdid,vid(idrlon),start,count, & rlat) to: status=nf_get_vara_FTYPE(ncgrdid ...
- Thu Apr 12, 2007 10:05 am
- Forum: ROMS Discussion
- Topic: Help Required in preparing SSS forcing file....
- Replies: 1
- Views: 2021
Help Required in preparing SSS forcing file....
Hi I prepared an ascii file containing the monthly Sea Surface Salinity from levitus data set using the procedure specified in the forcing.in file. I am specifying the name of the ascii data file and trying to run forcing package. I am getting the following error GET_GRDFLD: latitude point = 39.54 ...
- Tue Apr 03, 2007 12:19 pm
- Forum: ROMS Discussion
- Topic: Request for oa4_sss.in....
- Replies: 0
- Views: 1660
Request for oa4_sss.in....
Hi
I want to test my installation of forcing package. Can i get the oa4_sss.in for creating the oa4_lev94_sss.nc which is required for running the forcing package. How different will this be from say oa4_coads.in or any other oa4_*.in
Thanks
Regards
Ratnam
I want to test my installation of forcing package. Can i get the oa4_sss.in for creating the oa4_lev94_sss.nc which is required for running the forcing package. How different will this be from say oa4_coads.in or any other oa4_*.in
Thanks
Regards
Ratnam
- Wed Feb 07, 2007 6:04 am
- Forum: ROMS Problems
- Topic: initial package
- Replies: 1
- Views: 2249
Re: initial package
Hi
the problem can be solved by declaring some variable say
character*60 tempnam in def_out.F
then making the following modifications:
Instead of
lsdim=Vname(6,idFsur)
you can have
tempnam=Vname(6,idFsur)
lsdim=lenstr(tempnam)
Ratnam
the problem can be solved by declaring some variable say
character*60 tempnam in def_out.F
then making the following modifications:
Instead of
lsdim=Vname(6,idFsur)
you can have
tempnam=Vname(6,idFsur)
lsdim=lenstr(tempnam)
Ratnam