Skip to content

Support pdb files #313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arokem opened this issue Jun 6, 2015 · 6 comments
Open

Support pdb files #313

arokem opened this issue Jun 6, 2015 · 6 comments

Comments

@arokem
Copy link
Member

arokem commented Jun 6, 2015

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?

@matthew-brett
Copy link
Member

How niche is the format? Who is using it?

@arokem
Copy link
Member Author

arokem commented Jun 7, 2015

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).

@MarcCote
Copy link
Contributor

I've been really busy lately but once #243 is merged, it would be really easy to add support to it.

@arokem
Copy link
Member Author

arokem commented Jun 16, 2015

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é <
[email protected]> wrote:

I've been really busy lately but once #243
#243 is merged, it would be really
easy to add support to it.


Reply to this email directly or view it on GitHub
#313 (comment).

@MarcCote
Copy link
Contributor

@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).

@arokem arokem mentioned this issue Dec 3, 2015
@effigies
Copy link
Member

Hi @arokem, looks like this hasn't been touched since #391 got merged. Would this still be a useful thing to merge into nibabel?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants