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

Guide reporting #197

Merged
merged 14 commits into from
Dec 23, 2018
Merged

Guide reporting #197

merged 14 commits into from
Dec 23, 2018

Conversation

jeanconn
Copy link
Contributor

No description provided.

@jeanconn jeanconn changed the base branch from master to extent December 17, 2018 01:33
@jeanconn jeanconn changed the base branch from extent to master December 18, 2018 01:52
@taldcroft taldcroft changed the title WIP: Guide reporting Guide reporting Dec 23, 2018
@taldcroft
Copy link
Member

I think this is ready to go. It could still use a plot of the star field and catalog, but that can be added in a separate PR.

@@ -371,7 +371,7 @@ def __init__(self, data=None, **kwargs):
# Make printed table look nicer. This is defined in advance
# and will be applied the first time the table is represented.
self._default_formats = {'p_acq': '.3f'}
for name in ('yang', 'zang', 'row', 'col', 'mag', 'maxmag', 'mag_err', 'color'):
for name in ('yang', 'zang', 'row', 'col', 'mag', 'maxmag', 'mag_err', 'color', 'COLOR1'):
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I want ASPQ1 too

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 15a0138.

# Plot a box showing the 8x8 image boundaries
x = row0 + drow / 2 - 4
y = col0 + dcol / 2 - 4
patch = patches.Rectangle((x, y), 8, 8, edgecolor='y', facecolor='none', lw=1)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was also trying to decide if there was value in trying to plot some indicator of the edge of the useable fov, though that's probably just applicable for the force-included stars that concerned me earlier.


# First plot: star spoilers
ax = fig.add_subplot(1, 2, 1)
plot_spoilers(guide, cand_guides, ax)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though since this just uses the table of the other candidates to get cand_guides.stars, it would make more sense to just pass cand_guides.stars .

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't hurt to have the whole thing and makes the API more consistent. These may end up as methods anyway in the next round of refactor that I'm planning.

@jeanconn
Copy link
Contributor Author

PS I'm working on the validation notebook, so ping me if you end up wanting to work on that.

@@ -23,7 +23,7 @@
# Do reporting for at-most MAX_CAND candidates
MAX_CAND = 50
COLS = ['id', 'stage', 'forced',
'mag', 'mag_err', 'MAG_ACA', 'MAG_ACA_ERR',
'mag', 'mag_err',
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MAG_ACA_ERR is used directly in the spoiler tests. I thought it was somewhat useful to have it here because I found myself looking it up for the cases where it is not presently reasonable (bright candidates). But I suppose if the ids are links to the kadi star lookup that's fine.

@jeanconn
Copy link
Contributor Author

PPS Where are the validation notebooks suppose to live at this point? Not in version control?

@taldcroft
Copy link
Member

Validation notebooks are in /proj/sot/ska/analysis/proseco/www (which is a link). I gave up on version control for these, not seeing the value added (but including the proseco.test(get_version=True) is key).

I'm not planning to work on the guide validation notebook.

@taldcroft
Copy link
Member

On MAG_ACA_ERR, fair enough. Reverted in f09e3a2.

The main thing is that in the meantime we put in this cut on mag_err for color=1.5 stars and will probably want something for bright stars, so MAG_ACA_ERR is really not the right thing. We probably need a mag_aca_err value which is explicitly the "correct" systematic catalog error in addition to mag_err which is the per-readout error. This is for post-release, nothing is changing right now.

@taldcroft
Copy link
Member

And I see this is captured in #192, will update that a bit.

@taldcroft
Copy link
Member

Merging to just get this into master. Further improvements or tweaks are likely.

@taldcroft taldcroft merged commit a7b0690 into master Dec 23, 2018
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.

2 participants