[Isocops] IBEX Orbit# 201 ATS v002
fair-play at comcast.net
fair-play at comcast.net
Sat Mar 16 18:17:15 EDT 2013
Nigel,
According to the header, the per-orbit OEF file used the latest forecast STF as input. I think it should have used last month's forecast STF as input because that is what was used to generate the per-orbit STF.
Ken
----- Original Message -----
From: "Nigel Angold" <ngangold at earthlink.net>
To: "Ibex Mission Operations" <ibexops at gmail.com>
Cc: "Thomas Regiec" <regiec.thomas at orbital.com>, "IBEX-FDG" <IBEX.fdg at applieddefense.com>, "ISOC at New Hampshire" <isocops at lists.sr.unh.edu>, "Bret Hautamaki" <hautamaki.bret at orbital.com>, "John Cavallo" <cavallo.john at orbital.com>, "Tim Perry" <perry.tim at orbital.com>, "Robert Lockwood" <Lockwood.Robert at orbital.com>, "Ryan Tyler" <tyler.ryan at orbital.com>, "Sheral Wesley" <wesley.sheral at orbital.com>, "IBEXOPS/ORB" <IBEXops at orbital.com>
Sent: Saturday, March 16, 2013 2:39:06 PM
Subject: Re: [Isocops] IBEX Orbit# 201 ATS v002
The maneuver pointing values in the FORECAST STF and ATS do not match (they match the OEF). I have not seen this mismatch before. Not huge differences but the Forecast STF and ATS have always matched since I started checking the ATS. Comments, anyone?
Nigel
Compare SetInrDir in ATS with pointing as defined in the Forecast STF & verify the vectors match.
Apogee maneuver: · SetInrDir 0.984316,0.165566,0.060909 $TIME=2013/04:01:18:48:07
· targetX: 0.98429500000000003 |targetY: 0.16568600000000000 |
targetZ: 0.06092700000000000
Perigee maneuver:
· SetInrDir 0.967472,0.235916,0.091328 $TIME=2013/04:06:09:33:23
· targetX: 0.96744900000000000 |targetY: 0.23599999999999999 |
targetZ: 0.09136300000000000
Guys,
Here are the planning files and ATS for Orbit# 201 (28 Mar 13 - 6 Apr 13)
All comments/approvals are required before 18 Mar 13 @ 1200 UTC
The ATS will be uploaded on 19 Mar 13 @1200 UTC
Please note the following items
1. Battery Balancing during PERIGEE
2. Moon in Lo FOV commands at APOGEE
3. Two contacts during this planning period
4. Command Load Constraint Violation Report (CCVR)
==========================
HARD CONSTRAINT VIOLATIONS
==========================
NO VIOLATIONS.
==========================
SOFT CONSTRAINT VIOLATIONS
==========================
NO VIOLATIONS.
==============
OTHER MESSAGES
==============
NO MESSAGES.
--
Sheral R. Wesley
SPVR., Satellite Operations
IBEX Mission OPS
(304) 279-6678 <IBEX_Orbit201Contacts.txt> <IBEX_2013_087_o0201a_v002.oef> <IBEX_2013_087_o0201a_v002.txt> <IBEX_2013_087_o0201a_v002.ccvr>
Please restrict discussions on this email list to non-ITAR sensitive topics.
______________________________________________
Isocops mailing list
Isocops at lists.sr.unh.edu
http://lists.sr.unh.edu/mailman/listinfo/isocops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sr.unh.edu/mailman/private/isocops/attachments/20130316/8dcb17e1/attachment-0001.html
More information about the Isocops
mailing list