[Isocops] IBEX Orbit# 184 ATS's for postverif_asc and desc_apo and arc b
Mark Tapley
mtapley at swri.edu
Fri Oct 12 16:22:16 EDT 2012
All,
I have looked at the Orbit 184 post-LUT-load ATS's
IBEX_2012_298_o0184a_desc_apo_v001.txt
and
IBEX_2012_298_o0184a_postverif_asc_v001.txt
and
IBEX_2012_298_o0184b_v001.txt
I don't understand or approve of the middle one yet. I
approve the first (...desc_apo...) and last (...184b...).
No constraint violations per .ccvr files:
IBEX_2012_298_o0184a_desc_apo_v001.ccvr
IBEX_2012_298_o0184b_v001.ccvr
On the other hand, .ccvr file:
IBEX_2012_298_o0184a_postverif_asc_v001.ccvr
correctly complains that we put the PL into HV operation and
then execute a thruster maneuver.
It would make sense to load ...desc_apo... alone if the PL
will be left in HV science operations after the LUT upload.
I can't see any circumstance in which it would make sense to
load ...postverif_asc... as is; if the descending commands are not
already up and we lose communication after loading it, the PL runs HV
straight into the thruster maneuver, whereas if the descending
commands in ...desc_apo... are already loaded, ...postviref_asc...
duplicates most (but not all) of the SC commands. The latter file
(...postverif...) also lacks this command:
@FCT_SetScState housekeeping $TIME=2012/10:28:21:24:21
which is present in the former file (...desc_apo...)
I recommend a new version of ...postverif_asc... with no SC
commands in it; operations would then do the LUT load, load and
confirm ...desc_apo..., then load ...postverif_asc_v002..... during
the 0130-0300 pass and confirm correct execution during the 0400-0500
pass on the 26th.
All PL ascending and descending operations in both files make
sense with respect to each other and to 15 Re ascending and Apogee
times from
IBEX_2012_298_o0184a_v001.oef
and with respect to the contact times from
IBEX_Orbit184Contacts_v001.txt
with the two LUT Upload contacts straddling the macro times
in ...postverif_asc... and -Lo ramp-up completing during the 2nd
pass.
Star tracker outage during ascending macros should not affect
HV operations, but may affect quality of science data until the star
tracker comes back online.
No Moon in -LO FOV.
No ground station contact commands in any load, to save command space.
All inertial maneuvers match those in
IBEX_2012_298_o0184a_v001.txt
which was already approved yesterday, (although the comment
mis-labels the apogee maneuver PERIGEE:).
No -Lo O-mode Commands.
No overlap to orbit 183 commands apparent by manual check;
http://ibex.unh.edu/cgi-bin/ats.cgi has a lot of commands interleaved
among various loads and is not usable for confirming no-overlap right
now.
At 13:51 -0400 10/11/12, Ibex Mission Operations wrote:
>Guys,
> Here are the planning and ATS files for Orbit# 184.
>Orbit# 184 will also include the LUT Upload.
>The ATS files have not been placed on the SFTP server so that Ken
>can check them individually.
--
- Mark 210-379-4635
-----------------------------------------------------------------------
Large Asteroids headed toward planets
inhabited by beings that don't have
technology adequate to stop them:
Think of it as Evolution in Fast-Forward.
More information about the Isocops
mailing list