ATMET.com

sea121 · Forum Member Joined: 30 May 2007 Posts: 22

Hi,
when I ran rams 6.0 with my own sst data(from 200703211200 to 200703231200), I modified the mktopo.f to get sst data as following:

S03211290S000E
S03211290S180W
S03211890S000E
S03211890S180W
S03220090S000E
S03220090S180W
S03220690S000E
S03220690S180W
S03221290S000E
S03221290S180W
S03221890S000E
S03221890S180W
S03230090S000E
S03230090S180W
S03230690S000E
S03230690S180W
S03231290S000E
S03231290S180W

and the SHERDER as following:

180 181 -90 -180 0.000000 0.000000
9
032112 2007 03 21 12
032118 2007 03 21 18
032200 2007 03 22 00
032206 2007 03 22 06
032212 2007 03 22 12
032218 2007 03 22 18
032300 2007 03 23 00
032306 2007 03 23 06
032312 2007 03 23 12
(bksz NO lat lon iofflat iofflon)
(ntimes)
(fpfx year mon date hour)

and then, I got sst data as following by running "rams -f RAMS-makevfile":

ssth-W-2007-03-21-180000-g1.h5
ssth-W-2007-03-21-180000-g2.h5
ssth-W-2007-03-22-000000-g1.h5
ssth-W-2007-03-22-000000-g2.h5
ssth-W-2007-03-22-060000-g1.h5
ssth-W-2007-03-22-060000-g2.h5
ssth-W-2007-03-22-120000-g1.h5
ssth-W-2007-03-22-120000-g2.h5
ssth-W-2007-03-22-180000-g1.h5
ssth-W-2007-03-22-180000-g2.h5
ssth-W-2007-03-23-000000-g1.h5
ssth-W-2007-03-23-000000-g2.h5
ssth-W-2007-03-23-060000-g1.h5
ssth-W-2007-03-23-060000-g2.h5
ssth-W-2007-03-23-120000-g1.h5
ssth-W-2007-03-23-120000-g2.h5

It's strange that the sst data at 200703211200 was missed!What's the problem? How to solve the problem?
Can anyone help me?????

tremback · Posted: Fri - 08 Jan 2010 - 4:49 pm Post subject:

Set up a short one hour run starting from the first 1200 UTC time. This should for sure generate the files.
_________________
- Craig

sea121 · Forum Member Joined: 30 May 2007 Posts: 22

Hi,Craig, thanks for your suggestions!

I had tried to set "TIMMAX = 1.0," as you suggested, but the problem was the same. This time, I got 4 sst files as following:
ssth-W-2007-03-21-180000-g1.h5
ssth-W-2007-03-21-180000-g2.h5
ssth-W-2007-03-22-000000-g1.h5
ssth-W-2007-03-22-000000-g2.h5

The first sst file was still "ssth-W-2007-03-21-180000-g1.h5" but not "ssth-W-2007-03-21-120000-g1.h5".

I had checked the ssth-W-2007-03-21-180000-g1.h5 by HDFView and found a strange phenomenon, in which the year,month ,day and hour info were 0 ,1 ,16 and 12 respectively( the same as the first sst files obtained by RAMS standard datasets ).It seemed that there was something wrong. It confused me, I don't know how to solve this,please help me.Thanks!

Another question, the procedure I writed to construct my own sst files in RAMS6.0 is the same as I did in RAMS4.4 and in the latter it was proved to be effective, does it matter this?

tremback · Posted: Mon - 18 Jan 2010 - 8:44 pm Post subject:

Something weird is happening...
Set ITIME1=1200, TIMMAX=0.,RUNTYPE='MAKESFC', and IUPDSST = 0,
Delete all previous created surface files from the directories and run again.
_________________
- Craig

sea121 · Forum Member Joined: 30 May 2007 Posts: 22

Hi,Craig,thanks for your suggestions again!
I had tried to set " ITIME1=1200, TIMMAX=0.,RUNTYPE='MAKESFC', and IUPDSST = 0," but the problem was the same.The sst file I got was still "ssth-W-2007-03-21-180000-g1.h5". I really don't know why?

Another question, the procedure I writed to construct my own sst files in RAMS6.0 is the same as I did in RAMS4.4 and in the latter it was proved to be effective, does it matter this?