Evaluate obliquity as an array of values

[tsalo]

Summary

Obliquity is currently evaluated as a single boolean (np.any(nb.affines.obliquity(img.affine) > 1e-4)). Maybe we could retain the actual obliquity values as a 3-element array? That way obliquity could be clustered like other numeric attributes, once #407 is merged.

[mattcieslak]

I was told we could simplify this even further by looking directly at ImageOrientationPatient that's already in the sidecars. If any of those elements not a 1 or a 0 then we know it's an oblique acquisition. Although I don't know if this covers all cases. For example, I think dcm2niix can de-oblique images and I'm not sure if it updates this field.

We're currently grabbing it from the added field from add-nifti-info.

Are you thinking we could have it set up so there would be acq-VARIANTOblique[XYZ]?

[tsalo]

I was thinking that variant names could include the group or value at some point, so something more like acq-VARIANTOblique3 to indicate it was the 3rd group of oblique values.

[mattcieslak]

So a user would need to look up what Oblique3 means somewhere in a metadata file? At first I was thinking this would be inconvenient, but after some more thinking I'm starting to really like this idea. It applies to the other variants too. Right now the variant names only tell you that the acquisition varies from the dominant acquisition, but not how. There's no info on how it differs, so users will need to look up the actual info somewhere anyways.

[tsalo]

With the fix we pushed in #417, the summary and file TSVs will retain the Cluster_<x> columns, so users shouldn't need to open other files to link a cluster value to the metadata values.

However, some kind of cluster summary file would probably be useful at some point, so that users can see what range of values goes into each cluster. Especially for figures.

[tsalo]

I think this is handled by #403.

[tsalo]

Whoops, I was thinking of #407.

[tsalo]

Per convo in #407, will switch from evaluating the obliquity array directly to having separate ObliqueAxis1, ObliqueAxis2, and ObliqueAxis3 boolean fields.