|
|
|
EES, IES, TMS, ACF, and DCF Daily CDF Production
It used to be necessary to go through the process outlined by
The Super-Long Super-Boring Manual Process
but now we are blessed with the program: auto_dailies which eliminates
steps one and two by going to the goddard website for you, finding the last
cdf made for each data type and making all of the rest of the dailies from
there until 31 days before the current date. Since step three is currently
not working, that only leaves the following process, which is much easier and
far more automated.
Also note, it is unfortunate that you will have to go through
The Super-Long Super-Boring Manual Process
if you want to run cdfs that are older than the last cdf of your data type sent
to Goddard.
| Creating the CDF files |
- Login to a machine as LZP
>rsh fastmachine -l lzp
- Source the integretion workspace:
>source /disks/fast/software/integration/setup
- Start the dailies
>auto_dailies
|
| Checking the CDF files - Currently
not working |
- Login to a machine as yourself.
>cd /disks/juneau/cdf1/dailycdf/newbatch
>../idl startup
>IDL>animate, "ees"
>IDL>animate, "ies"
- Check for any data anomalies.
|
| Creating the .sfdu files |
- Login to a machine as LZP.
>cd /disks/juneau/cdf1/dailycdf/newbatch
>../cdfsfdu2 ees v01
>../cdfsfdu2 ies v01
>../cdfsfdu2 tms v01
>../cdfsfdu2 acf v01
>../cdfsfdu2 dcf v01
|
| Sending the files to Goddard |
- Login to juneau as LZP.
>cd /disks/juneau/cdf1/dailycdf/newbatch
>ftp cdaweb.gsfc.nasa.gov
>[User name is "fastgst"]
>[Type in password]
ftp>bin
ftp>prompt
ftp>mput f*
|
| Checking Which CDF's Have Been Made |
- The day after the files are sent, CDHF sends status
report via email. Check to confirm they recieved all of
the files you sent.
- They also update their website at ftp://cdaweb.gsfc.nasa.gov/pub/istp/fast .
Use this site also to find out which CDFs have been made
in the past and which ones you should make.
- There is also a log of dailies that have not worked in the
past, Bad Dailies.
|
Webpage maintained by Webster.
|
