Page History
...
Property | Value | Comment |
|---|---|---|
freehep.app.hep.wired.glast.gleam.defaultRunEventServer | http://glast-ground.slac.stanford.edu/DataPortalWired//EventFinder | Tells WIRED what web service to use to look for events |
freehep.app.hep.wired.glast.gleam.defaultDatasetFinderServer | http://glast-ground.slac.stanford.edu/DataPortalWired//DatasetFinder | Tells WIRED what web service to use to look for datasets |
freehep.app.hep.wired.glast.gleam.runEventServer.folder | 11628535 | The primary key of the data catalog folder |
freehep.app.hep.wired.glast.gleam.defaultScript | /u/gl/glast/heprepserver/4.1/ssh_gleam_server | The script used to start Gleam |
Web Services
org.glast.dataportal.wired.DatasetFinderServlet
...
This is all done in hep.wired.glast.HepEventServerRecordSource
Outstanding Issues
- WIRED does handle rel files, but most of the eventComponents in the data catalog do not point to the rel event component (51306242 /MC-Tasks/ServiceChallenge/backgnd-GR-v17r16-53Day-OVRLY/runs digi=digi,reco=recon,mc=mc,rel=relation is an exception).
- WIRED does not seem to be able to open MERIT files when run in this mode. The web service does return the merit file if it is pointed to by eventComponents, but it is ignored by HepEventServerRecordSource. This should be easy to fix, except that I do not remember how to pass the MERIT file to gleam (an extra ;merit-file-location seems like a good guess).
- Random access to events is not supported when running in this mode, the list of run/events must be created when connecting to the server, and only these events can be viewed.
- When Gleam fails to open the files passed to it for any reason the end user just gets an obscure message saying "no such event".
- The version of Gleam run is hardwired into /u/gl/glast/heprepserver/4.1/ssh_gleam_server. The user can specify an alternative script, but this is very obtuse and not many people know how to do it.
Overview
Content Tools