BIDS Execution Specification

[gkiar]

Project info

Title: BIDS Execution Specificaion

Project lead: Chris Markiewicz (@effigies), Greg Kiar (@gkiar)

Timezone: UTC-4/UTC-5

Description: An extension proposal that has been in the works for a while, and builds upon the original BIDS Apps paper, this extension seeks to further standardize the execution specification for BIDS applications, including integration with Boutiques.

Link to project:

• Related issue
• Extension proposal

Mattermost handle: @Markiewicz, @gkiar

Goals for the OHBM Brainhack

• Identify the current state of the proposal
• Draft list of remaining questions to be answered and filler which needs to be provided
• Seek community feedback
• Finalize proposal submission (reach)

Good first issues:

• Read the proposal & ask any question
• Comment on the PR/Google Doc with feedback
• Inside the Google doc, any comment beginning with "TODO: Good first issue" (e.g. gathering related terms from the BIDS-Raw specification)

Skills:

• (necessary) Interest in launching computational pipelines on BIDS datasets
• (ideal) Some knowledge of the original BIDS Apps proposal
• (ideal) Some knowledge of Boutiques
• (not necessary, but would be helpful) knowledge of integrating tools in cloud or high performance computing systems

Chat channel: ~hbm-bids-exec

Image for the OHBM brainhack website

Project submission

Submission checklist

Please include the following above (all required):

• Link to your project: could be a code repository, a shared document, etc. See here
• Include your Mattermost handle (i.e. your username). If you do not have an account, please sign up here.
• Goals for the OHBM Brainhack: describe what you want to achieve during this brainhack. See here.
• Flesh out at least 2 "good first issues": those are tasks that do not require any prior knowledge about your project, could be defined as issues in a GitHub repository, or in a shared document, cf here.
• Skills: list skills that would be particularly suitable for your project. We ask you to include at least one non-coding skill, cf. here.
• Chat channel: A link to a chat channel that will be used during the OHBM Brainhack. This can be an existing channel or a new one. We recommend using the Brainhack space on mattermost, cf. here.
• Provide an image of your project for the OHBM brainhack website

You can also include information about (all optional):

• Someone co-leading the project in the timeslot you have not selected to provide additional visibility.
• Number of participants, cf. here
• Twitter-size summary of your project pitch, cf. here
• Set up a kanban board on your repository to better divide the work and keep track of things, cf here
• Project snippet for the OHBM Brainhack website, cf. here

We would like to think about how you will credit and onboard new members to your project. We recommend reading references from this section. If you'd like to share your thoughts with future project participants, you can include information about (recommended):

• Specify how will you acknowledge contributions (e.g. listing members on a contributing page).
• Provide links to onboarding documents if you have some.

QMENTA has agreed to sponsor the event and provide computational resources through their platform.

• Get in touch with QMENTA through their Brain Innovation Hub Slack space, if you think your project would benefit from their support.

[gkiar]

hi @ohbm/project-monitors: My project is ready!

[gkiar]

cc: @rob-luke @adelavega @francopestilli

@rob-luke I know you're based in Australia, so what times of day would work best for you? I believe that @effigies and I are in UTC-5, and @adelavega is generally in UTC-6. It could be great to sync up once per day in the event to decide how we can work asynchronously given that there isn't likely to be much temporal overlap.

[rob-luke]

I can do any time from 8am to 10pm AEST if that works? If not, then don't worry too much about it.

[gkiar]

@rob-luke If you want, you and I could touch base this morning for you (evening of the 15th, for me) and chat about the project so you're able to hack without us asynchronously for the whole event. Reach out via Mattermost once you're up and we'll coordinate? Won't need to be a long call.

[gkiar]

To make things a bit easier to find, here is a link to the google doc that contains the spec draft.