You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Processing Status

The current status is available at http://glast-ground.slac.stanford.edu/DataProcessing/

When ASP falls over, rollback at either the process level or the stream level.

Adding Monitored Sources

Jim runs a script based on ATels by the FA list.

From Jim:

The "insert_pointsource.py" script is what I use to add a monitored source to the FSSC list, and I use it with this page: https://confluence.slac.stanford.edu/display/SCIGRPS/New+DRP+sources+based+on+ATels which you've probably seen.  I'll put together more detailed notes on the full procedure and will check that into to the above repository.

Code Development

Pipeline code is in CVS at  http://glast.stanford.edu/cgi-bin/viewcvs/users/jchiang/ASP/

Code runs under glast-raw.

No CCB process for changes

Leap Seconds

Putting Leap Seconds in. Requires testing. Needed for the GRB ID assignation. 

Confluence page about Leap Seconds. Rob has tried to gather information: https://confluence.slac.stanford.edu/display/ISOC/Leap+Second+Adjustments

 Install Procedures

See the contents of install_procedures.txt in http://glast.stanford.edu/cgi-bin/viewcvs/users/jchiang/ASP/

From Jim:

The "install_procedures.txt" file is my rather elliptical description of all the steps needed to update the ASP software with a new release, so it points to all of the software elements I mentioned this morning. I'll try to clarify it over the next few days, so if you have any questions on it, please let me know.

Running the ASP Cron Job

The cron jobs are running from Jim's account.
If the cron job that sends the ASP file to the FSSC fails, it can be run manually.  The command to create and send the package is simply:
/afs/slac/g/glast/ground/links/data/ASP/makeDrpLcTables.sh

If you log into a rhel6-64 machine at SLAC, you should just be able to issue that command assuming you have the right permissions.  You need to be a member of the AFS group g-glast-new:flightops-oracle and account name has to be listed in the Oracle table FCOPY_SUBMITTER.
The script does not automatically bump the file version number, so running it twice in a row will cause the data with the same file name to be sent to the FSSC.   You can wait  at least six hours to issue the command again since that is the interval between PGWAVE/DRP runs.

You can check the FASTCopy delivery status here: http://glast-ground.slac.stanford.edu/FCWebView/?tabMode=Outgoing
That will show any scheduled ASP deliveries either pending or sent.  If you don't see an entry there for that day, then it would need to be done by hand.

 

If you get an error like:
FASTCopy.py --send GSSC gll_asp_0509328000_v00.fit
FASTCopy: creating transfer package "/nfs/farm/g/glast/u23/ISOC-flight/Outgoing/LISOC_2017052205255.tar"
(Connection failed) (DatabaseError) ORA-12154: TNS:could not resolve the connect identifier specified

You are likely not a member of the AFS group g-glast-new:flightops-oracle. Steve, Rob, Gegg and Jana can add members to this group. After you are added, as a simple test, you should be able to read the file /afs/slac/g/glast/isoc/flightOps/oracle/admin/tnsnames.ora.
If you get any error like:
eval `/afs/slac/g/glast/isoc/flightOps/rhel5_gcc41/ISOC_PROD/bin/isoc env --add-env=flightops`; FASTCopy.py --send GSSC gll_asp_0509414400_v00.fit
FASTCopy: creating transfer package "/nfs/farm/g/glast/u23/ISOC-flight/Outgoing/LISOC_2017053202355.tar"
FASTCopyDB::Send: horner is not in GroupManager groups ('glastops_planners',)
Your account name is not listed in the Oracle table FCOPY_SUBMITTER.  The complaint about the glastops_planners group was a red herring. Steve has fixed it.


 
  • No labels