User-provided information about how to generate colors based on feature values is stored in a FeatureColorMode class, that can be serialized to YAML, and is managed like the BDV RenderSettings and the TrackSchemeStyle.
The mode editing panel resembles this:
Classic case like coloring a vertex by a vertex feature is supported, but it is also possible to color and edge by a vertex feature and vice-versa:
The editor looks like this on Windows platform:
The color maps are represented by a ColorMap class, that can also be serialized to YAML. There is no editor for these colormaps, however it is possible to drop ImageJ LUT files in the ~/.mastodon/luts folder:
tinevez@lilium:~$ cat .mastodon/luts/Algae.lut
Index Red Green Blue
0 17 36 20
1 17 37 20
2 18 37 21
3 18 38 22
4 18 39 22
...
The coloring is based on the feature projections (scalar, double values) of a feature. The editor panel lets the user pick a pair of feature and projection keys:
Finally, the validity of a color mode depends on the feature to be calculated. It is possible and even common to have a color mode pointing to features that are not registered in the feature model. We want to let the user edits such modes, but we warn them that the related features need to be computed before use in a view:
TrackScheme coloring.
The TrackScheme coloring menu now includes feature-based color modes. The color modes that are invalid (depending on feature that are not yet computed) appear disabled in the menu:
It looks like this on Windows platform:
Here is an example:
Another example for a track feature: all the spots of a track have the same feature values, ergo the same color:
Please review and merge #55 first.
A settings page to edit color modes.
User-provided information about how to generate colors based on feature values is stored in a
FeatureColorMode
class, that can be serialized to YAML, and is managed like the BDVRenderSettings
and theTrackSchemeStyle
.The mode editing panel resembles this:
Classic case like coloring a vertex by a vertex feature is supported, but it is also possible to color and edge by a vertex feature and vice-versa:
The editor looks like this on Windows platform:
The color maps are represented by a
ColorMap
class, that can also be serialized to YAML. There is no editor for these colormaps, however it is possible to drop ImageJ LUT files in the~/.mastodon/luts
folder:The coloring is based on the feature projections (scalar, double values) of a feature. The editor panel lets the user pick a pair of feature and projection keys:
Finally, the validity of a color mode depends on the feature to be calculated. It is possible and even common to have a color mode pointing to features that are not registered in the feature model. We want to let the user edits such modes, but we warn them that the related features need to be computed before use in a view:
TrackScheme coloring.
The TrackScheme coloring menu now includes feature-based color modes. The color modes that are invalid (depending on feature that are not yet computed) appear disabled in the menu:
It looks like this on Windows platform:
Here is an example:
Another example for a track feature: all the spots of a track have the same feature values, ergo the same color: