Giters

gemini-hlsw / ocs

Observatory Control Software

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Asterism Configuration

swalker2m opened this issue · comments

commented

The SingleTarget and GhostStandardRes asterisms have no additional configuration beyond the targets themselves but the GhostHighRes asterism does have a few settings. It isn't clear which if any of these are needed for June. Going by the Asterism model, it would include these values:

asterismconfig

but maybe all we need for now is to be able to pick standard vs. high resolution?

commented

Ahhh... never mind: sorry, I was confused in my previous comment between the Asterism configuration and the Asterism target configurations.

Couldn't we include this information in the GHOST tab if we go that route?

Or what about including these in the GHOST editor? I know they are tied to the target environment editor, but it seems like they would seldom be changed once set. We could even just adjust the text at the top of the Target Environment table to indicate what the settings are. Indeed, perhaps there are already cases where we should be doing this? (GPI?)
screen shot 2018-03-13 at 10 51 31 am

commented

Couldn't we include this information in the GHOST tab if we go that route?

Keep in mind this is asterism configuration as a whole. Each GHOST target has it's own bit of configuration, which I think is what you're referring to by the "GHOST tab".

Or what about including these in the GHOST editor?

The drawer is probably the easiest to implement option, if that's a concern. Putting it in the instrument editor is also a possibility but ideally we should keep it with the target component since it changes several things about the UI there.

commented

Again, as UI work, and related to 1438, I'm guessing 2-3 days?

commented

This will be configured in the instrument editor as per our discussion this morning, so I'll include estimates in 1437.

commented

I believe this task is not needed for June. We will support the radio button selection between modes. Any additional configuration will be left to the future.

commented

As said, this has been partially implemented in the instrument component for resolution modes. Any further configuration is something we will have to rework into the UI n the future.