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

DM-36276: Update fgcm to avoid matplotlib 3.6.0 hexbin bug #32

Merged
merged 4 commits into from Sep 19, 2022

Conversation

erykoff
Copy link
Collaborator

@erykoff erykoff commented Sep 19, 2022

No description provided.

Copy link

@laurenam laurenam left a comment

Choose a reason for hiding this comment

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

Comments were (unintentionally) made outside the PR. I tried to capture the relevant discussion here for posterity.

if self.plotPath is not None:
fig.savefig('%s/%s_mjd_deep_expgray.png' % (self.plotPath,
self.outfileBaseWithCycle))
plt.close(fig)

Choose a reason for hiding this comment

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

Might it still be good to have this put.close(fig) trigger regardless (or perhaps move the figure opening into the if deepUse.size > 0: clause)?

plt.close(fig)


if ok.size > 0:

Choose a reason for hiding this comment

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

I wondered:

Is 0 really the best threshold here? I.e. is there a minimum (non-zero) number of points below which a hexbin plot can be useful?

But @erykoff assured me that:

If there's only one point, hexbin plots one ugly point. It's fine, not great, but fine.

@erykoff erykoff merged commit 3dbc634 into lsst-dev Sep 19, 2022
@erykoff erykoff deleted the tickets/DM-36276 branch March 5, 2024 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants