Open arokem opened 9 years ago
How niche is the format? Who is using it?
I am not sure. It is the native format for the Quench viewer, which I believe is still being used among some of my academic siblings and nephews/nieces. But they're not really using Python :-(
The file format has some neat features. It allows storing not only spatial coordinates, but also associated statistics (e.g. FA along the length of the track, or the mean FA per track).
I've been really busy lately but once #243 is merged, it would be really easy to add support to it.
Sorry to come in late on that one. Is there anything I can do to help that along? I just took a cursory look and have some superficial comments, but maybe I should read through the discussion first.
On Tue, Jun 16, 2015 at 7:40 AM, Marc-Alexandre Côté < notifications@github.com> wrote:
I've been really busy lately but once #243 https://github.com/nipy/nibabel/pull/243 is merged, it would be really easy to add support to it.
— Reply to this email directly or view it on GitHub https://github.com/nipy/nibabel/issues/313#issuecomment-112452829.
@arokem I just need to address MrBago's latest comment, I'll have some time to work on #243 in July. In the meantime, I would appreciate any comments on the design/code/documentation (I know I missing some documentation, though).
Hi @arokem, looks like this hasn't been touched since #391 got merged. Would this still be a useful thing to merge into nibabel?
This is a somewhat niche file-format for streamlines from dMRI tractography. I have an implementation of reading, writing and converting from/to trk files implemented here: https://github.com/vistalab/pdb_files. Would integrating this implementation into nibabel be a desirable thing?