Skip to content
This repository has been archived by the owner on Nov 21, 2023. It is now read-only.

Autoreduce: Dis-high data in blue #36

Closed
tdwilkinson opened this issue May 18, 2015 · 5 comments
Closed

Autoreduce: Dis-high data in blue #36

tdwilkinson opened this issue May 18, 2015 · 5 comments

Comments

@tdwilkinson
Copy link
Contributor

First, thanks to your last changes, this a sample of great DIS-high data reduction (in red):
kic5597604 16r

It was so quick ! So, I decided to try it with the blue images. The results were... interesting. I ran the pydis.autoreduce the first time with the red henear by accident:
kic2285598 11b_r

The results were off, and I found the error in my code. This is what I got with the blue henear:
hmmm 15b
It seems we have discovered plasma dragons.

I'm not sure why the blue images would reduce differently than the red. I looked in pydis.py and could not find anything. On my side, I double checked my lists, and all seem to be the same. The next DIS-high night I ran with pydis.autoreduce also looked good in the red, and the same distortions appeared in the blue.

@jradavenport
Copy link
Member

this wacky result is when the HeNeAr gets solved poorly. Consider: you're fitting a polynomial to describe wavelength versus pixel number. That polynomial could turn over and start going back down again, which would cause the spectrum to "double over" on itself.

Be sure to do the Blue HeNeAr with care! And be careful when fitting to polynomial!

@jradavenport
Copy link
Member

Are you doing the HeNeAr manually for both the red/blue?

@tdwilkinson
Copy link
Contributor Author

Okay, that makes sense. I was using interact=False, so I was expecting to rerun these to get more robust results anyway.

@tdwilkinson
Copy link
Contributor Author

Whoa. :)
I was just running the quick autorun script to get through all of the nights of data. Then, I am going to run the red side manually from there.

@jradavenport
Copy link
Member

It's an interesting bug, i'll create a new issue for it. Not entirely clear to me at the moment how to solve it, but we should impose the condition that wavelength must monotonically change and not turn over!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants