Include variant cluster number/centroid or value in variant renaming recommendations

[tsalo]

Summary

I think it would be informative to include the variant's value in the proposed acquisition value.
For example, if you had two echo time variants: one with EchoTimes ranging from 0 - 20 and one with EchoTime = 40 - 60 (assuming the dominant group was 20 - 40), you would get the following variant names:

• acq-VARIANTEchoTime
• acq-VARIANTEchoTime (same)

It would be great to have the proposed variant names be something like the following:

Using centroid

• acq-VARIANTEchoTime10
• acq-VARIANTEchoTime50

This could be hard with floats though.

Using cluster number

• acq-VARIANTEchoTime1
• acq-VARIANTEchoTime2

Less informative, but still better than the current approach, I think.

Additional details

Next steps

[mattcieslak]

It would be great to get feedback on this. I like the idea of cluster number the most

[tsalo]

I agree that cluster number is the easiest. We might want to create pseudo-cluster numbers for string and array-of-string fields as well, since the different string values might end up being pretty long.

[singlesp]

Cluster number would probably be easier. If not already clearly presented then a consolidated table of cluster number to entity value/ranges would be a nice thing to have as well.