[INSTRM-345] Support "online" and "offline" OCSes. Created: 01/May/18  Updated: 09/Nov/18  Resolved: 09/Nov/18

Status: Done
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-379 Invert nesting of OCS/MHS parts of ic... Open

 Description   

PFS will want to be able to run (take exposures) anytime, whether allocated or not, whether on the telescope or not.

Discussions yielded:

  • PFS will have an "online" and an "offline" OCS. The online one is the real operational Subaru copy, the offline one is something which PFS will run, can connect to, and will let us never worry about interfering with observations by other instruments.
  • Subaru will come up with a single frame counter accessible to both.
  • PFS will come up with a way to seamlessly and quickly switch between the two. "gen2 online"/"gen2 offline" is the way I think of it.
  • The offline OCS should be clever about headers: what to provide, what to declare, what to lie about.

This ticket should simply defer to at least two others: for the Subaru OCS work and for the PFS ics_gen2Actor work.

 Comments   
Comment by cloomis [ 09/Nov/18 ]

The visit/frame number function has been tested: both observatory servers use the same database table.

INSTRM-462 deals with switching between servers, and/or INSTRM-379.

Generated at Sat Feb 10 16:24:02 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.