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

Agenda for (second) May call | Wed 29 4pm / 3pm / 10noon / 7am #57

Closed
1 of 2 tasks
KirstieJane opened this issue May 15, 2019 · 1 comment
Closed
1 of 2 tasks
Assignees
Labels
community Building the BEP001 community

Comments

@KirstieJane
Copy link
Member

KirstieJane commented May 15, 2019

Next dev call: Wednesday 29 May at 4pm CEST / 3pm BST / 10am EDT / 7am PDT

All welcome, please see BIDS mailing list for zoom link (or ping @KirstieJane!)

Agenda

The following points are put in place by @KirstieJane after the call on 15 May....they might move around as we develop and discuss the extension 😸

Document merged changes: @KirstieJane & @agahkarakuzu

There are a few changes that are already merged to master but that aren't reflected in the ProposedChangesToSpecification.md file.

Update the examples: @lazaral, @tiborauer, @ChristophePhillips & @Gilles86

General driving principle is that for each new concept in the specification we have an example in the text (and maybe as a dataset?)

Empty files correctly named: @lazaral

Issues #34 & #46.

Real data in BIDS format: @tiborauer, @ChristophePhillips & @Gilles86

Issue #11.

List of metadata terms

Do the metadata terms that we have listed contain the information needed to run the processing pipelines? Are there any missing?

Run hmri toolbox on BIDS formatted data: @ChristophePhillips

Specifically, can we run the hmri toolbox on BEP001 formatted data? (And get out BEP001 formatted data!)

Field maps: @agahkarakuzu

Expand definition of field maps in specification. Issue #44.

Symbolic links: @KirstieJane

Need to add to the specification something about being able to symlink derivatives files to raw. See #25

  • Specifically to allow outputs to be used with current BIDS-Apps.
  • In the future, hopefully the BIDS-Apps will be able to take inputs from the derivatives, so this linking is a band-aid to help qMRI researchers get into the BIDS-App ecosystem, not a long term plan 😄

Timeline

It would be GREAT to get a PR open to the main specification before OHBM. Documenting what we have done (and why we have done it) is one of the big steps in getting there.... 💪 Keep up the hard work 🏋️ 🏋️‍♀️ 👾

We'll plan to meet in person at OHBM in the Open Science Room: ohbm/OpenScienceRoom2019#18

@KirstieJane KirstieJane added the community Building the BEP001 community label May 15, 2019
@KirstieJane KirstieJane self-assigned this May 15, 2019
@ChristophePhillips
Copy link
Collaborator

Hi,
I might be a bit late for the meeting.
Moreover since I'm running behind the clock I haven't sufficiently investigated the MPM data set to provide a nice feedback on how it BIDSifies, if parameters are missing or not matching definitions in BIDS, etc. Sorry about that !
At the latest, I'll do that during the Hackathon in Rome.

@Gilles86 Gilles86 closed this as completed Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Building the BEP001 community
Projects
None yet
Development

No branches or pull requests

3 participants