[Isocops] ATS for Orbit# 205 (4 - 13 May 2013)
Nigel Angold
ngangold at earthlink.net
Mon Apr 22 09:17:07 EDT 2013
Can you regenerate with the latest ephem file please.
Thanks,
Nigel
>
> Ken,
> When I was trying to generate an OEF for Orbit 205 I ran into a couple
> errors. I went back to a previous ephem to see if I would get the same
> error. Well I found that the errors were caused by my inputs being off.
> Unfortunately I forgot to change the ephem file back to the DOY 106.
> Tim
>
>
>
>
> From: fair-play at comcast.net
> To: Tim Perry <Perry.Tim at orbital.com>
> Cc: Bret Hautamaki <hautamaki.bret at orbital.com>, IBEX-FDG
> <IBEX.fdg at applieddefense.com>, IBEXOPS/ORB
> <ibexops at orbital.com>, ISOC at New Hampshire
> <isocops at lists.sr.unh.edu>, John Cavallo
> <cavallo.john at orbital.com>, Mark Tapley <mtapley at swri.edu>,
> Nigel Angold <ngangold at earthlink.net>, Robert Lockwood
> <lockwood.robert at orbital.com>, Roland Vanderspek
> <roland at space.mit.edu>, Ryan Tyler <tyler.ryan at orbital.com>,
> Sheral Wesley <wesley.sheral at orbital.com>, Thomas Regiec
> <regiec.thomas at orbital.com>, Tim Perry <perry.tim at orbital.com>,
> Ken Fairchild <fair-play at comcast.net>, Chelle Reno
> <mreno at swri.edu>
> Date: 04/21/2013 08:02 PM
> Subject: Re: [Isocops] ATS for Orbit# 205 (4 - 13 May 2013)
>
>
>
> Tim,
>
> I noticed that the .oef file says that the predictive file
>
> IBEX_Ephem_2013_097_09_29_v002.e
>
> was used to generate it. However, the current predictive file is
>
> IBEX_Ephem_2013_106_08_21_v001.e
>
> Is there a reason why you used the older predictive file?
>
> By the way, I discovered that we are no longer including the predictive
> ephemeris file in the STF header comments. That's because the current 140
> day predictive files end after the current 2 year predictive file. I've
> requested a new 2 year predictive file.
>
> Ken
>
> From: "Tim Perry" <Perry.Tim at orbital.com>
> To: "Bret Hautamaki" <hautamaki.bret at orbital.com>, "IBEX-FDG"
> <IBEX.fdg at applieddefense.com>, "IBEXOPS/ORB" <ibexops at orbital.com>, "ISOC
> at New Hampshire" <isocops at lists.sr.unh.edu>, "John Cavallo"
> <cavallo.john at orbital.com>, "Mark Tapley" <mtapley at swri.edu>, "Nigel
> Angold" <ngangold at earthlink.net>, "Robert Lockwood"
> <lockwood.robert at orbital.com>, "Roland Vanderspek" <roland at space.mit.edu>,
> "Ryan Tyler" <tyler.ryan at orbital.com>, "Sheral Wesley"
> <wesley.sheral at orbital.com>, "Thomas Regiec" <regiec.thomas at orbital.com>,
> "Tim Perry" <perry.tim at orbital.com>
> Sent: Saturday, April 20, 2013 12:22:59 PM
> Subject: [Isocops] ATS for Orbit# 205 (4 - 13 May 2013)
>
>
>
> All,
> I did receive 2 errors. The Second one was an easy one and this is
> covered by the eclipse commands that we added for the medium eclipse. The
> first one took a little bit time to understand. In Orbit 204 there was a
> sun maneuver at Apogee. The maneuver window was from 2013-04-29T21:34:03 -
> 2013-04-29T22:04:05 and the sun maneuver was from 2013-04-29T21:34:03 -
> 2013-04-29T21:49:03. So, in the OEF file for Orbit 204 these times were
> correct. Now, when the new forecast STF file was used to generate the OEF
> file for Orbit 205. The maneuver window had shifted by 1 minute and 31
> seconds. In the Orbit 205 OEF file I found that the sun maneuver begin was
> pulled from the history. But the sun maneuver end was not and I think that
> this was because of where the new maneuver window begin was placed in the
> OEF file. The end time is the last time in the orbit 205 OEF file. MPS
> tried to find the SunMvrEnd and it couldn't. The sun maneuver was
> successful. So, I am comfortable with releasing this command load for
> everyone to approve.
>
> Please respond to this email thread with your comments/approvals. All
> comments/approvals are required before 22 Apr 13 @2100 UTC
>
> ==========================
> HARD CONSTRAINT VIOLATIONS
> ==========================
> NO VIOLATIONS.
>
> ==========================
> SOFT CONSTRAINT VIOLATIONS
> ==========================
> IBX-CLC-001: Sun precession maneuver at 2013/04/29 21:34:03 UTC -
> 2013/05/18
> 09:52:58 UTC (one endpoint unknown) overlaps eclipse at
> 2013/05/04
> 19:45:49 UTC - 2013/05/04 20:52:24 UTC
> IBX-CLC-015: Battery charge falls below minimum from 2013/05/04 20:39:49
> UTC -
> 2013/05/04 21:20:04 UTC. Lowest charge level is 7260.242983
> watt-minutes during this interval.
>
> ==============
> OTHER MESSAGES
> ==============
> NO MESSAGES.
>
> STF files:
> # Filename: IBEX_2013_forecast_04mar13-18jun13_v001.stf
> #Orbit: 204
> # Sun pointing maneuver
> 2013-04-29T21:34:03.000Z|ManeuverWindowStart
> 2013-04-29T22:04:05.000Z|ManeuverWindowEnd
>
> # Filename: IBEX_2013_forecast_01apr13-24jul13_v001.stf
> #Orbit: 204
> # Sun pointing maneuver
> 2013-04-29T21:35:34.000Z|ManeuverWindowStart
> 2013-04-29T22:05:36.000Z|ManeuverWindowEnd
>
> OEF Files:
> # Filename: IBEX_2013_115_o0204a_v001.oef
> 2013-04-29T21:34:03.000Z,ManeuverWindowStart
> 2013-04-29T21:34:03.000Z,SunMvrBegin,
> 2013-04-29T21:49:03.000Z,SunMvrEnd
> 2013-04-29T22:04:05.000Z,ManeuverWindowEnd,orbit:204
>
> # Filename: IBEX_2013_125_o0205a_v001.oef
> 2013-04-29T21:34:03.000Z,SunMvrBegin,
> 2013-04-29T21:35:34.000Z,ManeuverWindowStart,orbit:204
> 2013-04-29T22:05:36.000Z,ManeuverWindowEnd,orbit:204
>
>
>
>
> (See attached file: IBEX_2013_125_o0205a_v001.ccvr)(See attached file:
> IBEX_2013_125_o0205a_v001.oef)(See attached file:
> IBEX_Orbit205Contacts.txt)(See attached file:
> IBEX_2013_125_o0205a_v001.txt)
>
> Timothy E. Perry
> IBEX Mission Ops Lead
> perry.tim at orbital.com
> Office: (703) 406-5976
> Cell:(301) 606-1430
>
>
>
> -----------------------------------------
> Notice: This e-mail is intended solely for use of the individual
> or entity to which it is addressed and may contain information that
> is proprietary, privileged and exempt from disclosure under
> applicable law. If the reader is not the intended recipient or
> agent responsible for delivering the message to the intended
> recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly
> prohibited. This communication may also contain data subject to
> U.S. export laws. If so, that data subject to the International
> Traffic in Arms Regulation cannot be disseminated, distributed or
> copied to foreign nationals, residing in the U.S. or abroad, absent
> the express prior approval of the U.S. Department of State. If
> you have received this communication in error, please notify the
> sender by reply e-mail and destroy the e-mail message and any
> physical copies made of the communication. Thank you.
>
> 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
>
More information about the Isocops
mailing list