Create Labels and Milestones for Research Projects and Grants

[praeducer]

• Goal is to help devs understand why they are working on certain features and how important/urgent those features are. This can also be used to manage research projects more effectively.
• We want to provide transparency to the devs of how their work ties into research goals and research projects. These should labels. Like tagging Singularity as halfpipe.
• Can help relate dev tasks to grant deadlines, paper submission deadlines, and conference deadlines as well as timelines coordinating with other groups. These should be milestones.
• This can help aid in requirements analysis so we know user needs.
• Evangelizing our impact such as all of the research papers we've been a part of - a continually updated list of concrete accomplishments to celebrate
• Gather a list of upcoming deadlines as well as any in progress research we are supporting.
• Send a blast out to the algorithms channel to share these goals and ask for help in tracking research projects. I can help manage any efforts that involve leveraging COINSTAC to get research done.
• Reshare the retrospective post and mention how the devs needs to use these new labels and milestones.

[praeducer]

Just messaged the algorithms channel in Slack and Sandeep for a list.

[praeducer]

Related to the discussions on our full-team meeting today and what I posted in #coinstac-algorithms, I wanted to start a discussion here: How can we better relate dev work back to research goals and deadlines? What changes to our collaboration processes and tooling should we make?

Currently, I'm thinking of anything with a deadline should be a Milestone. Then, anything that is fairly consistent throughout the year (like research groups, projects, grants, and maybe even the PI's/researcher's themselves) would be Labels.

Also, any deadlines should be shared out as calendar events. These could be things like submission deadlines for conferences and grants.

The hardest part of this is getting the humans to follow the patterns... like ideally whoever is leading the project should add the deadline to a shared calendar we can all see and needs to mention it during our weekly meetings.

[praeducer]

sandeep panta 11:39 Here are some I have on the list for upcoming deadlines: -Singularity feature without job scheduler (Testing group : Halfpipe team,), impact factor: high, reason: new channels and user groups who only have access to Singularity can join the research which leads to research publications and interesting results -Singularity with job scheduler , more sites have this setup fro my experience, Ohio state university (Jess), ENIGMA groups, Gunter's groups, impact factor same as above if not higher -Computation development: Name of algorithm-Decentralized SBM, helps run ICA on sMRI data which will be very useful and ICA is something Vince is known for, so this will be a unique highlight feature that leads to cool research publications. Debrata Saha , a phd student is working on this. --Computation development: Name of algorithm- Decentralized version of multi-site canonical correlation analysis with reference + joint-independent component analysis ( mCCAR+jICA) approach in Fusion ICA toolbox (FIT) Paper link: https://ieeexplore.ieee.org/document/7973190, Sumanth the new GRA is working on this. Impact factor : high since its a new algorithm in COINSTAC.

[praeducer]

OHBM, NeurIPS are other good ones to include.

[praeducer]

I have started the pattern in Github and in Outlook calendar for establishing deadlines and tracking accomplishments via Milestones. Here are the first three:

• NeurIPS Content Submission
• OHBM Content Submissions
• EMBC Paper Submission Deadline (IEEE Engineering in Medicine and Biology Society)

@sandeep panta and I are working on how to add these to a shared team calendar via a team email alias.

These can be used to make sure we plan ahead to reduce stress and also to make sure we can better schedule other improvements to COINSTAC. This will also aid in summarizing and associating all of our work with accomplishments like research papers, projects, and grants.

[praeducer]

Created a separate task for calendar and file sharing: https://github.com/trendscenter/coinstac/issues/1663

[praeducer]

Per Sandeep: Just absorbing some of Vince feedback today. I think the takeaway from tagging github tasks to achieve transparency for devs and efficiency, should be targeted more towards projects, end users awaiting coinstac feature, paper submissions etc. I think what Vince was saying was that, Grants is such a big umbrella that everything can be tagged into a grant pretty much, since there are basically handful of big grants supporting it. Once we get priority of projects from PI's, wishlist items etc. which would be my task, between us we can use that for tagging issues, and that should be satisfying the goal of dev transparency, motivation, better tracking. So I believe he was just suggesting it would be an extra unnecessary layer to have a tag that says grant since everything we develop falls under some grant practically. Just want to make sure we are synced up on this incase what Vince said was confusing or something. But gathering paper submission deadlines, projects, features, wish lists etc. is still my task that will be help us plan sprints.

[praeducer]

Frontiers has a recently launched research collection, Neurological and Neuropsychiatric Disorders Affecting Military Personnel and Veterans. In­formation on the collection can be found here. The deadline for submission is June 2023, but Frontiers fast-track review process, led by the editorial team, means each article is published online as soon as it’s been successfully peer-reviewed and accepted (typically within 61 days). As an open-access journal, publishing fees are applied to accepted articles. Please contact neurology.submissions@frontiersin.org to discuss fees, institutional waivers, and discounts.