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.

Sign up for GitHub

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

Jump to bottom

Determine input parameter validity ranges for distortion transformations #68

Open
Johannes-Sahlmann opened this issue Oct 22, 2018 · 2 comments
Open

Determine input parameter validity ranges for distortion transformations #68

Johannes-Sahlmann opened this issue Oct 22, 2018 · 2 comments

Comments

@Johannes-Sahlmann
Copy link
Collaborator

No description provided.

@ColinRCox
Copy link
Collaborator

Would this not be studied by whoever delivers the distortion solution? I assume the valid range covers the associated detector but probably not far beyond that. We should ask for this information.

@Johannes-Sahlmann
Copy link
Collaborator Author

Currently, there is no information about the validity range and a user is not warned when it is exceeded. I agree this should be the responsibility of the delivering entity to define the value.
The JWST pipeline handles this via setting the bounding_box associated with a transformation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Johannes-Sahlmann @ColinRCox