You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Frequently separations of, e.g., binary stars is given in angles, usually arcseconds or mas. We should add another part of the constructor parsing that allows passing distance as a keyword argument, which will automatically change any angular arguments for a. We could also check if R_planet or R_star are angles and adjust them, but that feels kind of weird- I think people are more likely to use stellar radii in those contexts.
in this case there will have to be some decisions made about defaults. First off, what should the unitless default for distance be? I think parsec is reasonable. Second off, how do we want to autoconvert from angles to distances. For instance, using AU makes sense for arcseconds and parsec, but maybe stellar radii is more appropriate for close planetary systems.
The text was updated successfully, but these errors were encountered:
Frequently separations of, e.g., binary stars is given in angles, usually arcseconds or mas. We should add another part of the constructor parsing that allows passing
distance
as a keyword argument, which will automatically change any angular arguments fora
. We could also check ifR_planet
orR_star
are angles and adjust them, but that feels kind of weird- I think people are more likely to use stellar radii in those contexts.MWE:
current required behavior
desired behavior
in this case there will have to be some decisions made about defaults. First off, what should the unitless default for distance be? I think parsec is reasonable. Second off, how do we want to autoconvert from angles to distances. For instance, using AU makes sense for arcseconds and parsec, but maybe stellar radii is more appropriate for close planetary systems.
The text was updated successfully, but these errors were encountered: