search

sot / starcheck

BSD 3-Clause "New" or "Revised" License
3 stars 0 forks source link

Check for bright stars in perigee catalogs #18

Closed jeanconn closed 11 years ago

jeanconn commented 12 years ago

Add warning on perigee catalog unless catalog has 3 9th mag or brighter stars.

jeanconn commented 12 years ago

Should this be a red or green warning?

taldcroft commented 12 years ago

I would say red since not meeting this requirement could result in a safing action, and we are likely to fail a load that has this warning. As always there are grey areas where a catalog squeak through.

On Tue, Sep 4, 2012 at 10:17 AM, jeanconn notifications@github.com wrote:

Should this be a red or green warning?

— Reply to this email directly or view it on GitHubhttps://github.com/sot/starcheck/issues/18#issuecomment-8264399.

jeanconn commented 12 years ago

Going into perigee it looks like it is not uncommon to disable radmon before the beginning of the maneuver to the first ER. Do we still want to warn on these? or only if the OR has N seconds or more in perigee or X fraction? In debugging I've got info statements like this

>> INFO   : Perigee overlap: obs stop at 2004:210:20:37:07.000 radmon disa at 2004:210:20:31:57.000
taldcroft commented 12 years ago

On Tue, Sep 4, 2012 at 12:14 PM, jeanconn notifications@github.com wrote:

Going into perigee it looks like it is not uncommon to disable radmon before the beginning of the maneuver to the first ER. Do we still want to warn on these? or only if the OR has N seconds or more in perigee or X fraction? In debugging I've got info statements like this

INFO : Perigee overlap: obs stop at 2004:210:20:37:07.000 radmon disa at 2004:210:20:31:57.000

We won't take action on this, and the guideline is specific to ERs in perigee. So no warning or informational message is needed.

jeanconn commented 11 years ago

Handled in #36