Data Modality & Methodology Task Force

Hello everyone! My name is Elizabeth Hutchins and together with Hirotaka Iwaki [@hirotaka] I am co-leading the newly formed Data Modality & Methodology Documentation Task Force. We would like to introduce you to our task force and extend an invitation to any community members who might be interested in joining.

We are researchers dedicated to reproducible and collaborative data analysis methods. Last year, we worked on a Getting Started with Parkinson’s Disease Data guide. We want to go even further and give specific examples of code that the community can build upon for analyzing Parkinson’s Disease data.

The goal of this task force is to document standard data analysis methods and practices across multiple data modalities, with the aim of fostering reproducible and collaborative data analysis by creating and sharing resources that can be used by the wider research community. We will provide specific examples in the first year, and see the future of this effort as something that can be expanded upon year after year as the community grows. We also envision this task force as one that will complement the goals of the other task forces, for example, providing guidance for mentees in the mentorship and training initiatives.

Specific topics will be selected based on members’ expertise. Development of GitHub repositories will be the main focus. We will use GitHub, and other languages such as python and/or R depending on user preference. Potential projects include:

  • GitHub repository: template for standard data analysis projects
  • GitHub repository: [Cohort] + [data type], basic stats, QC, analysis
  • Combined analysis across multiple modalities
  • “Getting started” example

By joining this task force, members will have the opportunity to provide input to task force goals and outputs, contribute to the creation of a resource that would help other researchers in the community, and get credit for their contributions. We will have monthly meetings or progress check-ins to monitor progress. Our ideal timeline looks like:

  • August: kick-off meeting, goal sharing, proposal suggestions
  • September: proposal presentations, project assignments, team forming
  • October: lecture on good coding practice and/or getting started with GitHub/support
  • Nov, Jan, Feb - progress check-ins
  • March, April - wrapping up
  • May - present to other DCIs

If you are interested, please respond to this post and/or reach out to me or @hirotaka. Please also let us know if you have any questions in the below thread. We will send out the polls next week for the kick-off meeting.

We look forward to your participation and support!

8 Likes

Hello! I like this Task Force’s idea! Count me in!

3 Likes

Great ideas to put in place! I would be glad to be part of this task force.

3 Likes

Thank you for your support @danieltds and @jf.daneault! This is going to be very exciting!

1 Like

I’m happy to help in any way I can; count me in!

3 Likes

Hello,

I am very interested in this task force. I think that I can help (and learn) a lot with it.

3 Likes

Wonderful! Happy to have you @mattk and @peixott!

2 Likes

Hi, I would be happy to contribute as well.

3 Likes

Hi all! This is a great idea for a task force, and I’m keen to get involved! Thanks!

4 Likes

Thank you @AmgadDroby and @vcatterson ! Looking forward to your contributions. :slight_smile:

3 Likes

This is a great task force, very happy to join and help!

3 Likes

Hi all! Thank you for your interest. Looking forward to your contributions to this task force. Here is a link to the Doodle poll for our kickoff meeting. Please add your availability to the poll. @danieltds @jf.daneault @mattk @peixott @AmgadDroby @vcatterson @elahif01

4 Likes

Hi, I’m interested in joining this task force. Thanks.

3 Likes

@cameronreidhamilton , thank you for your interest! We will have a kick-off meeting at 12-1pm EST (4-5pm GMT) on Sep 11th. Please join us from this meeting link

2 Likes

Thank you to everyone who attended last Friday’s meeting! For those who couldn’t make it, here are the links to the presentation slides and meeting notes:

Please feel free to share any comments and suggestions! Our next meeting is scheduled for October, where members will have the opportunity to pitch their project ideas and form teams. Working on a project together will be a fantastic opportunity to learn from one another, and I’m very excited about it.

Fanny (@elahif01) and Thiago (@peixott) , we missed you last time but please feel free to add project ideas if you have some in mind!

Action Items:

  1. Fill out the Doodle poll (Please side-scroll there are 9 options. You can also change the timezone at the page.)
  2. If you have a project idea, please prepare 1–2 slides to pitch it at the next meeting.
5 Likes

Thank you for your interest everyone!

Don’t forget to fill out the Doodle poll for the next meeting if you haven’t already. Looking forward to expanding on our project ideas!

@cameronreidhamilton @jf.daneault @danieltds @mattk @peixott @AmgadDroby @vcatterson @elahif01

4 Likes

Thank you all for participating in the Doodle polls! It looks like the best time for most of us will be Friday, October 25, 2024, at 12:00 PM (EST). Please mark your calendars.

During this meeting, we’ll be pitching projects to each other and forming teams—it should be an exciting session! It seems that @danieltds already has 5 ideas to share. :grin:

I’ll be sending out the project pitch template shortly.

As always, it is open and anybody who is interested in will be welcomed. Please let us know!

5 Likes

We held our second TF meeting last Friday and had a productive discussion. For those who couldn’t attend, here are the slides and meeting notes:

We primarily discussed four potential project ideas, and we’ll be sharing more details about the projects soon via Discourse posts as well as how to participate. Keep an eye out for updates!

6 Likes

We are going to work asynchronously for now and get back together after the holidays.

Before our next meeting, if you can, each project should have a base repo with a README outlining the goals of the project. By a base repo, we mean creating an empty repo and adding a README page as follows:

  1. If you haven’t used GitHub before, or if you have and need a refresher, review their getting started docs
  2. Create a GitHub account if you don’t have one already
  3. Project leads: initiate a repo for your project, share that with your team
  4. Create a README in your project repo outlining the goals of the project. Team members can contribute!

If you get stuck feel free to reach out to me or @hirotaka , and/or we can discuss this at the next meeting as well. The goal is to get started and get some basic familiarity with GitHub before we dive in.

Please fill out this doodle poll with your availability for our next meeting.

Looking forward to meeting with everyone in January!

@cameronreidhamilton @danieltds @jf.daneault @mattk @peixott @AmgadDroby @vcatterson @elahif01 @AmgadDroby

6 Likes

Thank you for your responses to the Doodle poll. We will be meeting Wednesday, January 15th at 12PM - 1PM EST (GMT -5). 2025-01-15T19:00:00Z

One more note about this that I failed to mention in the above post - we are putting the repos (starting with the READMEs) on the MJFF GitHub page. If you need access, contact @jgottesman with your GitHub ID and he can add you.

@cameronreidhamilton @danieltds @jf.daneault @mattk @peixott @AmgadDroby @vcatterson @elahif01 @jonahkeller

4 Likes