Closed shaycrk closed 3 years ago
I agree with the points you made here; using the existing 'all' preset is probably the way to go, and sorting the names when we create the matrix metadata. Since we are already doing 830 to break old hashes, might as well do this change as well before tagging a new version.
Ok -- updated to use the all
subsetter by default instead and sorting the feature group names when creating the matrix metadata. I think this should be all set, but we should probably coordinate merging with #830 (and probably #835) as well as bumping the version.
I believe this should fix the bug Evan identified in #832
However, one question before merging: is there any good reason for the default to not simply be:
The
FeatureGroupCreator
already has anall
subsetter that we could take advantage of rather than recreating the logic here. However, if we do that, I wonder if we want to explicitly sort the group names in creating the matrix metadata here -- the main reason I didn't add that as well is because there might be an issue with backwards compatibility changing existing matrix hashses. That might not be a huge deal if we merge/tag at the same time as #830 however.