Question from @jyeatman on the call just now: Can we plug this into AFQ-Browser, so that if the data is available, this becomes the viewer inside of AFQ-Browser. The user would have to additionally specify where to get the anatomical + trk data from for this.
My hunch is that the way forward for that is to add a niivue viewer into AFQ-Browser. I think that many of the features that will be implemented here (e.g., colors, see #5) will feed directly into that. I think that we can continue developing things here for now, and then eventually work on this when things are hashed out here.
Question from @jyeatman on the call just now: Can we plug this into AFQ-Browser, so that if the data is available, this becomes the viewer inside of AFQ-Browser. The user would have to additionally specify where to get the anatomical + trk data from for this.
My hunch is that the way forward for that is to add a niivue viewer into AFQ-Browser. I think that many of the features that will be implemented here (e.g., colors, see #5) will feed directly into that. I think that we can continue developing things here for now, and then eventually work on this when things are hashed out here.