-
Notifications
You must be signed in to change notification settings - Fork 78
Landing page #725
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
julia-pfarr
wants to merge
46
commits into
bids-standard:main
Choose a base branch
from
julia-pfarr:landing_page
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Landing page #725
Changes from all commits
Commits
Show all changes
46 commits
Select commit
Hold shift + click to select a range
fc33deb
[DATALAD] Recorded changes
Remi-Gau 98ac33a
first updates to landing page
julia-pfarr b3da874
Merge branch 'main' of github.com:bids-standard/bids-website into lan…
julia-pfarr 08f3732
resolve merge conflict
julia-pfarr f5b8ce4
first modifications for landing page
julia-pfarr e76dd7d
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] c5aea7f
remove minify plugin; not needed
julia-pfarr 1dc57ae
Merge branches 'landing_page' and 'landing_page' of github.com:julia-…
julia-pfarr 9c46d4d
Apply suggestions from code review
julia-pfarr 86bcd37
first modifications based on review
julia-pfarr 5fb71e1
Merge branch 'landing_page' of github.com:julia-pfarr/bids-website in…
julia-pfarr e5cbc5c
Merge branch 'main' into landing_page
julia-pfarr 6ff0239
change logo path
julia-pfarr 407cfb2
Merge branch 'landing_page' of github.com:julia-pfarr/bids-website in…
julia-pfarr 03b285f
Merge branch 'main' into landing_page
Remi-Gau 3bebffb
modify landing page according to code review
julia-pfarr faa7c4c
adjust heights and spaces
julia-pfarr 5d6d36b
adjust spacing in feature boxes
julia-pfarr e705068
adjust mobile specs
julia-pfarr d355d39
Merge branch 'landing_page' of github.com:julia-pfarr/bids-website in…
julia-pfarr 875aace
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 11ee739
Merge branch 'main' into landing_page
julia-pfarr bfd1758
try other path for logo
julia-pfarr dcedb83
Merge branch 'landing_page' of github.com:julia-pfarr/bids-website in…
julia-pfarr 6af0a1c
Merge branch 'main' into landing_page
julia-pfarr b689b2f
Merge branch 'main' of github.com:bids-standard/bids-website into lan…
julia-pfarr 26a4add
code review and add logo
julia-pfarr cee7a70
Merge branch 'landing_page' of github.com:julia-pfarr/bids-website in…
julia-pfarr 033c997
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 450f141
fix navigation sidebars
julia-pfarr 68ba06d
change link for logo
julia-pfarr dd3f5a7
Merge branch 'landing_page' of github.com:julia-pfarr/bids-website in…
julia-pfarr 25c92f7
Apply suggestions from code review
julia-pfarr c0949f2
Merge branch 'main' into landing_page
Remi-Gau 1f7d49d
rm pr template changes
Remi-Gau a19cc22
rm logo and copy from spec on build
Remi-Gau 30a6b94
format with djlint
Remi-Gau 0e79749
revert config changes
Remi-Gau 51c6d5f
revert
Remi-Gau 982c828
mv
Remi-Gau db05f11
mv
Remi-Gau 68502f4
comment
Remi-Gau 7835a8c
mv
Remi-Gau 3e2ed8d
evert
Remi-Gau eeb8368
fix contrast
Remi-Gau 34978ff
improve dark mode contrast
Remi-Gau File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julia-pfarr marked this conversation as resolved.
Show resolved
Hide resolved
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,165 +1,4 @@ | ||
| --- | ||
| template: home.html | ||
| title: BIDS | ||
| --- | ||
|
|
||
| Experiments in neuroscience result in complex data that can be arranged in many different ways. | ||
| For a long time, there was no consensus how to organize and share experimental data. | ||
| Even two researchers working in the same lab could opt to arrange their data in a different way. | ||
| Lack of consensus (or a standard) leads to misunderstandings and time wasted on rearranging data | ||
| or rewriting scripts expecting certain structure. | ||
| With the Brain Imaging Data Structure (BIDS), | ||
| we describe a simple and easy to adopt way of organizing neural and associated, such as behavioral, data. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| BIDS was heavily inspired by the format used internally by the OpenfMRI repository | ||
| that is now known as [OpenNeuro][openneuro]. | ||
| While working on BIDS we consulted many neuroscientists to make sure it covers most common experiments, | ||
| but at the same time is intuitive and easy to adopt. | ||
| The specification is intentionally based on simple file formats and folder structures | ||
| to reflect current lab practices and make it accessible to a wide range of scientists coming from different backgrounds. | ||
|
|
||
| ## BIDS is a community effort | ||
|
|
||
| BIDS is developed by the community for the community | ||
| and everybody can [become a part of the community](./extensions/index.md). | ||
|
|
||
| The most important part of BIDS are the users: | ||
| if more people use it, more data will be shared and the more powerful it will become. | ||
|
|
||
| <strong>We want to make it easy to learn</strong> and more adopted. | ||
|
|
||
| Since BIDS is platform independent | ||
| and still an adapting, growing tool, the greater the community, the better it will be. | ||
|
|
||
| ## Specification vs. Ecosystem | ||
|
|
||
| Since the inception of the BIDS specification that documents how to organize neural and associated data, | ||
| a large ecosystem of tools and resources has evolved around BIDS. | ||
|
|
||
| A few of the key elements of this ecosystem are | ||
| the [BIDS specification](http://bids-specification.readthedocs.io/) with the nitty-gritty details, | ||
| <!-- markdown-link-check-disable --> | ||
| the [starter kit](./getting_started/index.md) with a simple explanation how to work with it, | ||
| <!-- markdown-link-check-enable --> | ||
| the [BIDS validator](https://github.com/bids-standard/bids-validator) to automatically check datasets for adherence to the specification, | ||
| [BIDS Apps](https://doi.org/10.1371/journal.pcbi.1005209), a collection of portable pipelines that understand BIDS datasets, | ||
| and [OpenNeuro][openneuro] as a database for BIDS formatted datasets. | ||
|
|
||
| A non-exhaustive list of further tools can be found in the [tools](./tools/index.md) section. | ||
|
|
||
| With the ongoing development of new tools and resources it is important to keep in mind | ||
| that the [BIDS specification](http://bids-specification.readthedocs.io/) remains | ||
| the standard according to which the entire ecosystem must adhere. | ||
|
|
||
| ## Philosophy | ||
|
|
||
| Another part is that BIDS is striving to not reinventing other standards and metadata ontologies but reuse them: | ||
|
|
||
|  | ||
|
|
||
| ## Benefits | ||
|
|
||
| <div class="grid cards" markdown> | ||
|
|
||
| - :material-account-group:{ .lg .middle } **For the public good** | ||
|
|
||
| --- | ||
|
|
||
| - Lowers scientific waste | ||
| - Gives opportunity to less-funded researchers | ||
| - Improves efficiency | ||
| - Spurs innovation | ||
|
|
||
| - :recycle:{ .lg .middle } **For yourself** | ||
|
|
||
| --- | ||
|
|
||
| - You are likely the future user of the data and data analysis pipelines you’ve developed | ||
|
|
||
| - Enables and simplifies collaboration | ||
|
|
||
| - Reviewers and funding agencies like to see reproducible results | ||
|
|
||
| - Open-science based funding opportunities and awards available | ||
| (for instance: OHBM Replication Award, Mozilla Open Science Fellowship, | ||
| Google Summer of Code, and so on.) | ||
|
|
||
| </div> | ||
|
|
||
| By using this standard you will benefit in the following ways: | ||
|
|
||
| - It will be easy for another researcher to work on your data. | ||
| To understand the organization of the files and their format you will only need to refer them to this document. | ||
| This is especially important if you are running your own lab and anticipate more than one person working on the same data over time. | ||
| By using BIDS you will save time trying to understand and reuse data acquired by a graduate student or postdoc that has already left the lab. | ||
|
|
||
| - There is a growing number of [data analysis software packages](./tools/index.md) that can understand data organized according to BIDS. | ||
|
|
||
| - Databases such as [OpenNeuro.org](http://openneuro.org), [LORIS](http://www.loris.ca), [COINS](https://coins.trendscenter.org), [XNAT](https://central.xnat.org/), [SciTran](https://scitran.github.io/), and others will accept and export datasets organized according to BIDS. | ||
| If you ever plan to share your data publicly (nowadays some journals require this) you can speed up the curation process by using BIDS. | ||
|
|
||
| - There are [validation tools](https://github.com/bids-standard/bids-validator) (also available [online](http://bids-standard.github.io/bids-validator/)) that can check your dataset integrity and let you easily spot missing values. | ||
|
|
||
| ## Further information | ||
|
|
||
| - Good introductions to the BIDS standard can be found in the initial | ||
| [paper published in Scientific Data](https://www.nature.com/articles/sdata201644), | ||
| as well as in the follow up papers on specific modalities: | ||
| [MEG](https://www.nature.com/articles/sdata2018110), | ||
| [EEG](https://www.nature.com/articles/s41597-019-0104-8), | ||
| [iEEG](https://www.nature.com/articles/s41597-019-0105-7), | ||
| [genetics](https://doi.org/10.1093/gigascience/giaa104), | ||
| [PET](https://doi.org/10.1038/s41597-022-01164-1), | ||
| [microscopy](https://doi.org/10.3389/fnins.2022.871228), | ||
| [qMRI](https://doi.org/10.1038/s41597-022-01571-4), | ||
| [ASL](https://www.nature.com/articles/s41597-022-01615-9), | ||
| [NIRS](https://www.nature.com/articles/s41597-024-04136-9), | ||
| [motion](https://www.nature.com/articles/s41597-024-03559-8), | ||
| and [MRS](https://www.nature.com/articles/s41597-025-05543-2). | ||
|
|
||
| - Look through some of the community's [presentations on BIDS](https://osf.io/yn93h/). | ||
|
|
||
| - Take a look at how the community [uses BIDS](https://medium.com/stanford-center-for-reproducible-neuroscience/bids-usage-survey-results-72637ff039c4). | ||
|
|
||
| - We have constructed a [grant writing kit](./impact/index.md) | ||
| to assist you in putting together BIDS-related grant proposals. | ||
|
|
||
| - We submitted an application to [The Neuro Open Science in action prize 2020](https://www.mcgill.ca/neuro/open-science/neuro-open-science-action-prize-2020). | ||
| Please find our [associated application](./assets/BIDS-materials/2020_TheNeuro_OpenScienceInAction_application.pdf). | ||
|
|
||
| **Leave comments about the site below:** | ||
|
|
||
| --- | ||
|
|
||
| <div style="display: flex; justify-content: space-evenly; align-items: center; flex-wrap: wrap"> | ||
| <div> | ||
| <a href="https://www.incf.org/"> | ||
| <img src="./assets/img/logos/INCF.png" | ||
| alt="INCF" | ||
| width=200px> | ||
| </a> | ||
| </div> | ||
| <div> | ||
| <a href="https://summerofcode.withgoogle.com/"> | ||
| <img src="./assets/img/logos/GSoC_220px.png" | ||
| alt="GSOC" | ||
| width=200px> | ||
| </a> | ||
| </div> | ||
| <div> | ||
| <a href="http://grantome.com/grant/NIH/R24-MH114705-01"> | ||
| <img src="./assets/img/logos/NIH.png" | ||
| alt="NIH" | ||
| width=200px> | ||
| </a> | ||
| </div> | ||
| <div> | ||
| <a href="https://www.arnoldventures.org/newsroom/laura-and-john-arnold-foundation-announces-3-8-million-grant-to-stanford-university-to-improve-the-quality-of-neuroscience-research"> | ||
| <img src="./assets/img/logos/arnold_foundation.png" | ||
| alt="Arnold Ventures" | ||
| width=200px> | ||
| </a> | ||
| </div> | ||
| </div> |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy the logo from the spec during the build