ebook img

The SPIRE Photometer Interactive Analysis Package SPIA PDF

0.18 MB·
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview The SPIRE Photometer Interactive Analysis Package SPIA

**VolumeTitle** ASPConferenceSeries,Vol.**VolumeNumber** **Author** (cid:13)c**CopyrightYear**AstronomicalSocietyofthePacific The SPIREPhotometer Interactive AnalysisPackageSPIA 1 BernhardSchulz 1 0 California InstituteofTechnology, 2 MC100-22,770SouthWilsonAve.,Pasadena,CA91125, USA n a Abstract. TheHerschelCommonScienceSystem(HCSS)(Ottetal.2006) J (Ott&ScienceGroundSegmentConsortium2010)isasubstantialJavasoftwarepack- 6 age,accompanyingthedevelopmentoftheHerschelMission(Pilbrattetal.2010),sup- portingall of its phases. In particularthe reductionof data fromthe scientific instru- ] mentsforinstrumentcheckout,calibration,andastronomicalanalysisisoneofitsmajor M applications.Thedatareductionsoftwareissplitupinmodules,called”tasks”.Agreed- I uponsequencesoftasksformpipelinesthatdeliverwelldefinedstandardproductsfor . h storageinaweb-accessibleHerschelScienceArchive(HSA)(Leonetal.2009). How- p ever, as astronomers and instrument scientists continue to characterize instrumental - effects, astronomers already need to publish scientific results and may not have the o timetoacquireasufficientlydeepunderstandingofthesystemtoapplynecessaryfixes. r t Thereisaneedforintermediatelevelanalysistoolsthatoffermoreflexibilitythanrigid s pipelines. a [ The task frameworkwithin the HCSS and the highlyversatile HerschelInterac- tiveProcessingEnvironment(HIPE),togetherwiththerichsetoflibrariesprovidethe 1 necessary tools to develop GUI-based interactive analysis packages for the Herschel v instruments. The SPIRE Photometer Interactive Analysis (SPIA) package, that was 4 demonstratedin this session, provesthe validity of the conceptfor the SPIRE instru- 8 ment(Griffinetal.2010),breakingupthepipelinereductionintologicalcomponents, 2 making all relevant processing parameters available in GUIs, and providing a more 1 controlledanduser-friendlyaccesstothecomplexitiesofthesystem. . 1 0 1 1 : v 1. PipelineProcessingversusInteractive Analysis i X Ideally the raw telemetry data that is downlinked from an instrument aboard the Her- r a schel spacecraft, is processed in some automatic sequence of processing steps, invert- ingthetransformation functionoftheinstrument. Theresultingfluxesforagivenfilter band and position on the sky are finally made available to the astronomer through the HSA(Leonetal.2009). Thisisaneasyandstraight forwardprocedure. However,this approach offersnoflexibility. Theother extremeistoeditandmodify thepipeline script according totheneeds of the particular data sets. This offers a maximum of flexibility and is usually needed by instrument experts. The need arises particularly during the early phases of a space observatory mission, when the modules that make up a data reduction pipeline aren’t mature yet. Science quality results can also be derived in this way, but they require a substantial investment of time and effort on the side of the astronomer to gather the necessary expertise, learn the intricacies of the scripting language, and the contents of theavailable softwarelibraries. 1 2 Schulz Thisisnotaneconomicwayforthegeneralscientistwhoneedstolimitthedepth ofhisinstrumentinvolvementtoareasonablelevel. Inthiscase,aninteractivemodular approach, providing guidance via GUIs, retains a limited amount of flexibility while avoiding theneedtolearnaboutthescripting language indepth. The typical work pattern consists of loading data, inspecting it, and then repro- cessing it with the newest calibration products and algorithms. After that the data is inspected again and possibly processing parameters are changed before reprocessing another time. Whenthe quality oftheintermediate processing level issatisfactory, the analyst advances to the next major step in asimilar iterative way. Atthe end there are manyresultsofwhichsomearetobesavedforlater. This scenario results in certain requirements, like simple data retrieval from the HSA, ability of easy data inspection, and the need to split the general workflow into smallerpipelineblocks. Itisalsonecessarytohaveinteractiveaccesstotheprocessing parameters via a GUI.Finally, the I/O of observational data must be simple and refor- mattingofoutputproductsforfurtherprocessingbyexternalastronomical applications shouldbeprovided. 2. Implementation Anearly example of aninteractive analysis for astronomical space missions, designed toprovideguidancethroughGUIstotheastronomer,wasshownbyGabrieletal.(1997) as an IDL implementation for the ISOPHOT instrument (Lemkeetal. 1996). We de- scribe here the implementation of the SPIREPhotometer Interactive Analysis (SPIA), whichisbasedonthetaskframeworkoftheHerschelCommonScienceSystem(Ottetal. 2006;Ott&ScienceGroundSegmentConsortium 2010)anditsinteractive processing environmentHIPEforthephotometerpartoftheSPIREinstrument(Griffinetal.2010) on board of Herschel (Pilbrattetal. 2010). The instrument was chosen because of the author’sclosefamiliaritywithit,buttheconceptassuchisapplicable totheotherHer- schelinstruments andsub-instruments aswell. Thepackage resides inaJython fileincluding severalclasses, eachrepresenting a separate task. The task framework provides automatic GUI’s for all input and output parameters that are defined in an initialization section in the code, thus avoiding time consumingSWINGprogramming. Thedefinitionsincludedefaultvalues,variabletype definitions, aswellastextforGUItooltips, contributing touser-friendliness. The general structure is shown in Figure 1. The tasks are drawn in blue, data repositories are shown in orange, and products within the HIPE session are shown in yellow. Many viewer and data manipulation tools were already available in HIPE and canbeusedalongwiththenewtasks. Alltasksusetheobservationcontextasahandle, which is an object with pointers to all other data products the observation consists of. Tasks perform I/O of observations and calibration products, as well as the interactive processing tothelevels0.5, 1,and2, representing i)datainengineering units, ii)flux- calibratedtimestreamswithsky-positions,andiii)reconstructedskymapsrespectively. Figure2showsascreenshot ofaHIPEsession withatypical arrangement ofcer- tain views, showing the task GUI, the command line, variables, tasks, and the internal outline ofanobservation context. Anumberofviewersforsignal timelines, flags, and mapdataareavailable thatcannotbeshownhereforlackofspace. An important improvement compared to prior implementations of the Interactive Analysis concept, is the implicit command line support of the task framework. Exe- TheSPIREPhotometerInteractiveAnalysisPackageSPIA 3 Figure 1. Block diagram of the different components of the SPIA. Processing tasksthatarecontrolledviaGUIsareshowninblue,datarepositoriesareinorange, anddataproductsheldwithintheHIPEsessioninmemoryareshowninyellow. Figure2. ScreenshotofaHIPEsessioninatypicalarrangementofviews(HIPE perspective)fortheusewithSPIA,showingthetaskGUI,commandlineview,vari- ablesview,tasklistview,andoutlineview. Theoutlineviewshowsanobservation contextthatincludesathumbnailofaLevel2map. 4 Schulz cuting a task by hitting the ”Accept” button in the GUI, will also create a command linethatcanbeincludedintoaJythonscripttorepeatthesamereduction procedure on otherdatasets. Thustheinteractiveanalysis canbeusedasapathfinder tooptimizethe datareduction, producing templatescriptsforlaterautomaticbulkprocessing oflarger datasets withoutobligating theastronomer tolearnalotaboutscripting. A challenge will be to keep the package in sync with the still quite rapid devel- opment of the SPIRE pipeline and HIPE. A possible solution is the integration of the packagewithHIPEtobenefitfromthetestharnessesthatcouldpointoutanyinconsis- tenciesalreadyduring thebuildprocess. The SPIA package is currently still distributed separately via the website of the NASAHerschelScienceCenter(NHSC)atIPAC/Caltechathttps://nhscsci.ipac. caltech.edu/sc/index.php/Spire/SPIA. The package comes in two forms: 1) a Jython script that needs to be executed in HIPE first, in order to have all tasks of the SPIAavailable, 2)aHIPEpluginthatneedstobeinstalled onlyonce, butisonlycom- patible withversion 5of HIPEand above. HIPEcan be downloaded from the website ofthetheESAHerschelScienceCentre(HSC)inSpainathttp://herschel.esac. esa.int/HIPE_download.shtml. AusermanualforSPIAisavailable aswellatthe NHSC site. The package is already being used successfully within the SPIRE instru- mentteamandbysomeofthegeneralusers. Animplementationofthisconceptforthe spectrometer partofSPIREisanticipated. Acknowledgments. TheHerschelInteractiveProcessingEnvironment(HIPE)isa jointdevelopmentbytheHerschelScienceGroundSegmentConsortium,consistingof ESA, the NASA Herschel Science Center, and the HIFI, PACS and SPIRE consortia. The author thanks the colleagues from the HSC, the NHSC, and the SPIRE ICC for valuable comments and suggestions. Special thanks go to Lijun Zhang, Dave Shupe, AnnieHoac,PaulBalm,JaimeSaiz,JavierDiaz,JorgoBakker,andStephanOtt. References Gabriel, C., Acosta-Pulido, J., Heinrichsen, I., Morris, H., & Tai, W. 1997, in Astronomical Data Analysis Software and Systems VI, edited by G. Hunt & H. Payne, vol. 125 of AstronomicalSocietyofthePacificConferenceSeries,108 Griffin,M.J.,etal.2010,A&A,518,L3+.1005.5123 Lemke,D.,etal.1996,A&A,315,L64 Leon, I., et al. 2009, in Astronomical Society of the Pacific Conference Series, edited by D. A. Bohlender, D. Durand, & P. Dowler, vol. 411 of Astronomical Society of the PacificConferenceSeries,438 Ott,S.,&ScienceGroundSegmentConsortium2010,inAmericanAstronomicalSocietyMeet- ingAbstracts,vol.216ofAmericanAstronomicalSocietyMeetingAbstracts,413.10 Ott, S., et al. 2006, in Astronomical Data Analysis Software and Systems XV, edited by C. Gabriel, C. Arviset, D. Ponz, & S. Enrique, vol. 351 of Astronomical Society of thePacificConferenceSeries,516 Pilbratt,G.L.,etal.2010,A&A,518,L1+.1005.5331

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.