Get other useful bits from the OR into the proseco ACACatalogTable?

[jeanconn]

I'd be a fan of pushing for the API change on both sides to get the other good bits from the OR and schedule in there:

1. a proper obsid (already discussed) [DONE]
2. observation duration or tstop
3. target offsets (code supports but not being passed by MATLAB) (See Provide target offset to proseco or sparkles sparkles#141) for more details.
   4.presence of monitor window and/or monitor window target coords [DONE]
4. rad zone indicator (LOW PRIORITY)

2 and 3 would help for nailing down attitudes and allowed rolls for aca_preview even if small effect. 4 would be great while we're in there to help with future checks.

[taldcroft]

cc: @jskrist

[taldcroft]

Took this off the 4.4 list, not realistic for this release.

[jeanconn]

Per discussion at the 7-Mar-2019 matlab meeting, we should also pass a parameter to indicate if an observation is in the rad zone (with the thought being that non-radzone-ERs don't need 3 bright stars etc).

[jeanconn]

And would it be possible to pass the allowed roll range?

[jskrist]

I'm knee-deep in infrastructure changes, but I will look into this (likely during the testing phase for the next MATLAB Tools release).