BIDScoin is a user-friendly Python application suite that converts (“coins”) source-level (raw) neuroimaging data sets to standardized data sets that are organized according to the Brain Imaging Data Structure (BIDS) specification. Rather than depending on complex programmatic logic for source data-type identification, BIDScoin uses a mapping approach to discover the different source data types in your repository and convert them into BIDS data types. Different runs of source data are uniquely identified by their file system properties (e.g. file name or size) and by their attributes (e.g. ProtocolName from the DICOM header). Mapping information can be pre-specified (e.g. per site), allowing BIDScoin to make intelligent first suggestions on how to classify and convert the data. While this command-line procedure exploits all information available on disk, BIDScoin offers a Graphical User Interface (GUI) for researchers to check and edit these mappings – bringing in the missing knowledge that often exists in their heads only. This interactive step can also be skipped for employment in fully automated dataflow pipelines.
Data conversions are performed within plugins, such as plugins that employ dcm2niix, spec2nii or nibabel.
BIDScoin requires no programming knowledge in order to use it, but users can use regular expressions and plug-ins to further enhance BIDScoin’s power and flexibility, and readily handle a wide variety of source data types.
BIDScoin is developed at the Donders Institute of the Radboud University.
Features
[x] DICOM source data
[x] PAR/REC source data (Philips)
[x] NIfTI source data
[x] Physiological logging data*
[x] MR Spectroscopy data**
[x] PET/CT data
[x] Field maps*
[x] Multi-echo data*
[x] Multi-coil data*
[x] Plug-ins
[x] Stimulus/behavioural logfiles
* = Only DICOM source data
** = Only Twix, SDAT/SPAR and P-file source data
How to contribute
Are you a Python programmer with an interest in BIDS who knows about GE and/or Philips data? Are you experienced with parsing stimulus presentation log-files? Or do you have ideas to improve BIDScoin or its documentation? Have you come across bugs? In any case, you are more than welcome to provide feedback and to contribute to this project.
1 maintainer
Release files for bidscoin 4.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bidscoin-4.6.2.tar.gz | 699.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bidscoin-4.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / bidscoin-4.6.2.tar.gz
| Download URL | bidscoin-4.6.2.tar.gz |
|---|---|
| Size | 699.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91c1a48af0ab91953adfc248fc08165925b261d337a96ef4f8fbbeb0b00bdebe
|
|
BLAKE2b-256 checksum How to use checksums |
c9a46ee8cc37c38542bf057aefa898fa461a5880f2e08f7209bfb7484a9c048b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2025.
Transparency logRelease files / bidscoin-4.6.2-py3-none-any.whl
| Download URL | bidscoin-4.6.2-py3-none-any.whl |
|---|---|
| Size | 770.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a51f7dc90715f390f38bc5f35ebab04cadfb6bc3857e299d72e01f145f9a4c6c
|
|
BLAKE2b-256 checksum How to use checksums |
7342b00adf6ffb697e92fa1c8b5cadf009ac86fa50d2582f76c3b1f609931561
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2025.
Transparency log
