Support for anisotropic data. #8
Conversation
almarklein
force-pushed
the
world-coords
branch
from
a8b7388 to
b32784a
Compare
almarklein
force-pushed
the
world-coords
branch
from
b32784a to
c41a012
Compare
| slicer1 = DashVolumeSlicer(app, vol1, axis=1, origin=origin, scene_id="myscene") | ||
| slicer2 = DashVolumeSlicer(app, vol1, axis=0, origin=origin, scene_id="myscene") | ||
| slicer3 = DashVolumeSlicer( | ||
| app, vol2, axis=0, origin=origin, spacing=spacing, scene_id="myscene" | ||
| ) |
There was a problem hiding this comment.
@emmanuelle see how we use different data in the 3d slicer, and connect it up by using a common scene_id :)
There was a problem hiding this comment.
I really like this example, haha
|
Thanks @almarklein ! Looks good to me. With this PR I think it's now possible to adapt https://github.com/plotly/dash-sample-apps/blob/master/apps/dash-covid-xray/app.py to use the slicer (the data are indeed anisotropic). Would you like to try it or would you prefer someone else to adapt the app so that you focus on development? As you wish, both are fine. |
|
Yeah, I think adapting that example would be a really nice exercise to see how the API holds up, so I think I'll have a go myself! |
| reverse_y (bool): Whether to reverse the y-axis, so that the origin of | ||
| the slice is in the top-left, rather than bottom-left. Default True. | ||
| (This sets the figure's yaxes ``autorange`` to either "reversed" or True.) |
There was a problem hiding this comment.
Also added this.
rebased
This:
spacingandoriginarguments to specify the position and scale of a volume.slicer_with_1_plus_2_views.pyexample to include one view with downsampled data.reverse_yargument.