Next: GOCG Post-Observation Products
Previous: Ground Radio Telescope (GRT) Products
Navigation Post-Observation Products
What: The state vectors will be exchanged between navigation groups and are used in comparing the reconstructed orbits.
How: In files named YYMMDD-isas-t.icv and YYMMDD-jpl-t.icv respectively.
When: Files will be exchanged once per week.
Where: The MBC files will be placed in /spectr/ra/oddata/mbcicv/track on the GOCG FTP site. The JPL MMNAV files will be made available on the JPL MMNAV FTP site in directory [RAstron.ODDATA.JPLICV.TRACK] (note the capital letters).
back to top
X-Band Doppler Data
What: X-band Doppler tracking data will be transmitted in near real-time from the DSN GTS to the JPL MMNAV team and from the Pushchino GTS to the ASC navigation team, and post-pass (via FTP) from the GBTS to the JPL MMNAV team.
How: Files will be named YYMMDD-YYMMDD-xxxx-x.odf, where the first YYMMDD is the start date in UTC of the contents of the file, and the second YYMMDD is the stop date in UTC of the contents of the file. Files named YYMMDD-YYMMDD-asc-c.odf will contain C-band range and range-rate data; YYMMDD-YYMMDD-asC-x.odf will contain X-band doppler data from the Pushchino GTS; and YYMMDD-YYMMDD-jpl-x.odf will contain X-band doppler data from the DSN and GBTS GTSs. GBTS files will be named YYMMDDHHMM.dop, where the YYMMDDHHMM correspond to the date and time of the BGN2LK entry in the SRS file. Data transferred between the DSN GTSs and GBTS and JPL MMNAV conforms to the JPL/DSN 'TRK 2-30' format, whereas data transferred between ISAS and JPL MMNAV will be in (the compatible) 'TRK 2-18' format.
When: The GBTS doppler data will typically be available within 2 hours after a tracking pass, or by the next morning (local time).
Where: MBC data will be placed in
spectr/ra/oddata/mbcodf/xdop on the GOCG FTP site.
JPL MMNAV data will be placed on the JPL MMNAV FTP site in [RAstron.ODDATA.JPLODF.XDOP] (note the capital letters) as shown in Mission Element FTP Sites. GBTS files will be available via the GBTS FTP site in the directory /ovlbi/out.
back to top
C/P-Band Range and Range-Rate Data
What: C/P-band range-rate data will be sent from the CS to the MBC navigation team in real-time during the telemetry down-link sessions. The range data will be made available to the JPL MMNAV team.
How: In format TBD, filename extension odf.
When: File will be available TBD days after the telemetry has been received.
Where: Files will be placed in /spectr/ra/oddata/cpdop on the GOCG FTP site.
back to top
JPL MMNAV Reconstructed Orbit
What: The reconstructed orbits will be based on C/P- range and C/P- and X-band range-rate data. The VLBA and Canadian correlators will retrieve the reconstructed orbit from the JPL MMNAV team via the DOTS.
How: The JPL MMNAV team will supply files in SPICE SPK format named YYMMDD-YYMMDD-r.bsp[.v].gz where the first YYMMDD group is the start date and the second YYMMDD group is the stop date (UTC days). The '-r.bsp' indicates a reconstructed binary SPICE format. The '.gz' extension indicates the file is 'gzip'-ed.
When: Each orbit will cover a period of 7 days (to the end of that tracking pass, i.e. no tracking pass will be segmented), and will be made available within 2 weeks of the observation. New files will generally be made available once per week by the end of day Friday (PST).
Where: DSN orbits will be available in pub/RAstron/oddata/rec on the DOTS FTP site.
back to top
ASC Reconstructed Orbit
What: The reconstructed orbits will be based on C- and X-band range and range-rate data. The PC is expected to retrieve the reconstructed from the ASC navigation team.
How: Orbits will be supplied in SCEF format, and provide the state vectors of the satellite every second. File extension is scf.
When: Each orbit will cover a period of TBD days (to the end of that observation where possible!), and be made available within 2 weeks of the observation.
Where: ASC orbits will be available in RadioAstron/oddata/scef on the RSOG FTP site.
back to top
Navigation Status Reports
What: A short summary of navigation activities will be written by the navigation groups. It will include a summary of the quality of the orbit processing and anomalies.
How: Suggested format as given in . Reports are named YYMMDDxxxx.stn, where YYMMDD is the first start date covering the period of the report and xxxx is either 'asc' or 'jpl'.
When: Normally the interval reported in a single file is the 1 week period matching the interval scheduled in the latest SRS file.
Where: E-mailed to RSOG@asc.rssi.ru, and/or placedon the Nav group's FTP site.