-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create code that plots star positions on fov maps/ Polaris Investigation #14
Comments
Alright, this is what you get applying UTC time corrections to the obsalt and obsaz nsb input parameters: It seems to be a bit closer to reality, there's one really bright source close to the centre of the field (which I'm sure is Polaris). So my questions now are: Is this close enough to reality for us to tolerate for practical purposes? Albeit other sources like issues #13 and #14 might rotate in the field more. If not, does anyone have any ideas for what other parameters to change (the set of parameters at the top of savefield.py , fromfits.py and in mypycat.txt on this repo are the versions used for this run)? The only one I can think of is perhaps the various epochs in the ICRS transformations, but that should be a really small I'm also advocating that we keep to mag 15 as the lower gaia limit from now on. It's worth spending an extra hour every run if it avoids weird smearing out of the bright stars on healpix maps that we see with the mag 8 variants (I think this is a bug in nsb). |
At the minute the positions of bright stars are only plotted in the camera images. Write code to put them in the sky fov maps.
Run low mag limit polaris field with reduced fov, but same healpix density as a check, both with and without the bright stars library correction applied.
Write simple star location code that takes the fits file and a WCS entry and plots positions of stars in the fov map.
The text was updated successfully, but these errors were encountered: