Miriade

https://ssp.imcce.fr/webservices/miriade/api/ephemsys.php?[parameters]

1. The ephemerides are available for a handful of asteroidal systems. Use the dedicated interface to retrieve the list of systems.
2. By default, the ephemerides are provided for 4 dates, spanned around the requested epoch as t₀-1h, t₀, t₀+1h, and t₀+2h.
3. Use the gensol keyword of the dedicated interface to know exactly the time span of computation of errors of the orbital solution. Outside this period, ephemerides can be computed without estimation of position errors.
4. The number and Ids of available solutions for a given asteroidal system can be retrieved using the dedicated interface.

The output results are described in the following section, and are available in VOTable (cf. examples). The only mandatory parameter is the name of the system. The other parameters are optionnal and their values can be omitted (just left blank the value, e.g. &-tscale=&-mime=).

• the list of asteroidal systems for which ephemerides can be computed,
• the list of orbital solutions available for a given asteroidal system.

https://ssp.imcce.fr/webservices/miriade/api/ephemsys.php?-get=<keyword>[&parameters]

The output response is a text/csv document which contains the following information:

Web Service URI:

https://ssp.imcce.fr/webservices/miriade/miriade.php

Namespace:

https://ssp.imcce.fr/webservices/miriade

WSDL:

https://ssp.imcce.fr/webservices/miriade/miriade.php?wsdl

SOAP header:

name of the SOAP header element: clientID

SOAP header's content: array('from' => 'YourName', 'hostip'=>'')

Method:

ephemsys (inputArray)

1. The ephemerides are available for a handful of asteroidal systems. Use the dedicated interface to retrieve the list of systems.
2. By default, the ephemerides are provided for 4 dates, spanned around the requested epoch: t₀-1^h, t₀, t₀+^h, and t₀+2^h.
3. Use the gensol keyword of the dedicated interface to know exactly the time span of computation of errors of the orbital solution. Outside this period, ephemerides can be computed without estimation of position errors.
4. The number and Ids of available solutions for a given asteroidal system can be retrieved using the dedicated interface.

The output of the ephemsys method is an object containing the following attributes:

'flag'

the status of the response: flag=1 means ok; flag=0 or flag=-1 mean that an error occured

'status'

the HTTP status-code of the response (e.g. 400: bad request, 422: Unprocessable Entity, 500: internal error)

'ticket'

the Unix timestamp of the response which can be useful to stamp the request

'result'

a string, formatted in the IVOA standard VOTable format, containing the ephemerides of the requested asteroidal system (see Output results section)

• name=Kalliope and gensol=1
• name=Kalliope and gensol=2
• name=Camilla and default gensol

The VOTable output consists of a collection of resources that contain tables with the ephemerides of each component of the given asteroidal system (Fig 1). Each resource corresponds to a set of orbital elements for each component of the system obtained by fitting the observations with the Genoide algorithm (Vachier et al. 2012, A&A 543). The number of resources within the VOTable is given by the parameter nbgensol, and each resource is identified by an attribute ID="gensol_i" where i is an index from 1 to nbgensol. Within a resource, the number of tables is given by the parameter nbcomposyst_i, and each table is identified by an attribute ID="<NameOfComponent>_i".

The VOTable contains a set of parameters that describe the overall data:

• VOTABLE/PARAM/Coordinates: the type of coordinates: relative to the center of mass of the system
• VOTABLE/PARAM/TimeScale: the time scale of the ephemerides TT or UTC
• VOTABLE/PARAM/RequestedEpoch: the requested epoch
• VOTABLE/PARAM/NbDates: the number of date of ephemerides (4), provided also by the nrows attribute of the tables
• VOTABLE/PARAM/StepSize: the step size of the ephemerides (1 h)
• VOTABLE/PARAM/NbGenSol: the number of Genoide's solutions

• VOTABLE/RESOURCE/PARAM/GenoideSystem: the name of the asteroidal system
• VOTABLE/RESOURCE/PARAM/GenoideSolutionDate: the date of computation of the solution
• VOTABLE/RESOURCE/PARAM/GenoideSolutionId : the Id of the Genoide's solution
• VOTABLE/RESOURCE/PARAM/NbCompoSyst: the number of components of the system
• VOTABLE/RESOURCE/PARAM/GenoideFomc: the quadratic mean of the O-C
• VOTABLE/RESOURCE/PARAM/GenoideProba: the probability of success of the solution

• VOTABLE/RESOURCE/TABLE/PARAM/Radius: the mean equatorial radius of the component
• VOTABLE/RESOURCE/TABLE/PARAM/Radius_err: the error on the mean equatorial radius of the component

For each component of a system, the ephemeris table contains the fields described in the following table. The uncertainties on the cartesian coordinates of the components (columns 4 to 15) are defined as the minimum and maximum errors at 1-sigma, 2-sigma, and 3-sigma levels (Fig. 2).

$> curl "<URL>"

$> wget "<URL>"

In order to help you to invoke the Miriade Web service, we provide some clients written in differents languages. Here are some detailed explanations to write a client with PHP and SOAP which invokes the ephemsys method:

1/ Provide the input parameters which are mandatory for the service:

// Client's ID: provide the name of your project or organisation or yourself
$from = 'MyName';
// Input parameters
$param = array('name' => 'a:camilla',
               'epoch' => '2018-03-19T0:42:46.0',
               'tscale' => 'TT',
               'gensol' => 0,
               'mime' => 'votable'
);

2/ Define the SOAP options, the namespace and the WSDL URI of Miriade Web service:

// Enables or disables the WSDL caching feature
ini_set('soap.wsdl_cache_enabled', 1);
// Miriade namespace
$namespace = 'https://ssp.imcce.fr/webservices/miriade';
// Miriade WSDL
$uriwsdl = $namespace.'/miriade.wsdl';

3/ Create a SoapClient object in WSDL mode, set the SOAP header, then call the method and catch exceptions:

try {
  // Constructs the client
  $client = new SoapClient($uriwsdl, array('exceptions'=>1));
  // SOAP header
  $header = array('from'=>$from, 'hostip'=>'', 'lang'=>'en');
  $client->__setSoapHeaders(array(new SOAPHeader($namespace, 'clientID', $header)));  
  // Call the resolver method
  $response = $client->__soapCall('ephemsys',array($param));
  // Display the results
  if (! empty($param['get'])) {

    // Display get results
    header("HTTP/1.0 ".$response->status);
    if ($response->status < 300) {
      header("Content-Type: text/csv");
    } else {
      header("Content-Type: text/xml;content=x-votable");
    }
    echo $response->result.PHP_EOL;

  } else {

    // Display ephemerides
    header("HTTP/1.0 ".$response->status);
    header("Content-Type: text/xml;content=x-votable");
    echo $response->result;

   }
} 
catch (SoapFault $fault) 
{
   trigger_error("SOAP Fault: {$fault->getTraceAsString()} (faultcode: {$fault->faultcode}, 
                               faultstring: {$fault->faultstring})", E_USER_ERROR);
}