Status: In Progress
Fix Version/s: None
Component/s: display_firefly, Documentation, firefly_client, SUIT
In a session with Merlin Fisher-Levine today, and in the course of some pre-flight testing of the new version of the Firefly server deployed on the integration platforms, I've accumulated a list of a number of annoying-to-ridiculous issues with various use cases that lie just outside the way it's normally tested in notebook-demo/Firefly.ipynb.
Some of these are also documentation problems, where the many different places that tutorial/recipe information is presented are not quite consistent (because of non-uniform application of updates in the past) and in some cases don't work with the currently deployed versions.
This ticket will have a number of children covering specific issues. The scope of this ticket is about consistency and usability of the Python interfaces and the launching experience in notebooks, JupyterLab, etc., and about the quality of the associated documentation. "New features" requests or other concerns with the behavior of the Firefly UI once an image is loaded, etc. are out of scope for this ticket. Weird behaviors when re-running a notebook, difficulties opening an external display, baroque magic recipes with hard-coded ports, etc. are examples of what's in scope for a child ticket under this one.
The goal is to get these items cleaned up in time for a May observing run and for DP0.1, so at some point I'll call it closed to more child tickets.
- is parent task of
DM-29656 All documentation on the Python (especially afw.display) interface to Firefly needs a scrub
- To Do
DM-29653 Re-running an afw.display getDisplay() does not re-display the URL for a Firefly display
- In Progress
DM-29654 The "hostname" option to afw.display's getDisplay() fails
DM-29655 afw_display.getClient().display_url() returns the wrong URL for Firefly
Still valid; moved to new epic accordingly.