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
During a hack day project, in which @eteq and Matteo Correnti were a part of, I was given a non-interactive version of a photometry notebook. My task was to use astrowidgets to make some parts interactive. The non-interactive version leveraged astropy.visualization rather nicely. But I had a hard time trying to do exactly the same steps using astrowidgets with Ginga as a backend because ejeschke/ginga#560 is still unresolved. I have a feeling that other backends we would support in the future (e.g., bqplot or Aladdin Lite) might not use astropy.visualization as well. So, I guess that hook into astropy.visualization might have to happen here in the astrowidgets layer.
Just speaking for myself, I would like this to work in a backend agnostic way, but maybe that is not even possible. Definitely need more looking into. For instance, astropy.visualization.stretch does not rely on Matplotlib, but astropy.visualization.mpl_normalize does.
During a hack day project, in which @eteq and Matteo Correnti were a part of, I was given a non-interactive version of a photometry notebook. My task was to use
astrowidgets
to make some parts interactive. The non-interactive version leveragedastropy.visualization
rather nicely. But I had a hard time trying to do exactly the same steps usingastrowidgets
with Ginga as a backend because ejeschke/ginga#560 is still unresolved. I have a feeling that other backends we would support in the future (e.g.,bqplot
or Aladdin Lite) might not useastropy.visualization
as well. So, I guess that hook intoastropy.visualization
might have to happen here in theastrowidgets
layer.Relevant snippets:
xref spacetelescope/dat_pyinthesky#7
The text was updated successfully, but these errors were encountered: