8000 Imagebrowser gives runtime warning after trying to do reduction · Issue #168 · mwcraig/reducer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Imagebrowser gives runtime warning after trying to do reduction #168

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
Open
rohanrajpal opened this issue Mar 17, 2018 · 2 comments
Open

Imagebrowser gives runtime warning after trying to do reduction #168

rohanrajpal opened this issue Mar 17, 2018 · 2 comments

Comments

@rohanrajpal
Copy link

I was trying out the example notebook using the default sample data, sequentially running all the commands.I get a runtime warning with this command

fits_browser = ImageBrowser(images, keys=['imagetyp', 'exposure'])
fits_browser.display()

The warning is

/home/rohan/anaconda3/lib/python3.6/site-packages/astropy/visualization/mpl_normalize.py:117: RuntimeWarning: divide by zero encountered in true_divide
  np.true_divide(values, self.vmax - self.vmin, out=values)
/home/rohan/anaconda3/lib/python3.6/site-packages/astropy/visualization/mpl_normalize.py:117: RuntimeWarning: invalid value encountered in true_divide
  np.true_divide(values, self.vmax - self.vmin, out=values)

This only happens for imagetyp: BIAS .Other imagetyp fit files are shown correctly.
issuebias

This is probably related to Issue #162. The error there is different than I'm getting here but it's on the same command(probably).
Python version:3.6.4
Reducer version:0.4.1
IPython 6.2.1
Jupyter 4.4.0
@jimboH
Copy link
jimboH commented Mar 26, 2018

It seems to be a weird error, but it does not actually affect the image display. Seems like the normalization step on BIAS image type is not working that properly.

@mwcraig
Copy link
Owner
mwcraig commented Mar 26, 2018

If I had to guess, the error is related to the fact that the data set provided with the package has been a little heavily compressed (in the sense of reducing the dynamic range) to make it smaller, so that it may well be that self.vmin and self.vmax are the same values. Thanks for reporting it though, it should get fixed.

50A3

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
3 participants
@mwcraig @rohanrajpal @jimboH
0