gost software user manual - esa · cux gost software user manual gaia-cu1-ug-esac-jfh-005-01 2...

GOSTSoftware User Manual

prepared by: Jorge Fernandez-Hernandez and Emmanuel Jolietapproved by: Hassan Siddiquireference: GAIA-CU1-UG-ESAC-JFH-005-01issue: 1revision: 2date: 2016-11-14status: Issued

AbstractThis document is the Software User Manual for the Gaia Observing Schedule Tool(GOST).

CUxGOST Software User ManualGAIA-CU1-UG-ESAC-JFH-005-01

Document History

Issue Revision Date Author Comment1 2 2016-11-14 JO Update the documentation for the command line inter-

face (CLI)1 1 2016-10-28 JO Include information about the statistic numbers1 0 2016-09-27 JFH Document issued.D 4 2016-09-27 HS Minor comments.D 3 2016-06-27 JFH Correct minor typos. Add extra information for Aladin

Lite.D 2 2015-06-09 JO Update urls to new schemaD 1 2014-06-24 EJ Move installation part to TN EJ-012D 0 2014-06-09 EJ First draft

Software User Manual 2


Contents

1 Introduction 4

1.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Definitions, acronyms, and abbreviations 5

3 Overview 6

4 The Web services 6

4.1 Gaia status metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.1.1 MDB queries for the totals . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.1.2 MDB queries for last 24h . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1.3 Science data statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1.4 Distance from Earth . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.1.5 Days since start of the mission . . . . . . . . . . . . . . . . . . . . . . . 9

4.1.6 Percentage of completion . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.1.7 URL and sample output . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.2 Gaia position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.3 Gaia Live position in GE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.4 Gaia contact planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.5 Direct query by name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.6 Direct query by coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15



5 The Web interface 16

5.1 Login tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.1.1 versions tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.1.2 Tools tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6 Command line interface 24

7 References 28

A Output format 29

1 Introduction

1.1 Objectives

This document is the Software User Manual for the Gaia Observing Schedule Tool (GOST). TheGOST is a tool to provide a means by which the general astronomer can determine the times atwhich Gaia will observe a given position during the course of its mission.

The tool consists of two parts. A web application permits the user to get the event time of target(s)via a web form interface. The same web application also offers several web services that can beused to retrieve different metrics, such as the contacts planning data, the number of transits, etc.

The web application gets the data from specific GOST data tables. These metrics are populatedand updated regularly via the MDB Data Manager (MDB).

1.2 Scope

The scope of this document is to provide generic usage instructions for the GOST. Specificinstructions and procedures how to use the tools in the SOC environment in combination withthe other software running in the SOC will be covered in section 6.

This issue of the document is applicable for GOST software release 17.0.0.



2 Definitions, acronyms, and abbreviations

The following is a complete list of acronyms used in this document.

The following table has been generated from the on-line Gaia acronym list:

Acronym Description2MASS Two-Micron All Sky SurveyAF Astrometric Field (in Astro)AOCS Attitude and Orbit Control Sub-systemAPI Application Programming InterfaceCCD Charge-Coupled DeviceCSV Comma-Separated Value (database output format, e.g., for MS Excel)DEC DeclinationDIAC Data Integrity and Accountability ChecksDPAC Data Processing and Analysis ConsortiumEPSL Ecliptic Pole Scanning LawFOV Field of View (also denoted FOV)FPA Focal Plane Assembly (Focal Plane Array)FoV Field of View (also denoted FOV)GOST Gaia Observation Scheduling ToolHTML HyperText Markup LanguageICRS International Celestial Reference SystemIDT Initial Data Treatment (Image Dissector Tube in Hipparcos scope)IOGA Initial On-Ground AttitudeISO International Organisation for Standardisation (Geneva, Switzerland)JSP Java Server PageMAINDB MAIN DataBaseMDB Main DataBaseMSL Modified Scanning LawOPS Object Processing SystemRA Right AscensionRSLS Reference Scanning Law ScheduleSDSS Sloan Digital Sky SurveySOC System On a ChipSRS Software Requirements SpecificationTCB Barycentric Coordinate TimeTN Technical NoteUB University of Barcelona (Spain)UI User Interface



UTC Coordinated Universal TimeWFS WaveFront SensorXML eXtensible Markup Language

3 Overview

GOST web interface deliver data stored in GOST tables. Those tables are updated externally viathe MDM, MDB Data Manager.

A main class will be listening to MDM queue while GOST is registered to it. Whenever a newsource or a cross-matched source is being confirmed and ingested in MAINDB, a message issent. GOST will update metrics table with this information.

Timeline table in IDTFLOPS will be consult in order to get recent total number of transit pro-cessed.

See section 6 for more details about configuration properties needed and on how to run the MDMlistener.

4 The Web services

GOST web application offers several web services that delivers basic metrics in different outputformat.

This services are typically servlets running in the application server. They can either be calledfrom browser or CLI with wget for instance.

They are accessed with the same url root:

http://gaia.esac.esa.int/gost/

The available services are described below.


http://gaia.esac.esa.int/gost/


4.1 Gaia status metrics

Gaia should provide estimates of various mission progress figures. This is achieved best by im-plementing a single service which then can be used by all stakeholders (Cosmos web-pages, Gaiaapp, management presentations, etc.). Of course they should be robust (i.e. always available) andconsistent (e.g. the cumulative number of transits should not go down).

Current GOST implementation is based on the MDB REST API providing DIAC data about theproducts ingested in the MDB.

4.1.1 MDB queries for the totals

These are the REST queries done to retrieve the totals since the start of the operational phase:nSp1 = CountsQueryModel

dmClassName = "gaia.cu1.mdb.cu1.rawdata.dm.Packet"misc = [!fileId=151%, !fileId=161%, !fileId=171%,

!fileId=181%, !fileId=183%, !fileId=185%, %type=SP1%]revolutionNumber >= 1077

nSp2 = CountsQueryModeldmClassName = "gaia.cu1.mdb.cu1.rawdata.dm.Packet"misc = [!fileId=152%, !fileId=162%, !fileId=172%,

!fileId=182%, !fileId=184%, !fileId=186%, %type=SP2%]revolutionNumber >= 1077

nPOs = CountsQueryModeldmClassName = "gaia.cu1.mdb.cu3.idt.raw.dm.PhotoObservation"misc = [ ]revolutionNumber >= 1077

nSOs = CountsQueryModeldmClassName = "gaia.cu1.mdb.cu3.idt.raw.dm.SpectroObservation"misc = [ ]revolutionNumber >= 1077

VO/SVO are explicitly filtered from the raw packets (SP1/SP2) and they are not part of the photoand spectro observations neither as they use different class types in these cases.



4.1.2 MDB queries for last 24h

For last 24h, we use the same queries but with the revolution resulting from the following code:EarthTime time = TimeFactory.newCurrentTime();long elapsedNanoSecs = time.getElapsedNanoSecs();long obmt = TimeFactory.newGaiaTime(elapsedNanoSecs).toObmt();int rev = (int) (4 * obmt / 1000000000L / 86400L);

int toRev = rev - 2; // Includes a 12h delays for data processingint fromRev = toRev - 4; // Covers a 24h period

4.1.3 Science data statistics

Finally these numbers are mapped into the desired statistics:

nTransitsObserved = nSp1nStarsPassedRVS = nSp2

nPhotometricMeasurements = 2 * nPOsnSpectroscopicMeasurements = 3 * nSOs

nAstrometricMeasurements = 69/7 * nSp1= (10 * 6/7 * nSP1 + 9 * 1/7 * nSP1)

--> Includes SM CCD--> Removes WFS packets:

We assume sources are equally distributed between the seven rows--> Some NULL valued windows for those measurements in SP1 (and SP2)

will appear when the window has moved out of the focal plane dueto cross scan motion of the s/c attitude.However, these numbers are so small that there is no pointto worry about it.

scienceVolumeReceived = (nSp1 * SP1_RATIO + nSp2 * SP2_RATIO) / GB_SIZE--> Current constant values are:

SP1_RATIO = 306.23SP2_RATIO = 3982.12



4.1.4 Distance from Earth

The distance from the spacecraft to Earth is taken from the ephemeris data:earthPos = GaiaFactory.getEphemerisProvider().

getEphemeris(Body.EARTH).getPosition(time);gaiaPos = GaiaFactory.getEphemerisProvider().

getEphemeris(Body.GAIA).getPosition(time);

distGaia2Earth = (earthPos.sub(gaiaPos).norm() - GaiaParam.Nature.EARTH_EQUATORIALRADIUS) / 1000; // km

4.1.5 Days since start of the mission

This value is taken as the difference between current data and 2014-07-25T02:14:47.343

4.1.6 Percentage of completion

This percentage is calculated as the difference between previous value (days since start of themission) compared to:

GaiaParam.Mission.LIFETIME_OPERATIONALPHASE_NOMINAL (5years)+ GaiaParam.Mission.LIFETIME_OPERATIONALPHASE_EXTENDED (1year)



4.1.7 URL and sample output

This service is located at

http://gaia.esac.esa.int/gost/gstat

The output is rendered as a JSON format, self explained structure key-value pair like the oneshown below:{

"GENERATED_TIME":"2016-10-25T14:44:01 (TCB)","MISSION_STATE_DATA":{

"SAT_DIST_FROM_EARTH":"1489215.445","MISSION_PERCENT_COMPLETED":"47.51%","DAYS_SINCE_OPS_START":"823.52"

},"MISSION_OPERATIONS_DATA":{

"ASTROMETRIC_MEASUREMENTS":"559203767610","SPECTROSCOPIC_MEASUREMENTS":"10951471719","RVS_OBSERVED":"3570765020","PHOTOMETRIC_MEASUREMENTS":"119616355502","GB_RECEIVED":"29422.242","TRANSITS_OBSERVED":"56730817004"},

"MISSION_OPERATIONS_DATA_24h":{"ASTROMETRIC_MEASUREMENTS":"0","SPECTROSCOPIC_MEASUREMENTS":"0","RVS_OBSERVED":"0","PHOTOMETRIC_MEASUREMENTS":"0","GB_RECEIVED":"0.000","TRANSITS_OBSERVED":"0"

}}


http://gaia.esac.esa.int/gost/gstat


4.2 Gaia position

It is mainly designed for outreach. It is located at

http://gaia.esac.esa.int/gost/gpos

The output is rendered as a plain text CSV of ra (deg), dec (deg) and distance (Km) from earth.For Example:87.824413058148,29.593426965927755, 1600254.782243192

4.3 Gaia Live position in GE

It is mainly designed for outreach. It is located at

http://gaia.esac.esa.int/gost/gkml

The output is rendered as a KML file1. For example:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/

kml/ext/2.2" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:xal="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0" hint="target=sky"><Document>

<name>ESA Gaia satellite</name><open>1</open><styleUrl>#Gaia</styleUrl><Style>

<BalloonStyle><text><text><center><b>Gaia</b></

center><br/>Position the 2016-06-27T14:29:56 (UTC)</text></text>

</BalloonStyle></Style><Placemark>

<name>Gaia</name><description>Gaia position seen from Earth at 1622975.4497314037

kms from us the 2016-06-27T14:29:56 (UTC)</description><LookAt>

<longitude>5.621809218570988</longitude><latitude>30.027379116517448</latitude><altitude>0.0</altitude><heading>0.0</heading><tilt>0.0</tilt>

1KML is an open standard officially named the OpenGIS KML Encoding Standard (OGC KML). It is maintainedby the Open Geospatial Consortium, Inc. (OGC). The complete specification for OGC KML can be found athttp://www.opengeospatial.org/standards/kml/.


http://gaia.esac.esa.int/gost/gpos

http://gaia.esac.esa.int/gost/gkml

http://www.opengeospatial.org/standards/kml/


<range>10000.0</range></LookAt><Point>

<coordinates>5.621809218570988,30.027379116517448</coordinates>

</Point></Placemark>

</Document></kml>

4.4 Gaia contact planning

It delivers the contact planning. It is mainly used by UB in mobile app. It is located at

http://gaia.esac.esa.int/gost/plnview

The output is rendered as a JSON format, self explained structure key-value pair. For example:

{ "Next": {"Station":"Malargue","End":"2014-06-10T08:00:58 (UTC)","Status":"Downloading to Malargue (MLG)","Start":"2014-06-09T23:21:43 (UTC)","Duration":"8.65h"

},"Contact" : {

"Status":"Scanning","Request":"2014-06-09T15:00:52 (UTC)"

}}

4.5 Direct query by name

A direct REST (representational state transfer) query can either be called from CLI or browserskipping the web UI. In order to query for a given object, we should make of the following queryparameter:

http://gaia.esac.esa.int/gost/GostServlet?name=target

where target is the object we are interested in. The complete output result is rendered in XMLformat. For example, for the target m31:

http://gaia.esac.esa.int/gost/GostServlet?name=m31


http://gaia.esac.esa.int/gost/plnview

http://gaia.esac.esa.int/gost/GostServlet?name=target

http://gaia.esac.esa.int/gost/GostServlet?name=m31


In this particular case, it makes used of VizieR name resolver by default. To change it, add aservice code:

http://gaia.esac.esa.int/gost/GostServlet?name=target&service=code

where ”&service=code” is an integer code such

• code=0 corresponds to Vizier2,

• code=2 corresponds to NED3,

• code=1 corresponds to Simbad4.

For example, the output of the parameter query

http://gaia.esac.esa.int/gost/GostServlet?name=m31&service=2

is rendered as<?xml version="1.0" encoding="UTF-8"?><gost>

<creationTime>Mon Jun 09 16:16:03 UTC 2014(id=1402330563[ns])</creationTime>

<attitudeDataServerId>OPS_RSLS_0021792 - with segments: EPSL_P [2013-12-01T12:00:00 (TCB)], ( /olddisk/jworkspace/Gost/./conf/OPS_RSLS_0021792_rsls_launch_minus_5_weeks_epsl_comm_leading_TUNED2014-03-12.xml )Segment #0: new EPSL from 2013-12-01T12:00:00.000000000 (TCB), at which time nu = 3.9252311467094363E-16 rad

</attitudeDataServerId><startTime>2013-12-19T09:55:44.848 (TCB)</startTime><endTime>2019-06-20T06:13:47.564 (TCB)</endTime><targets>

<target><name>m31</name><id>0</id><coords>

<ra>0.18648476538416495</ra><dec>0.7202809762030913</dec>

</coords><startTime>2013-12-19T09:55:44.848 (TCB)</startTime><endTime>2019-06-20T06:13:47.564 (TCB)</endTime><events>

<event><eventDate>2014-06-03T07:42:25.721 (TCB)</eventDate><details>

2The VizieR service at CDS.3The NASA/IPAC ExtraGalactic Database at the California Institute of Technology (CalTech).4(The SIMBAD Astronomical Database at the Centre de Donnes astronomiques de Strasbourg (CDS).


http://gaia.esac.esa.int/gost/GostServlet?name=target&service=code

http://gaia.esac.esa.int/gost/GostServlet?name=m31&service=2


<ccdStripNo>11</ccdStripNo><angleToZaxis>-0.006304476884000062</angleToZaxis><acCcdCoordinate>941.2769686665949</acCcdCoordinate><fov>FOV1</fov><normAcTransitPosition>-1.0458093599016887</

normAcTransitPosition><scanAngle>2.650496278163309</scanAngle><pfovdir>11.189611786167962 41.32503010325796</pfovdir><ffovdir>221.23189862531535 26.70356250924403</ffovdir>

</details></event>

</events><sm2>39</sm2><sm1>36</sm1>

</target></targets><message>COMPLETED - Target(s) 1 added (SM1+SM2 75 hits).</message><status>COMPLETED</status><sm2>39</sm2><sm1>36</sm1><ephemId>SOLUTIONID = 1580842634044243973</ephemId>

</gost>

See Appendix A for more detail about the element definition of the XML output.

4.6 Direct query by coordinates

The source target can also be queried by its astronomical coordinates ra and dec coordinates indegrees:

http://gaia.esac.esa.int/gost/GostServlet?ra=ra_in_degree&dec=dec_in_degree

The output is rendered in XML format.

See Appendix A for more detail about the element definition of the XML output.

It is also possible to resolve the name of the target making use of the following query

http://gaia.esac.esa.int/gost/GostServlet?name=target&service=code&resolve”





FIGURE 1: Form view page for one year prediction of m31 object.

5 The Web interface

The web interface consist mainly in a webform accessed via the main page index.jsp5. Theuser input should be:

• the target name,

• the astronomical coordinates (ra and dec) in degrees,

• a 3 column CSV text file, each line with an identifier, right ascension and declination.

For example figure 1 displays the webform for the target m31 (resolved by clicking on the bluebutton below target name) and period of one year prediction.

5JSP is a file extension for Java Server Pages file format. A JSP is an HTML page containing a reference to Javaservlets, or, java server side applets.



The results will appear in the result.jsp page (see figure 2). This page keeps an history ofthe previous query result. The table displays the report id, status, message, created date, coverageperiod prediction time and links to other output format (XML, CSV,etc.). See Appendix A formore details. When clicking on the id number of the report on the most left-hand column ’ID’cell, the calendar view will open in a different window showing the result in a calendar outputformat. This is the main report view. Each cell dark coloured represent a potential observation.A detail result of the events can be displayed by clicking on a particular darker cell (day ofpredicted observation). The calendar can be navigated by two buttons above on 6 months basis.Example of the calendar view for m31:

FIGURE 2: Calendar view page for one year prediction of m31 object.

The result can be exported in different ways, each of them contain the time of the FPA transitspotentially seen by Gaia. This is not a full guarantee of getting the transits observed. Thetarget(s) could have been crossing the FoVs but for different reasons, the observed transits didn’tget downlinked and/or processed.

In routine phase, GOST will compute the transit crossing the FoVs based on the routine nominalscanning law.

A different page - properties.jsp - will show information regarding the scan law used tocompute the resulting time events. Other extra added information should be found there.



5.1 Login tab

DPAC access page (auth.jsp) displays a login username and password fields to authenticatethe DPAC user and enable full details output mode. Figure 3 displays the main authenticationwebform. The authentication required MyPortal credentials. The authenticated user will beredirected automatically to the home page (index.jsp) with the extra tabs Versions andTools (see the following section) as well as its username in bold format indicating full GOSTdetails output mode is enabled.

FIGURE 3: Authentication page.

5.1.1 versions tab

As we have pointed out before, once the user successfully login the system, there will a newversion tab available. Figure 4 shows the versions page. It displays basic information for:

• the attitude data server. It shows the main class in GaiaTools that should be used inorder to get access to the attitude. Clicking on ”[click to expand info]” more detailsabout the attitude is displayed (see Figure 5);

• the Ephemeris/Attitude coverage period valid. It provides the time range for the forwhich the Ephemeris/Attitude is valid;

• specific information for the ephemeris.

5.1.2 Tools tab

The Tools tab provides extra handy functionalities for the satellite. Figure 6 displays the mainTools page. As can bee seen, it contains the following options.



FIGURE 4: Versions page.

• Where is Gaia now? Clicking in this button downloads the file gaia live.kml6. Itcan be opened with Google Earth and it will get position of Gaia (plus the distant toEarth) each 5 seconds.

• The What is Gaia AOCS mode now? button displays the Attitude and Orbit ControlSub-system (AOCS) mode used by Gaia. An example of the result is displayed inFigure 7.

• The Get Downlink/Contact status (JSON) button generates the Downlink/Contactstatus in json format

• The Get Gaia position (ra[deg], dec[deg], distance[km] from Earth) (CSV) providesthe right ascension and declination, in degrees, as well as the distance from Earth ofthe satellite in km. The information is displayed as comma-separated values.

• The Get Gaia metrics (JSON) button displays the Gaia metrics in json format. Seethe example shown in the json file displayed in section 4.1.

• The Go to FoV visualization tool button displays the fields of views (FOV) of thesatellite making use of the VirtualSky application7. The following are the main op-tions that can be selected by the user:

6Keyhole Markup Language (KML) is an XML notation for expressing geographic annotation and visualizationwithin Internet-based, two-dimensional maps and three-dimensional Earth browsers. KML was developed for usewith Google Earth.

7VirtualSky a browser-based planetarium from LCOGT that lets you see what is visible in the sky from anylocation on Earth. http://http://virtualsky.lcogt.net/


http://http://virtualsky.lcogt.net/


FIGURE 5: Expand version of the Version page. The information displayed on Figure 4 is basedon the XML configuration file displayed in red.

– The Gaia FOV;

– the rate for the data updating;

– the initial UTC time. The button Set time to now sets the time to the presentUTC time;

– and the time step.

In order to start the application, the user must press the play button. A blue or yellowsquare symbol for the Preceeding FOV or Folowing FOV, respectively, will appear atthe sky image with its corresponding date, representing the position of the satellite.The user can zoom in/out the displayed image making use of the mouse. Note thatthe user can get extra information pressing keyboard ’1’. The pause button stops theapplication.



• The Go to FoV+SDSS view tool button displays similar information as the previousone, but it also shows the sky observed by the SDSS catalogue (upper picture inFigure 9), making use of Aladin Lite8. Note that it is possible to select a differentastronomical catalogue making use of the drop down menu of the Aladin lite win-dow. The options that can be selected by the user are similar to the ones previouslydescribed.

FIGURE 6: Tools page.

FIGURE 7: Result of the What is Gaia AOCS mode now? button.

8Aladin lite is a lightweight version of the Aladin Sky Atlas, running in the browser and geared towards simplevisualization of a sky region. http://aladin.u-strasbg.fr/AladinLite/doc/.


http://aladin.u-strasbg.fr/AladinLite/doc/


FIGURE 8: FoV visualization tool page.

.



FIGURE 9: FoV visualization tool and SDSS page.



6 Command line interface

GOST predictions can be obtained from CLI. The syntax of the script is as follows:Usage: bin/runGost.sh

[-h|--help][(-a|--attitude) <attitude>][(-s|--service) <service>][(-n|--name) <name>][(-r|--ra) <ra>] [(-d|--dec) <dec>] [-o|--torad][(-f|--tfrom) <tfrom>] [(-t|--runto) <runto>][(-i|--filein) <filein>]

[-h|--help]Print this message

[(-a|--attitude) <attitude>]Attitude data server can be: NSL37, EPSL, EpslAndNsl, MSL, SCHED or

COMB

[(-f|--tfrom) <tfrom>]Covered attitude from this time [ex.: J2012.0 or2012-01-01T12:00:00.000000000 (TCB) (default: J2014.0)

[(-t|--runto) <runto>]RSLS coverage time duration [i.e. 5yr] (default: 5.0yr)

[(-i|--filein) <filein>]Input file containing at least first 3 columns such as name, alpha,delta in radians (if in deg, use flag to convert)

[-o|--torad]If present, it will convert the input angle in radians

[(-r|--ra) <ra>]ICRS (EQU) RA in rad (default: 0.0)

[(-d|--dec) <dec>]ICRS (EQU) DEC in rad (default: 0.0)

[(-s|--service) <service>]Name resolver service - could be starting capital letter (V)izier,(N)ED, (S)imbad or (A)ll (default: )

[(-n|--name) <name>]Name to be resolved (default: m31)



In order to execute the previous command the GOST package must be downloaded from the Gaiasubversion service and the jar, including all the dependecies, created using the ’jarComplete’ anttarget.

The local gost properties are to be found where you define the -Dgaia.cu1.tools.util.prop.propdirsproperty flag. In the above script, the env.gost.properties has to be found under local folder name’envprops’.

Example of env.gost.properties:# Ephemer i s d a t a s t o r e p r o v i d e rg a i a . cu1 . t o o l s . d a t a . G e n e r i c D a t a P r o v i d e r = g a i a . cu1 . t o o l s . d a t a . G B i n S t o r e D a t a P r o v i d e rg a i a . cu1 . t o o l s . d a t a . G B i n S t o r e D a t a P r o v i d e r . s t o r e L o c a t i o n = . / d a t a / eph

# IDTFLDB MIRROW# g a i a . cu1 . t o o l s . d a t a . G e n e r i c D a t a P r o v i d e r = g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r# g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . d r i v e r =com . i n t e r s y s . j d b c . CacheDr ive r# g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . u r l = j d b c : Cache : / / g a i a l s 1 7 0 . n 1 d a t a . l a n : 5 6 7 7 2 / IDTFLOPSMIRROR# g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . username=∗∗∗∗∗∗∗∗# g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . password=∗∗∗∗∗∗∗∗

# De f i ne a t t i t u d e s e r v e r t o be used .g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r = g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . r s l s . S c h e d u l e d A t t i t u d e D a t a S e r v e r# g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r = g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . impl . n u m e r i c a l .

C o m b i n e d A t t i t u d e D a t a S e r v e r# g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . r s l s . S c h e d u l e d A t t i t u d e D a t a S e r v e r# g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . impl . a n a l y t i c a l . EpslAndNsl

g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r . l o c a t i o n = . / con f /O P S R S L S 0 0 2 2 9 1 6 r s l s n s l g a r e q 1 a f t e r F i r s t S p i n P h a s e O p t i m i z a t i o n . 2 . xml

# I f EPSLAndNSL a t t s e r v e r used , p l e a s e c o n f i g u r e t h e s e p r o p s t o o :g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r . s w i t c h =30dg a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r . t S t a r t =2012−01−01T12 : 0 0 : 0 0 . 0 0 0 0 0 0 0 0 0 (TCB)g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r . d u r a t i o n =5 yr

# I f CombinedServer a t t s e r v e r i s used , i t needs :g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . impl . n u m e r i c a l . I n c r e m e n t a l C o m b i n e d A t t i t u d e D a t a S e r v e r . a t t i t u d e = g a i a . cu3 . i d t f l . i d t . dm . Ioga g a i a

. cu1 . mdb . cu3 . a g i s . dm . Oga3 g a i a . cu1 . mdb . cu3 . f l . dm . Oga2 g a i a . cu1 . mdb . cu3 . i d t . i n t e r m . dm . Oga1g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . impl . n u m e r i c a l . C o m b i n e d A t t i t u d e D a t a S e r v e r . a t t i t u d e = g a i a . cu3 . i d t f l . i d t . dm . Ioga# g a i a . cu1 . mdb . cu3 . a g i s . dm . Oga3 g a i a . cu1 . mdb . cu3 . f l . dm . Oga2 g a i a . cu1 . mdb . cu3 . i d t . i n t e r m . dm . Oga1

g a i a . cu1 . o s t . s e r v i c e . G o s t S e r v i c e C l i e n t = g a i a . cu1 . o s t . s e r v i c e . sesame . S e s a m e C l i e n t

# g a i a . cu1 . o s t . u t i l s . s c a n t y p e =DEFAULTg a i a . cu1 . o s t . u t i l s . s c a n t y p e =FULL#FASTER

a g i s . s o u r c e . S o u r c e D i r e c t i o n = S o u r c e D i r e c t i o n G r e m I m p l

g a i a . cu1 . t o o l s . g o s t . web . s t a r t T i m e =2014−09−26T00 : 0 0 : 0 0#2013−12−20T00 : 0 0 : 0 0

# Java temp f o l d e r# ( used i n t h e g o s t r e p o r t s t o save memory )j a v a . i o . t m p d i r = .



Before execute this command we should provide the following inputs:

• Define the input file ’INPUT ASCII’, ascii format, three comma-separated columns:Name,RA(deg),Dec(deg) like

HIP104382,317.200797446,-88.9564792381HIP104385,317.197826281,-76.2125385922HIP104395,317.238948184,-5.5820777019

• START ISO DATE: Start ISO date of prediction UTC - i.e. ’2014-01-02T12:00:00.000’

• DURATION : Duration in days/months.years/etc of the predicted period - i.e. 30dwould be 30 days after Start date above

Taking these parameters into account, the resulting command would be:$ bin/runGost.sh --tfrom <START_ISO_DATE> --runto <DURATION>

--torad --filein <INPUT_ASCII>



If you want to predict in the past, you may be interested in using IOGA or any attitude data fromOPS db. In that case, the server property to define is:

# De f i ne a t t i t u d eg a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r = g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . impl . n u m e r i c a l .

C o m b i n e d A t t i t u d e D a t a S e r v e rg a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . impl . n u m e r i c a l . C o m b i n e d A t t i t u d e D a t a S e r v e r . a t t i t u d e = g a i a . cu3 . i d t f l . i d t . dm . Ioga

# De f i ne d a t a s e r v e r i f DBg a i a . cu1 . t o o l s . d a t a . G e n e r i c D a t a P r o v i d e r = g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e rg a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . username=g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . password =g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . d r i v e r =g a i a . cu1 . t o o l s . d a t a . J d b c S t o r e D a t a P r o v i d e r . db . u r l =

# I f a t t i t u d e i n g b i n s :g a i a . cu1 . t o o l s . d a t a . G e n e r i c D a t a P r o v i d e r = g a i a . cu1 . t o o l s . d a t a . G B i n S t o r e D a t a P r o v i d e rg a i a . cu1 . t o o l s . d a t a . G B i n S t o r e D a t a P r o v i d e r . s t o r e L o c a t i o n =GBIN FOLDER LOCATION

Otherwise, define the configuration scanning law for predicted events to be used by setting thefollowing properties

# De f i ne a t t i t u d eg a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r = g a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . r s l s . S c h e d u l e d A t t i t u d e D a t a S e r v e rg a i a . cu1 . t o o l s . s a t e l l i t e . a t t i t u d e . A t t i t u d e D a t a S e r v e r . l o c a t i o n =XML FILE PATH#Ex : con f / OPS RSLS 0026877 EPSL−F TUNEDfor2014−06−06.xml

The output will be result.csv and .xml files. See Appendix A for more details about XML format.



7 References

[GAIA-LL-061-3], Lindegren, L., Bastian, U., 2009, Local plane coordinates for the detailedanalysis of complex Gaia sources,GAIA-LL-061-3,URL http://www.rssd.esa.int/llink/livelink/open/504573


http://www.rssd.esa.int/llink/livelink/open/504573


A Output format

The goal of this section is to explain the different format and in particular the XML structure aswell as the different elements from a query result either from CLI or from web interface.

Figure 10 displays the result page. It shows an export column which are links to the other outputformat.

FIGURE 10: Result page for one year prediction of m31 object.

As can be seen on the rigth column, it is possible to select the rendered format of the result:HTML, XML, CSV and ICS9.

For example the following is a CSV result for the target m31 in the interval 2014-09-26T00:00:00to 2015-06-26T00:00:00 (see figure 1):Target, ra[rad],dec[rad], Event, Kind, Row, Strip, normalized AC

position, scan anglem31,0.18648476538416492,0.7202809762030912,2014-12-05T00:57:39.842 (TCB),SM

,6,1,-0.6276421161535093,-0.4844573861707808m31,0.18648476538416492,0.7202809762030912,2014-12-05T00:57:50.535 (TCB),AF

,6,3,-0.6273383992362432,-0.4844585910982644m31,0.18648476538416492,0.7202809762030912,2014-12-05T02:44:18.898 (TCB),SM

,6,2,-0.44589399796790286,-0.4851784270291692m31,0.18648476538416492,0.7202809762030912,2014-12-05T02:44:24.737 (TCB),AF

,6,3,-0.4457281779980724,-0.48517908487634576m31,0.18648476538416492,0.7202809762030912,2014-12-05T06:57:54.055 (TCB),SM

,3,1,-0.013731502217305373,-0.4868929083394862m31,0.18648476538416492,0.7202809762030912,2014-12-05T06:58:04.749 (TCB),AF

,3,3,-0.013427761636804135,-0.4868941133398819

9An ICS file is a calendar file saved in a universal calendar format used by several email and calendar programs,including Microsoft Outlook, Google Calendar, and Apple Calendar. It enables users to publish and share calendarinformation on the web and over email.



m31,0.18648476538416492,0.7202809762030912,2014-12-05T08:44:33.121 (TCB),SM,4,2,0.16803059968469394,-0.4876139956795409

m31,0.18648476538416492,0.7202809762030912,2014-12-05T08:44:38.959 (TCB),AF,4,3,0.16819643225533648,-0.4876146535717495

m31,0.18648476538416492,0.7202809762030912,2014-12-05T12:58:08.300 (TCB),SM,1,1,0.6002249439959568,-0.4893286105216469

m31,0.18648476538416492,0.7202809762030912,2014-12-05T12:58:18.993 (TCB),AF,1,3,0.6005287062586148,-0.48932981562725425

m31,0.18648476538416492,0.7202809762030912,2014-12-05T14:44:47.375 (TCB),SM,2,2,0.7819998512052607,-0.4900497637010647

m31,0.18648476538416492,0.7202809762030912,2014-12-05T14:44:53.213 (TCB),AF,2,3,0.7821656952963983,-0.4900504216559468

m31,0.18648476538416492,0.7202809762030912,2015-06-03T13:28:41.084 (TCB),SM,1,2,0.954954104954664,2.6584338168133343

m31,0.18648476538416492,0.7202809762030912,2015-06-03T13:28:46.922 (TCB),AF,1,3,0.954797573496316,2.658433195796311

m31,0.18648476538416492,0.7202809762030912,2015-06-03T17:42:16.274 (TCB),SM,1,1,0.5470200293848196,2.6568154183904786

m31,0.18648476538416492,0.7202809762030912,2015-06-03T17:42:26.968 (TCB),AF,1,3,0.546733331902708,2.6568142809884767

m31,0.18648476538416492,0.7202809762030912,2015-06-03T19:28:55.345 (TCB),SM,3,2,0.3754603326818708,2.6561347998600353

m31,0.18648476538416492,0.7202809762030912,2015-06-03T19:29:01.184 (TCB),AF,3,3,0.37530381167762883,2.65613417890565

m31,0.18648476538416492,0.7202809762030912,2015-06-04T01:29:09.579 (TCB),SM,5,2,-0.2039933548734496,2.6538359861595398

m31,0.18648476538416492,0.7202809762030912,2015-06-04T01:29:15.417 (TCB),AF,5,3,-0.20414986467509819,2.6538353652523226

m31,0.18648476538416492,0.7202809762030912,2015-06-04T05:42:44.730 (TCB),SM,6,1,-0.6118696278932191,2.6522178454990697

m31,0.18648476538416492,0.7202809762030912,2015-06-04T05:42:55.424 (TCB),AF,6,3,-0.6121562837889394,2.6522167082582557

m31,0.18648476538416492,0.7202809762030912,2015-06-04T07:29:23.785 (TCB),SM,7,2,-0.7834041972755587,2.651537318412611

m31,0.18648476538416492,0.7202809762030912,2015-06-04T07:29:29.624 (TCB),AF,7,3,-0.783560695136274,2.6515366975370602

Event times are in TCB. CCD strip type (SM or AF), row number (1-7), strip number (1-11)1 and 2 being SMs and 3 to 11 AFs, across scan normalized position (zeta angle) and the scanangle as defined in GAIA-LL-061-3.

An example of an XML formatted output can be seen in section 4.5

• <creationTime >: the time when the report has been created

• <attitudeDataServerId >: information of the attitude data being used to make theprediction - usually the XML configuration file name used

• <startTime>and <endTime>wich are the time range which covers the report of the



predictions - in this case, 5 years from launch to 20th of June 2014.

• Then a list of <targets><target>, each of them with: <coords>ra dec and an iden-tifier <id>which is generally a running number that make sense if more than onetarget has been asked in the prediction.

• Each <target>will contain a list of events element <event>

• Each of <event>contains:

– <evenDate>: the predicted transit date

– <details>: wrap details such as kind, row, strip numbers.

– <angleToZaxis>: the angle of the target seen in Gaia SRS and Z axis

– <acCcdCoordinate>: the across pixel position (pixel column)

– <normAcTransitPosition>: the across normalized angle transit position

– <scanAngle>: the scanning angle

– <pfovdir>and <ffovdir>are the vector direction of the Preceeding and Fol-lowing FoV in degrees and in ICRS frame

For the ICS format, the file in this output format can directly be used in any iCal reader client.

The HTML format displays the results in a table (see figure 11). As can be seen, the number ofthe displayed results can be selected by the left top button (the default number of values is 10).The information displayed in the table is basically the same information as the one is obtainedin the XML format (see previous paragraph about the rendered XML). At the lower left corner,the image of the object is displayed making use of the 2MASS catalogue at epoch J2000. Boththe catalogue and the epoch can be selected in the drop down menu of the figure. The figure isgenerated by Aladin Lite.



FIGURE 11: Result page for one year prediction of m31 object in HTML format.


gost software user manual - esa · cux gost software user manual gaia-cu1-ug-esac-jfh-005-01 2...

Documents