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

Add option to automatically determine the overscan axis #263

Merged
merged 1 commit into from
Jan 12, 2016

Conversation

evertrol
Copy link
Contributor

If the overscan axis is explicitly set to None in
subtract_overscan, the overscan direction is determined from the
shape of the overscan section, set the shortest dimension. (In case of
a square overscan, the default of 1 is picked.)

This can be convenient in cases where fits_section is used with an
(unknown) input string (for example, from an image's BIASSEC header
keyword): the user can let the function determine the appropriate
axis.

@evertrol
Copy link
Contributor Author

This PR is incomplete, and largely meant as an issue/RFC, with an example implementation.
Unit tests, docstring update and a CHANGES update are still missing.

@evertrol
Copy link
Contributor Author

I guess the failure of Travis here is directly related to #262 ?

@crawfordsm
Copy link
Member

Yes, the test failure is related to that, which shouldn't effect the rest of your work. If you want to go ahead and add the doc_string update, a test, and something to the change log that would be great. Thanks for the contribution!

If the overscan axis is explicitly set to `None` in
`subtract_overscan`, the overscan direction is determined from the
shape of the overscan section, set the shortest dimension. (In case of
a square overscan, the default of 1 is picked.)

This can be convenient in cases where `fits_section` is used with an
(unknown) input string (for example, from an image's BIASSEC header
keyword): the user can let the function determine the appropriate
axis.
crawfordsm added a commit that referenced this pull request Jan 12, 2016
Add option to automatically determine the overscan axis
@crawfordsm crawfordsm merged commit a85bdb0 into astropy:master Jan 12, 2016
@evertrol evertrol deleted the overscan_axis branch March 2, 2016 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants