Aesthetic for Matplotlib and Python Framework for data analysis
Aesthetics
To use only the aesthetics and not the framework simply use create a class instance and call for PlotLikeR().plot_cfg() and/or PlotLikeR().plot_cfg_grid() methods.
In the matplotlib documentation it is possible to find a description of each individual parameter. The majority of which, in the Aesplot library, are set as the default. For more check this link: https://matplotlib.org/stable/tutorials/introductory/customizing.html#the-default-matplotlibrc-file .
Framework
Use a separate python file to create the basic framework structure. Modify the new file or string to make your analysis.
Utils
Fixing the SVG export from matplotlib
When saving the matplotlib figure as SVG, the syntax used doesn’t contain any <text></text>. Instead, matplotlib opts for creating there own letters as mathematical curves. This can be an issue due to the “low resolution” aspect of these curves. To solve this, an utility tool was developed to find and replace the curves for letters.
Additionally, when using LaTex equations in labels and/or legends, some elements can also be converted into HTML syntax.
Converting LaTex to HTML
Some mathematical notation is usually used when plotting graphs such as square root, superscript, index and many others. And, since matplotlib supports LaTex interpretation/compilation, it is useful to have a translation from one markup language to another.
Using utils.SVGText() replaces markups, such as /textbf{}, into an equivalent <tspan></tspan> around the tag. More LaTex markups will be added in the future.
Dependencies
Numpy: https://numpy.org
Matplotlib: https://matplotlib.org
Pandas: https://pandas.pydata.org
Scipy: https://scipy.org
Miktex: https://miktex.org or other latex compiler
To-dos
Expand the latex functions that can be interpreted and translated
Develop tests
Create data examples and plot examples
Metadata
Release files for aesplot 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aesplot-1.1.tar.gz | 15.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aesplot-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.0 kB
Release files / aesplot-1.1.tar.gz
| Download URL | aesplot-1.1.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cce7a2430cdf87768a3579f79aa5d6d9b38ac5764a478a5b91a8c7272a4aa426
|
|
BLAKE2b-256 checksum How to use checksums |
29e8509829f5c09a0487c196c2a108aa0b2e5bf48af9f905e6555481a7e4b2bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Release files / aesplot-1.1-py3-none-any.whl
| Download URL | aesplot-1.1-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
080f722cc19e6777fd75a54334c0b4d14dd2d5ca2025986472d7fcba9057945e
|
|
BLAKE2b-256 checksum How to use checksums |
839c7ba09bd1ac0eeeb37d76aeec6736817e66af63a9fbe47e50bd3f78d1247e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for aesplot 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.