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

Create code that plots star positions on fov maps/ Polaris Investigation #14

Open
2 tasks done
STSpencer opened this issue May 4, 2021 · 2 comments
Open
2 tasks done

Comments

@STSpencer
Copy link
Collaborator

STSpencer commented May 4, 2021

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.

@STSpencer STSpencer changed the title Create code that plots star positions on fov maps Create code that plots star positions on fov maps/ Polaris Investigation May 5, 2021
@STSpencer
Copy link
Collaborator Author

I've done a run on Polaris with min gaia magnitude turned down to 8 from 15, but with healpix level still set to 11. This saves a bit more compute time than I thought (~-1.5 hours) but causes some weird effects in the fov maps that I'm not entirely sure of the origin of:

image

The highlighted star positions are still a bit off, but there's clearly a very bright source very near the centre of the images so Polaris is definitely being taken into account, so that's good:

image

and that star is definitely polaris (1Alp UMi ) according to astropy:
image

I'd been assuming the UTC timezone correction needed to be applied to the final star tracking part of the code (in fromfits.py), but now I'm not so sure (I think it might need to be taken into account in the obsalt and obsaz variables passed to NSB during the fits file generation). I'm going to give that a try now.

@STSpencer
Copy link
Collaborator Author

Alright, this is what you get applying UTC time corrections to the obsalt and obsaz nsb input parameters:
image

image

image

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 (<arcsec)effect.

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).

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

No branches or pull requests

1 participant