tomviz icon indicating copy to clipboard operation
tomviz copied to clipboard

Select the active array to visualize in a data set

Open cryos opened this issue 7 years ago • 7 comments

Multidimensional data sets have more than one scalar array, at present Tomviz can only support s single array per data set. I think at a minimum we should support selecting the active data set from a list of available arrays read in from a file. We need to explore lazily loading the active array(s) due to memory constraints, and offering a separate array per module.

If we embrace the use of multiple scalar arrays per data set, we probably want to consider folding label arrays from segmentation into the main data set, and improving the interface to expose multiple arrays. This bug should extend the data panel once #1322 has moved forward to a place where it can be built upon. This is part of the core of supporting multidimensional/multimodal reconstructions (in addition to the RGB support being explored for three channel data sets).

cryos avatar Dec 06 '17 18:12 cryos

#1380 works towards this.

cquammen avatar Jan 10 '18 18:01 cquammen

@cryos Things mentioned on this issue that haven't been implemented:

  • Lazy loading of data arrays
  • Selecting an alternative data array to color by in modules
  • Folding label arrays into transformed data results/child data sets

Should we break those out into separate issues to track them more easily?

cquammen avatar Jan 29 '18 14:01 cquammen

I would say the 2nd and 3rd bullet are highly related, if you change the code to select alternate arrays to color by to look at all in a data source, then will it be easier to drop the support for selecting the alternative array from others? I would focus on 2 and 3 in the short term, if you would rather use this issue as a tracker, and break out a few smaller issues that is fine by me. I know this and a few other issues are on the larger side.

cryos avatar Jan 29 '18 15:01 cryos

The 2nd bullet makes doing the 3rd useful, it's true, but they are orthogonal in terms of implementation.

if you change the code to select alternate arrays to color by to look at all in a data source, then will it be easier to drop the support for selecting the alternative array from others?

I think you may be referring to the Contour module, which lets you color by a child data set which is usually assumed to be a label map produced by a segmentation algorithm. Saving the label map data into the data source would indeed simplify this color choice.

I'll focus on 2 and 3 in the short term.

cquammen avatar Jan 29 '18 15:01 cquammen

@cquammen Did you make any progress on 2 and 3? May be this is something @psavery could take over.

cjh1 avatar Jul 24 '18 15:07 cjh1

This won't make 1.4, we can revisit.

cryos avatar Jul 30 '18 17:07 cryos

@cjh1 The most recent progress was in #1411, but that was based on the old pipeline. It would be better off to start fresh IMHO.

cquammen avatar Jul 30 '18 18:07 cquammen