Marco
@alberttorosyan Speaking out loud, it should be a simple fix that requires changes in a few lines at: https://github.com/plotly/plotly.py/blob/4b5392221bd71d5fa338bfc2144a2fcf3451c177/packages/python/plotly/plotly/matplotlylib/mplexporter/exporter.py#L289-L300 However, Plotly doesn't have a development/contribution guide, I don't know how...
seems like it isn't as straightforward as I thought: ``` plotly.py\packages\python\plotly\plotly\matplotlylib\renderer.py:574: UserWarning: Dang! That path collection is out of this world. I totally don't know what to do with it...
Hi, the zenodo reference is a little bit out of date, is `extinction v0.3.0` the preferred way of referencing this package? https://zenodo.org/record/804967#.Yw4OsXZBwrQ Thanks!
@SiddhantSadangi I have not done anything against this issue :| https://github.com/plotly/plotly.py/issues/3624#issuecomment-1161805210 is probably the best solution at the moment(?).
@rjs3273 Try using create_fits() first. This is a bug that has been bugging me for half a year now. I don't understand why save_fits() doesn't work on its own.
Include stating clearly what is the default HDU number.
Coverage on `dev` has passed the 80% mark in the last commit today.
Update: this doesn't seem to be a problem anymore. Will not close until an appropriate test is written.
In a future release, we may include a "typical" telluric profile that can be used for sub-optimal telluric removal.
should investigate `plotly.tools.mpl_to_plotly` and `mpld3`.