Uh oh!
There was an error while loading. Please reload this page.
First poc - #2
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Really cool! I'll read at least some of the code before our meeting this afternoon. Could you please add a minimal |
emmanuelle
commented
Oct 29, 2020
almarklein
commented
Oct 29, 2020
Will do. Though if you run |
almarklein
commented
Oct 29, 2020
Nope, the current dir is only in PYTHONPATH when running interactively. Anyway, setup.py is added, so you can do e.g. |
Uh oh!
There was an error while loading. Please reload this page.
| zeroline=False, | ||
| ) | ||
| # Add an empty layout image that we can populate from JS. | ||
| fig.add_layout_image( |
There was a problem hiding this comment.
I know we sent you code where the image was added as a layout image but the more "modern" way of doing this is to use an Image trace like in https://github.com/plotly/dash-sample-apps/blob/master/apps/dash-covid-xray/app.py#L68 and https://github.com/plotly/dash-sample-apps/blob/master/apps/dash-covid-xray/app.py#L418. This way you can get hover and click events on image pixels, which is not the case with a layout image
There was a problem hiding this comment.
I saw that the two examples used different methods, and I assumed that layout images where easier, but will change this :) I think I'll do that in a new PR. Are there any other differences? E.g. I saw that with layout images one can create a stack of them and use alpha blending to overlay e.g. segmentation results. Is that possible with image traces as well?
Screenshot of the

slicer_with_3_views.pyexampe: