110 likes | 171 Views
“DDSinterface”. a software interface between Consert EGSE and Rosetta Data Delivery System (DDS). DDSinterface : overview. software developed for ground operations aims to extract data from the Rosetta Mission Control System (MCS)
E N D
“DDSinterface” a software interface between Consert EGSE and Rosetta Data Delivery System (DDS)
DDSinterface : overview • software developed for ground operations • aims to extract data from the Rosetta Mission Control System (MCS) • interacts with the DDS (Data Delivery System) (documentation=DDID) • main features • behaves in a “realtime” manner • extracts and download telemetry data (APID) on the Consert EGSE • handles several APID in parallel • merges retrieved data within a single file • takes into account temporary unavailability of data • DDSinterface = Java application executed on the EGSE
Spacecraft datafile DDS : an overview Consert EGSE Rosetta MCS (ESOC) data analysis software(CDH ) D D S DDSinterface IP network
DDS : how to make requests requests Request file (XML) FTPtransfer DDS FTP server DDS Main PI EGSE (PC) Data PI FTP server Data file (SFDU or raw data) FTPtransfer Monitoring Processing Archiving …
DDSinterface : the request loop 1 software thread / apid generate request DDS Request file (XML) “near” realtime Request # n from Tn-1 to Tn Request # n+1 from Tn to Tnow wait wait PI EGSE (PC) concatenate data Data file disk storage TM File
DDSinterface : the request loop (failure) 1 software thread per APID generate request DDS Request file (XML) timeout “near” realtime Request # n from Tn-1 to Tn Request # n+1 from Tn-1 to Tnow wait wait PI EGSE (PC) concatenate data Data file disk storage • Failure types : • DDS down (timeout) • Corrupted data file • Empty file
generate request Request file (XML) “near” realtime Request # n from Tn-1 to Tn Request # n+1 from Tn to Tnow wait wait concatenate data Data file TM File DDSinterface : user parameters • APID number • “back time” for first request • realtime offset - offset
DDSinterface : future evolutions or improvements • no clear choice (yet) between SFDU data or raw data • “standalone executable” to be built (JAR file) • should use the XML acknowledgment returned by the DDS • take care of evolutions (?) in the DDS system : • behavior change may involve modifications in DDSinterface • take care of evolutions in software technology (especially Java) and future compatibility issues • take care to maintain a FTP service at the PI’s home institute, with correct configuration. Similar FTP service may become mandatory on the EGSE.