phys2bids
phys2bids copied to clipboard
physiopy
Document similar software
Detailed Description
There is currently a link to tarrlab/physio2bids in the README, but there are a few other tools that I think should be documented and compared to phys2bids explicitly.
Context / Motivation
In https://github.com/nipy/heudiconv/pull/446, they are integrating one such tool (cbinyu/bidsphysio) into heudiconv. This tool serves a different niche (CMRR sequence-stored physio data), but is clearly related in function to phys2bids. It would be nice if all of the relevant tools linked to one another in their documentation, so that users are able to find the appropriate tool for their data easier.
Possible Implementation
Search for other software for converting physio data to BIDS format, and add links in either the README or the docs. Here is a partial list:
- tarrlab/physio2bids: Siemens data
- ostanley/physio2bids: Siemens data (7T-specific?)
- cbinyu/bidsphysio: CMRR sequence data, Siemens data, and BioPac data
- CoAxLab/Cmrr2Bids: CMRR sequence data
- lukassnoek/scanphyslog2bids: Philips data
Plus, if any of these projects go stale, phys2bids devs could contact the creators to see if they'd be cool with merging their code into phys2bids!
Cool @tsalo, thank you for looking around! Do you want to create a documentation page or section?
It doesn't look like there's a good page in the docs for it, and I don't think it's big enough for a page of its own, so I think a section relatively low on the main docs page is the best option.
@tsalo you can also expand this page to contain more sections - not only measurement but also analysis.
In nipy/heudiconv#446, they are integrating one such tool (cbinyu/bidsphysio) into heudiconv. This tool serves a different niche (CMRR sequence-stored physio data),
Clarification: cbinyu/bidsphysio started with CMRR physio data stored in the DICOM files, but now it also handles AcqKnowledge and PMU files. We are working on EyeLink files too, and on automating the BIDS file-naming by using @tsalo's conversion.py module.
Ah yes sorry about that @pvelasco. When I found out that bidsphysio had a larger scope than I originally thought, I updated the list under "Possible Implementation" but forgot to update the paragraph in "Context / Motivation".