At the moment the user has to do some pretty non-trivial arithmetic to work out what the corresponding impact parameter axes are when using the *rendergeodesics methods. I propose instead that a new API works like this:
a, b, img = rendergeodesics(...)
where a and b are the $\alpha$ and $\beta$ impact parameters respectively.
fjebaker
commented
1 year ago
At the moment the user has to do some pretty non-trivial arithmetic to work out what the corresponding impact parameter axes are when using the
*rendergeodesicsmethods. I propose instead that a new API works like this:where a and b are the $\alpha$ and $\beta$ impact parameters respectively.