Skip to content
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

Passing over the bruker2nifti torch #67

Open
SebastianoF opened this issue Nov 23, 2020 · 3 comments
Open

Passing over the bruker2nifti torch #67

SebastianoF opened this issue Nov 23, 2020 · 3 comments

Comments

@SebastianoF
Copy link
Owner

SebastianoF commented Nov 23, 2020

I've not been working with bruker data in a while now, therefore this repo can not have the test and the support that it would need to stay alive and to be useful.

I'm looking for a bruker2nifti main developer to take my place and take ownership of this repo.

If you are the one, I can share my knowledge and the best practices I have learned and implemented so far, providing support in the transition process. It is not a problem if you are new to python or new to coding in general, as long as you are willing to learn and you have the need to convert bruker images for the years to come.

Please do contact me via email if you are willing to keep this repo alive, in particular if you are already a user, and if you have ideas or need for possible new features and requirements.

@SebastianoF SebastianoF changed the title Passing the bruker2nifti torch Passing over the bruker2nifti torch Dec 27, 2020
@TheChymera
Copy link

@SebastianoF hi, I have been thinking for a while of extending the conversion to cover Bruker to BIDS (i.e. NIfTI and sidecar JSON files). Currently I'm doing it with a more complex workflow described here, but I believe it should be do-able in a standalone workflow similarly to how bruker2nifti outputs text files with metadata summaries.

I'd be more than happy to take the project over, if you could give me a more in-depth dev tour, please contact me (email in profile). The only caveat is that I do not use GUIs for my workflows, so if it's just me, that part will fall into disrepair — but I will try to recruit someone else for that.

@gdevenyi
Copy link
Contributor

brkraw https://github.com/BrkRaw/brkraw already has bids support, and we would very much welcome more developers to assist in maintaining and updating the software.

@SebastianoF
Copy link
Owner Author

Thanks @TheChymera!
I'll contact you shortly via email. No problem for the GUI (an good API would be a better idea than the naive tkinter layer that I implemented and that can be deprecated with no big deal).

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

No branches or pull requests

3 participants