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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geodesic Plotting improvements #624
Comments
Hi @JeS24, I'd like to work on this once matplotlib v3.7 gets released. |
@mshumayl Sure. |
Matplotlib just added the first release candidate for If we were to follow Matplotlib's nomenclature, if I understand this right, the equivalent mapping for the aspect parameters between Matplotlib and Plotly are as follows:
|
@mshumayl This looks good. Once |
@mshumayl |
@JeS24 thank you for letting me know! Sure, I'll send in a PR soon. Thanks again for your time. |
馃悶 What bugs you?
(Continued from #610)
#612 added an
aspect
ratio option to*GeodesicPlotter
s that helps avoid skewed plots. However, at the moment, we are usingplotly
's nomenclature for aspect modes for theInteractiveGeodesicPlotter
andmatplotlib
's nomenclature for theStaticGeodesicPlotter
. This is mainly becausematplotlib
is yet to finalize the API for the aspect options (targeted for3.7.0
and also see this).To me, matplotlib's names for the options make more sense than Plotly's. I think, it will be great to offer a unified set of
aspect
options, since the most used API arguments for both the plotting modules (InteractiveGeodesicPlotter
andStaticGeodesicPlotter
) follow the same naming convention. Of course, users can still make changes using thefig
orax
attributes for both the plotters, if they want to.We can also take a look into arguments such as
figsize
, that are also not uniform across these modules.馃幆 Goal
To bring uniformity to the plotting API.
馃挕 Possible solutions
Once matplotlib finalizes the API around aspect and scaling, we can decide on a common set of names and offer them as options for
aspect
across both the modules.matplotlib
'sequal
andplotly
'sdata
are going to the most relevant ones, but others can be useful too. So, the tasks are:figsize
.馃搵 Steps to solve the problem
Refer: https://docs.einsteinpy.org/en/latest/dev_guide.html
Addresses #<put issue number here>
The text was updated successfully, but these errors were encountered: