Next: Navigation Pre-Observation Products
Previous: RSOG Pre-Observation Products

• SRT (Space Radio Telescope) Schedule (SRS) File
• Constraints for Long-Term Experiment Schedule
• Control Session File
• Telemetry Prognosis File

SRT (Space Radio Telescope) Schedule (SRS) File

• GOCG to Tracking Stations

What: GOCG generates the Space Radio Telescope (SRT) schedule file, or SRS file, from current GSTS file. The SRS file has more precise time stamps than long-term schedules, and also designates which GTS will be used when. It incorporates also all auxiliary operations with the SC service systems like unloading gyroscopes and P/C-band orbit measurements. A one-second precision is used for GTS activities, though the accuracy is dependent on the orbit used.The SRS file will contain a list of activities describing the tracking support for one week of the mission from Monday through Sunday UTC, continuing to the end of any tracking pass that starts before the end of Sunday UTC. The SRS file also serves as the antenna pointing schedule file, as it describes the planned orientation of the spacecraft (and solar panels) as a function of time. The JPL MMNAV team will take detailed solar-pressure effects into consideration in generating the orbit predictions.

How: The file format is described in "SVLBI Space Radio Telescope Schedule File". The files are named YYMMDD.srs[.v], where the date corresponds to the Monday of the week for which the file is valid.

When: SRS files are generated each week for the following weeks - it is envisaged that each week SRS files will be generated for the following 4 weeks. The schedule for the following week is, unless some contingency arises (see Contingency Plans), the final version; the schedule for 4 weeks in advance is preliminary, but allows mission elements to determine their staffing requirements, etc. The SRS files will be made available by Tuesday at 1900 UTC.

Where: The files are placed in the sub-directory spectr/ra/schedule/srtsched on the GOCG FTP site (see Mission Element Points-of-Contact).

back to top

Constraints for Long-Term Experiment Schedule

• GOCG to RSOG

What: There are numerous constraints for SC operations which must be considered in scheduling of science observations. These constraints may change during SC life time. New parameters of the constraints can be valid for the limited time period (temporary constraints), or they can be valid from definite starting time to the end of the mission (permanent constraints). RSOG will use constraints file to edit availability file for SRT.

How: The file format will be described in the separate document "Space Radio Telescope Constraints File". The files are named YYMMDD.cns, where the date corresponds to the time when the constraints start to be valid.

When: Costraints files are generated when any new changes to constraints will be found by GOCG.

Where: The files are placed in the sub-directory spectr/ra/status/constraint on the GOCG FTP site (see Mission Element Points-of-Contact).

back to top

Control Session File

• GOCG to CS

What: Using SRS files scientific team of GOCG generates programm for every communication session with the SC. The programm describes the sequence of standard assignments wich will be performed with the science and service equipments on-board of the SC. The standard assignment consist of the set of commands with their parameters. There are two types of command files: files containing commands of direct action which will be performed during the uplink communication session, and files containing commands which will be loaded to the on-board memory of Temporal Commanding Device (TCD) for future automated performance. The first type of files are named naxxxbx.mci or nvcxxxbx.mci, where n - science information file's number , a/c - any letter, xxx - the uplink communication session's number, b - version's number, v - time tag to establish relation between this command file and command file for automated performance. The second type of command files are named @SRxxxbx.pvs (dispatcher program), and SRxxxBx.mrk (program of accompanied TM).

How: The TCD team of GOCG translates programs indicated above into binary code (Control Session File). Resulting code is tested with TCD model to simulate SC behaviour. CSF file is named SRSxxxBx.spr, where SR is abbrivation for the SC name, S is uplink session, xxx - session's number, x - session's version. The file format will be described in the document "SRT Control Session File".

When: Control Session Files are generated 24 hours in advance to corresponding uplink session.

Where: The files are placed in the sub-directory spectr/ra/schedule/short/ on the GOCG FTP site (see Mission Element Points-of-Contact).

back to top

Telemetry Prognosis File

• GOCG (internal usage)

What: GOCG generates TPF-file which contains expected time variations for selected set of TM-parameters.

How: The TPF-file will be generated from the SRS-file. The file format will be described in the separate document "Telemetry Prognosis File".

When: The TPF-file will be generated 24 hours in advance to the uplink communication session.

Where: The files are placed in the sub-directory spectr/ra/schedule/short on the GOCG FTP site (see Mission Element Points-of-Contact).