Is your feature request related to a problem? Please describe.
The newly added Heatmap.plot_subplot() could have a better public facing API. Right now a separate scene is created for each subplot, this can cause a segmentation fault if the reference to each scene isn't kept between the plot_subplot() call and the call to plt.show().
Describe the solution you'd like
We could allow a scene to be initialised with more than one slicing location. The plot() function would then either provide a single plot if only one slicing location is provided or a plot with multiple subplots if multiple positions were passed during initialisation.
This would generate a single plot at position 8000:
This is just one idea, the position argument already has a few meaning depending on the dimensionality of the visualisation and the specific type passed (tuple vs ndarray).
Is your feature request related to a problem? Please describe. The newly added
Heatmap.plot_subplot()
could have a better public facing API. Right now a separate scene is created for each subplot, this can cause a segmentation fault if the reference to each scene isn't kept between theplot_subplot()
call and the call toplt.show()
.Describe the solution you'd like We could allow a scene to be initialised with more than one slicing location. The
plot()
function would then either provide a single plot if only one slicing location is provided or a plot with multiple subplots if multiple positions were passed during initialisation.This would generate a single plot at position 8000:
This would generate a plot with 6 subplots:
This is just one idea, the position argument already has a few meaning depending on the dimensionality of the visualisation and the specific type passed (tuple vs ndarray).
See discussion in #44.