fix sign of w0wzCDM inv_efuncs pyx#15049
Conversation
|
Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
|
👋 Thank you for your draft pull request! Do you know that you can use |
|
Failure in https://github.com/astropy/astropy/actions/runs/5502061341/jobs/10026067493?pr=15049 is unrelated. |
is that an issue with the auto-completion? |
|
On reflection, I'm moving the |
|
#15076 seems fine, but for this one I have no idea about the sign ;). |
|
|
||
| >>> cosmo.comoving_distance(0.5) | ||
| <Quantity 1982.66012926 Mpc> | ||
| <Quantity 1849.74726272 Mpc> |
There was a problem hiding this comment.
Is there a way to check those numerical values with another package/software ?
There was a problem hiding this comment.
I can test this with Mathematica.
I'll add some tests.
There was a problem hiding this comment.
Same example is now a test, with the Mathematica code if this ever needs to be rerun.
There was a problem hiding this comment.
@pllim, I've checked the calculation (see screenshot in this thread) and implemented a trivial test. I think this is an uncontroversial merge, if you feel comfortable!
There was a problem hiding this comment.
Can you please rebase then, the CI should be green by now.
edbb4f2 to
8460977
Compare
8460977 to
ac50c42
Compare
ac50c42 to
62dc222
Compare
And update the the internal consistency tests. Signed-off-by: nstarman <nstarman@users.noreply.github.com>
Signed-off-by: nstarman <nstarman@users.noreply.github.com>
62dc222 to
d4626fd
Compare
Signed-off-by: nstarman <nstarman@users.noreply.github.com>
|
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
|
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
|
@nstarman , are you willing to do manual backport for both release branches? 🙏 |
|
I can do that. It would be nice if the backport bot could open Issues if a manual backport is required. It would be a better reminder in my inbox. Can that be configured? |
|
I think that is overkill, the backport bot already applies this label that you can check: Still Needs Manual Backport |
|
@pllim, on v5.0.x this changelog entry is deleted, should I keep it deleted? |
|
Oh maybe because it was rendered into |
…v5.0.x Backport PR #15049 on branch v5.0.x (fix sign of w0wzCDM inv_efuncs pyx)
…v5.3.x Backport PR #15049: fix sign of w0wzCDM inv_efuncs pyx (v5.3.x)
|
Sorry for the long time with response, vacation time ;). |

And update the internal consistency tests.
Fixes #15025
cc @cmarmo