-
Notifications
You must be signed in to change notification settings - Fork 10
Unit test issues #39
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
Unit test issues #39
Conversation
|
Actually sleeping on this, I think a simple modification in astropy's discretize_oversample_1D/2D would solve this problem. They just need to force an |
|
Submitted issue and hopefully a PR over at |
|
The |
|
One set of error is that Fix is to convert: |
|
@AnthonyHorton @danjampro can you do a review on this PR? It is ready to merge. Travis is failing on certain builds, but we'll reconfiguring the test environment when #38 is merged so we can address it over there. |
|
Pausing this effort as it seems #38 works just fine without these changes. This might imply my incorrect usage of outdated |
Bringing a few commits from #38 to here as they are seperate to that PR. @AnthonyHorton I need some input on this one.
First few commits are minor updates I needed to run unit tests in
test_psf.py:I think these are minor, though I needed them to run tests.
The main problem is that
astropy'sdiscretize_oversample_1D/2Dwas recently updated to usenp.linspace, for good reason: astropy/astropy#9293Trouble is that
np.linspacenow requires the argnumto be an integer: https://numpy.org/doc/stable/reference/generated/numpy.linspace.htmlThis wasn't an issue before as
discretize_oversample_1D/2Dusednp.arangewhich accepted different inputs just fine from thegunagala.psffunctions used: https://numpy.org/doc/stable/reference/generated/numpy.arange.html@AnthonyHorton can you suggest a way forward?
My last commit now forces integer
x_rangeandy_range, but I don't think this is the right way to do this.