Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mosaic FOV does not take into account readout mode #28

Open
mgdaily opened this issue May 21, 2024 · 0 comments
Open

Mosaic FOV does not take into account readout mode #28

mgdaily opened this issue May 21, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@mgdaily
Copy link
Contributor

mgdaily commented May 21, 2024

It was reported that:

When setting up a mosaic, I expect that the “Line Overlap Percent” and “Point Overlap Percent” refer to the field-of-view of the selected Readout Mode (Sinistro or QHY600). However, some tests show that the pointings created when I click “Generate Mosaic” are always for the full field-of-view. ---- Is this the correct behavior? I would expect users who want mosaics to use the larger FoVs, but for the QHY600s, the default readout mode is Central 30x30.

This is because the code used to calculate the FOV of the camera uses the full pixels_x, pixels_y instead of a trimmed down version based on the readout mode, as this information is not currently available via ConfigDB to derive an effective FoV for the camera.

Possible solutions include:

  • Adding effective FoV to ConfigDB and plumbing it through to the /api/instruments endpoint in the Observation Portal and using it in the mosaic calculation
@mgdaily mgdaily added the bug Something isn't working label May 21, 2024
@mgdaily mgdaily self-assigned this May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant