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

BEP030: Extend BIDS to add near-infrared spectroscopy (NIRS) #438

Closed
rob-luke opened this issue Mar 24, 2020 · 42 comments
Closed

BEP030: Extend BIDS to add near-infrared spectroscopy (NIRS) #438

rob-luke opened this issue Mar 24, 2020 · 42 comments
Labels

Comments

@rob-luke
Copy link
Member

I would like to propose extending BIDS to include near-infrared spectroscopy (NIRS) .

I have taken a look at the currently-active BEPs and could not see anything NIRS related. Is there already support for NIRS? And if not, is there sufficient interest for me to start a proposal?

@sappelhoff
Copy link
Member

Thanks for opening the issue Robert. I think NIRS support in BIDS would be great. There is already a similar initivative in the NIRS community: https://github.com/fNIRS/snirf

I am not sure in how far BIDS and SNIRF are parallel or whether they could be joined.

It'd be great to discuss this with the NIRS community and SNIRF developers!

@rob-luke
Copy link
Member Author

Thanks Stefan, I was unaware of SNIRF. It seems very well specified.

@lpollonini
Copy link
Collaborator

lpollonini commented Mar 27, 2020

Coincidentally, my collaborative group has been discussing this for the last few weeks, so I definitely second Robert's proposal and will be interested in actively participating. If it may help, I am familiar with the SNIRF format and I am involved with the proposing SfNIRS (Society for Functional Near Infrared Spectroscopy). Please let me know the next steps, thanks!

@rob-luke
Copy link
Member Author

rob-luke commented Mar 29, 2020

Thats great news @lpollonini. There is a BIDS extension proposal guide, and a BIDS extension template. I am happy to make a start on the proposal document and put it online for us to edit/comment (I will post link in this thread). And in the meantime I will try and get a few more people interested. @lpollonini is this plan ok with you?

@sappelhoff is this the usual way to proceed? Whats the simplest/cleanest BEP that you would recommend I take a look at to get started?

@lpollonini
Copy link
Collaborator

Sounds good to me, Robert.
I will wait for Stefan to educate us on the process (or anything we are missing), and then we can start coordinating the effort.

@sappelhoff
Copy link
Member

Hi @rob-luke and @lpollonini, indeed what you suggest sounds like a good workflow. Let me add to that:

  1. as a starting point, please read the governance document (it's not too long), specifically the parts relating to a BIDS Extension Proposal (BEP)
  2. use the two documents you linked for more guidance
  3. get as many people interested as possible, forming a core team and a team of people to review regularly and provide opinions

In addition, I think it'd also be cool to start this off with a short call, where everybody can explain their backgrounds / motivations, and ask open questions that are not easily addressed in our docs. I would leave organizing that call to you (we could find a suitable date via email, and then post the decision here for more interested people to join).

As current example BEPs I recommend:

@franklin-feingold @effigies did I forget some crucial hints?

@robertoostenveld
Copy link
Collaborator

robertoostenveld commented Mar 30, 2020

Hi @rob-luke and others

Last week we were meant to have a relatively small fNIRS toolkit course at the Donders, similar to these https://www.ru.nl/donders/agenda/donders-tool-kits/. This would be the first fNIRS toolkit for us, but we might make it into a yearly event. However, given the current situation the fNIRS toolkit has been postponed for now.

In this fNIRS toolkit course, I was to present on precisely BIDS and NIRS. I have just posted my slides online, see The Brain Imaging Data Structure and its use for fNIRS. I had planned to discuss how BIDS relates to SNIRF (which I consider perfectly compatible) and to propose "BEP028"(?) as BIDS for NIRS.

@robertoostenveld
Copy link
Collaborator

From my perspective related to this are fieldtrip/fieldtrip#1161, https://github.com/fieldtrip/fieldtrip/blob/master/data2bids.m (which includes some preliminary NIRS support) and documentations and examples that we have at http://www.fieldtriptoolbox.org/example/bids/ (no NIRS example yet, but that could be added). With @helenacockx we just finished the first draft fNIRS dataset in BIDS format.

@rob-luke
Copy link
Member Author

Hi @robertoostenveld,

It seems this issue came at a good time for all of us then. I am definitely on the same page as the slides you linked. How do you feel about the plan that Stefan proposed? Should I try and organise a call via email for the people in this thread? And in the meantime we see who else is interested. Or are you much further along this process?

@robertoostenveld
Copy link
Collaborator

Yes, please follow the plan that @sappelhoff outlined. I.e. get multiple people with different backgrounds (i.e. different labs/systems, but also acquainted with different softwares) involved, and get them to converge using a google doc.

@lpollonini
Copy link
Collaborator

lpollonini commented Mar 30, 2020

I agree on everything, and will start reach out to people who may be interested in joining in. How long we should give ourselves to form ideas and schedule the introductory call? Would 10-14 days be acceptable considering the current situation (people doing lots of online teaching./mentoring, dissertation defenses coming up, etc.)? Maybe sooner? Thanks!

@robertoostenveld
Copy link
Collaborator

Planning it within 2 weeks sounds acceptable to me. Also, people that might miss out on the first online meeting should be able to join the process later. The first meeting would be more on setting goals and agreeing on a style of working, than on tossing arguments around and deciding.

@lpollonini
Copy link
Collaborator

Shall we try April 9th or 10th?
No time is truly ideal with participants from all over the world, , but 7am US CDT / 2pm Europe / 10pm Syndey (+- 1 hour) seems manageable. What do you all think?

@robertoostenveld
Copy link
Collaborator

April 9 works for me, April 10 is Good Friday, which for me (and I suspect a lot of people) is a day off. Although week and weekend-days are now more similar while working at home, I think we should respect holidays if possible.

@lpollonini
Copy link
Collaborator

I agree, and I apologize. Good Friday was not marked on my calendar.
April 9th is good for me.

@sappelhoff
Copy link
Member

9th of April 2pm Berlin time sounds good to me 👍

@lpollonini
Copy link
Collaborator

Is there a preferred meeting platform that BEP people have been using successfully?
I would like to share this thread with the fNIRS community at large (500+ SfNIRS members and 1,300 on the Facebook group) and even if a small fraction will participate, we want to make sure the e-meeting remains manageable.

@rob-luke
Copy link
Member Author

9th of April is good for me too.

I have created a zoom call that anyone can join with details below (no account required by attendees). But happy to use another platform if people prefer. I am also happy to take minutes for the meeting / record the session.

Time: Apr 9, 2020 10:00 PM Australia/Melbourne 
Join from a PC, Mac, iPad, iPhone or Android device: 
    Please click this URL to start or join: https://macquarie.zoom.us/j/338374702
 
Join from dial-in phone line: 
    Dial: +61 2 8015 2088
    Meeting ID: 338 374 702 
    International numbers available: https://macquarie.zoom.us/u/acPY47YGNU 

Join from a H.323/SIP room system: 
    Dial: 61262227588
    or SIP:7588@aarnet.edu.au
    or H323: 338 374 702@182.255.112.21  (From Cisco)
    or H323:182.255.112.21## 338 374 702  (From LifeSize or Polycom)
    or 162.255.36.11 or 162.255.37.11 

    Meeting ID: 338 374 702

@rob-luke
Copy link
Member Author

@hamishib you may be interested in this.

@hamishib
Copy link

Great initiative @rob-luke, I will join the Zoom and see if I can contribute :)

@robertoostenveld
Copy link
Collaborator

As I am always confused with time zone differences (and even more so around daylight savings time changes), I scheduled it on arewemeetingyet to shows the meeting in everyones own timezone.

@sappelhoff
Copy link
Member

hehe. Good call @robertoostenveld it seems that @rob-luke scheduled the meeting for a different time than @lpollonini proposed in #438 (comment)

the arewemeetingyet link tells me that we meet at 10:00 (am!) UTC + 10 ... which would be 22:00 in Berlin ... would still be borderline okay with me. But just a heads up that this might be a confusion.

@robertoostenveld
Copy link
Collaborator

hmm, the confusion apparently is not yet gone. This is what I see
Screenshot 2020-03-31 at 10 53 02 which is 14:00 in Central Europe Time. That works for me.

@rob-luke
Copy link
Member Author

which is 14:00 in Central Europe Time

Isn't that what was proposed above? The call is scheduled for 10pm Aus time, which I checked was 2pm EU and 7am Houston. How did you get 10am Berlin time?

@sappelhoff
Copy link
Member

okay, I just misread the output 🤷‍♂️ I was confused by the time underneath the "For your calendar" heading.

So everything is fine, sorry :-)

@rob-luke
Copy link
Member Author

Ok cool. But I am open to other suggestions too. Taking calls at odd hours comes with the territory when you live upside down.

@rob-luke
Copy link
Member Author

rob-luke commented Apr 6, 2020

@robquant this might be of interest to you too.

@robquant
Copy link

robquant commented Apr 7, 2020

@rob-luke Thanks for the hint!

@rob-luke
Copy link
Member Author

rob-luke commented Apr 9, 2020

It was nice to meet everyone on the call.

I can create the draft google doc based on the BIDS spec template tomorrow and email around a link. Did anyone record who put there hands up to be in the smaller committee? If we gather those emails I can set the write access permissions. Then we can also discuss a preferred method of communication.

@lpollonini
Copy link
Collaborator

Thanks Robert, I just started an e-mail thread...

@manipulative
Copy link

waiting for good news from you guys!

@lpollonini
Copy link
Collaborator

Hello @manipulative, we have formed a core working group as a result of the initial meeting and we'll be posting he a link to the BEP draft (as soon as ready) for anyone to comment on.

@manipulative
Copy link

Hi @lpollonini , I do some hyperscanning researches by fNIRS. Thanks for your contribution to bids of fnirs!

@robertoostenveld
Copy link
Collaborator

Hi @lpollonini is there already a google doc online with a draft that I (and others) can read and/or contribute our ideas to?

@rob-luke
Copy link
Member Author

rob-luke commented Apr 28, 2020

Yes. We have a google doc. I can open access and post here tomorrow when I get to my work pc.

@rob-luke
Copy link
Member Author

Unless one of the others with access does it before then

@robertoostenveld
Copy link
Collaborator

I propose to share it such that others (i.e. people that do not explicitly have permissions) can only make suggestions. That ensures that the BEP leads keep in charge of all the edits and are aware of all changes to the actual text.

@manipulative
Copy link

Also want to view and comment it too

@rob-luke
Copy link
Member Author

The document can be found here.

I have set the access to public with only ability to add comments (I think, see figure below). If anyone has issues accessing please comment in this thread and we can address it.

image

@sappelhoff
Copy link
Member

This BEP is now official: BEP030, see: bids-standard/bids-website#123

@sappelhoff sappelhoff changed the title Extend BIDS to add near-infrared spectroscopy (NIRS) BEP030: Extend BIDS to add near-infrared spectroscopy (NIRS) May 8, 2020
@rob-luke
Copy link
Member Author

rob-luke commented Sep 9, 2020

The BEP has had some attention lately. I will now create an example dataset according to the current specification.

Now would be a good time to collect some edits/reviews/comments on the document if anyone is available or can share the link... https://bids.neuroimaging.io/bep030

I am particularly interested to gather comments from users of different NIRS types and vendors than I have experience with (e.g. frequency domain NIRS devices).

@rob-luke
Copy link
Member Author

Brief update:

  • The BEP is shaping up nicely and has recently had many changes and comments resolved.
  • A call for public review will be made in the society for fNIRS April newsletter.
  • A pre-review by the experts in this conversation would be appreciated before the public call.
  • Please unresolve any comments you think were prematurely closed.

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

No branches or pull requests

7 participants