INCF/OCNS Software WGhttps://ocns.github.io/SoftwareWG/2023-10-10T10:29:42+01:00The INCF/OCNS Software Working GroupWG meeting 09 October 20232023-10-10T10:29:42+01:002023-10-10T10:29:42+01:00Ankur Sinhatag:ocns.github.io,2023-10-10:/SoftwareWG/2023/10/10/wg-meeting-09-october-2023.html<p class="first last">These are the minutes from the working group meeting on 09 October, 2023.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 09th October 2023.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in November</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li>Marcel Stimberg</li>
<li>Ankur Sinha</li>
</ul>
<p>Regrets:</p>
<ul class="simple">
<li>Shailesh Appukuttan</li>
</ul>
<div class="section" id="agenda">
<h3>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h3>
<ul class="simple">
<li>Introductions, get to know each other</li>
<li>Announcements<ul>
<li><span class="caps">CNS</span> 2024 will be in Natal, Brazil. July 20-24, 2024: <a class="reference external" href="https://www.cnsorg.org/cns-2024">https://www.cnsorg.org/cns-2024</a></li>
</ul>
</li>
<li>Task force updates<ul>
<li>Simselect</li>
<li>Cookbook</li>
</ul>
</li>
<li>Ideas for more sessions (tutorials/spotlights/dev sessions)</li>
<li><span class="caps">OCNS</span> Director elections: self nominations are open till 11th October</li>
</ul>
</div>
<div class="section" id="minutes">
<h3>Minutes<a class="headerlink" href="#minutes" title="Permalink to this headline">⋆</a></h3>
<div class="section" id="tasks-from-last-meeting">
<h4>Tasks from last meeting<a class="headerlink" href="#tasks-from-last-meeting" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>No tasks from last meeting</li>
</ul>
</div>
<div class="section" id="task-force-updates">
<h4>Task force updates<a class="headerlink" href="#task-force-updates" title="Permalink to this headline">⋆</a></h4>
<div class="section" id="simselect">
<h5>Simselect<a class="headerlink" href="#simselect" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>v0.1 prototype live at: <a class="reference external" href="https://simselect.fly.dev/project_browser">https://simselect.fly.dev/project_browser</a></li>
<li>meets every two weeks on Wednesday at 1300 <span class="caps">UTC</span> (see <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/117">this ticket</a> for announcements)</li>
<li>consolidated notes are here: <a class="reference external" href="https://hackmd.io/LWjtz9ykQbm7yg5X_RKpCQ">https://hackmd.io/LWjtz9ykQbm7yg5X_RKpCQ</a></li>
<li>working on next version</li>
<li>looking for more people to get involved to<ul>
<li>help with the design of the next iteration</li>
<li>help us understand how to best display data</li>
<li>help with implementation</li>
<li>help with testing</li>
<li>provide feedback on all updates to the application</li>
</ul>
</li>
<li><span class="caps">ACTION</span>: Ankur e-mail list calling for more participation</li>
</ul>
</div>
<div class="section" id="cookbook">
<h5>Cookbook<a class="headerlink" href="#cookbook" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>lives at <a class="reference external" href="https://ocns.github.io/CompNeuroCookBook/index.html">https://ocns.github.io/CompNeuroCookBook/index.html</a></li>
<li>open for more contributions</li>
<li>if you have a code snippet you use regularly, please share it with the community<ul>
<li>how to contribute: <a class="reference external" href="https://ocns.github.io/CompNeuroCookBook/Contributing.html">https://ocns.github.io/CompNeuroCookBook/Contributing.html</a></li>
</ul>
</li>
</ul>
</div>
</div>
<div class="section" id="ocns-elections">
<h4><span class="caps">OCNS</span> elections<a class="headerlink" href="#ocns-elections" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>Candidate nominations are still open, there’s still time to nominate yourself: <a class="reference external" href="https://www.cnsorg.org/election-procedures">https://www.cnsorg.org/election-procedures</a></li>
</ul>
</div>
<div class="section" id="other-discussion">
<h4>Other discussion<a class="headerlink" href="#other-discussion" title="Permalink to this headline">⋆</a></h4>
<div class="section" id="satellite-tutorials-in-2023-2024">
<h5>Satellite tutorials in 2023/2024<a class="headerlink" href="#satellite-tutorials-in-2023-2024" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>not sure if a week of online tutorials is the best format, given our experience in 2021</li>
</ul>
</div>
<div class="section" id="replication-challenge">
<h5>Replication challenge<a class="headerlink" href="#replication-challenge" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>Similar to the <a class="reference external" href="https://paperswithcode.com/rc2022"><span class="caps">ML</span> replication challenge</a></li>
<li>Replicate published models</li>
<li>Submit to <a class="reference external" href="http://rescience.github.io/read/">rescience-c</a> for review + publication</li>
<li>Will involve lots of community members, who already replicate existing models in their projects</li>
<li>Will involve simulator developers who can help people with their specific questions</li>
<li>Fits in with both <span class="caps">INCF</span>/<span class="caps">OCNS</span> goals</li>
<li><span class="caps">ACTION</span>: Ankur mail <span class="caps">OCNS</span>/<span class="caps">INCF</span>, software wg, and simulator developers to get feedback on idea</li>
<li><span class="caps">ACTION</span>: Ankur open ticket to collect feedback</li>
</ul>
</div>
</div>
</div>
</div>
WG meeting 21 April 20232023-09-25T11:19:25+01:002023-09-25T11:19:25+01:00Ankur Sinhatag:ocns.github.io,2023-09-25:/SoftwareWG/2023/09/25/wg-meeting-21-april-2023.html<p class="first last">These are the minutes from the working group meeting on 21 April, 2023.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 21st April 2023.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in October</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<p>0800</p>
<ul class="simple">
<li>Brent Huisman</li>
<li>Ankur Sinha</li>
<li>Marcel Stimberg</li>
<li>Chitaranjan Mohaptra</li>
</ul>
<div class="section" id="agenda">
<h3>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h3>
<ul class="simple">
<li>Tasks from last meeting: <a class="reference external" href="https://ocns.github.io/SoftwareWG/2023/03/20/wg-meeting-15-march-2023.html">https://ocns.github.io/SoftwareWG/2023/03/20/wg-meeting-15-march-2023.html</a></li>
<li>Tasks force updates</li>
<li><span class="caps">RFC</span>: <span class="caps">WG</span> presence at <span class="caps">CNS</span> 2023 #125</li>
<li>Call for self-nominations for co-chairing the <span class="caps">WG</span> #129</li>
<li>Use of <a class="reference external" href="https://gitter.im/OCNS/SoftwareWG">https://gitter.im/<span class="caps">OCNS</span>/SoftwareWG</a></li>
</ul>
</div>
<div class="section" id="minutes">
<h3>Minutes<a class="headerlink" href="#minutes" title="Permalink to this headline">⋆</a></h3>
<div class="section" id="tasks-from-last-meeting">
<h4>Tasks from last meeting<a class="headerlink" href="#tasks-from-last-meeting" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>All actions complete</li>
</ul>
</div>
<div class="section" id="presence-at-cns-2023">
<h4>Presence at <span class="caps">CNS</span> 2023<a class="headerlink" href="#presence-at-cns-2023" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>Informal get together in breaks/after the conference.</li>
</ul>
</div>
<div class="section" id="task-force-updates">
<h4>Task force updates<a class="headerlink" href="#task-force-updates" title="Permalink to this headline">⋆</a></h4>
<div class="section" id="simselect">
<h5>Simselect<a class="headerlink" href="#simselect" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>working towards a 0.1 <span class="caps">MVP</span> release: <a class="reference external" href="https://github.com/OCNS/simselect/milestone/1">https://github.com/<span class="caps">OCNS</span>/simselect/milestone/1</a></li>
<li>prototype live here: <a class="reference external" href="https://simselect.fly.dev">https://simselect.fly.dev</a></li>
<li>we continue to meet every two weeks, recurrent meeting at 1300 <span class="caps">UTC</span> on Wednesday, next meeting on 3 May</li>
</ul>
</div>
<div class="section" id="cookbook">
<h5>Cookbook<a class="headerlink" href="#cookbook" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>It was decided another guideline isn’t needed. Many exist.</li>
<li>Task force concluded. New task force: CompNeuroCookBook</li>
</ul>
</div>
<div class="section" id="new-task-force-compneurocookbook">
<h5>New task force: CompNeuroCookBook<a class="headerlink" href="#new-task-force-compneurocookbook" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>example: <a class="reference external" href="https://faircookbook.elixir-europe.org/content/home.html">https://faircookbook.elixir-europe.org/content/home.html</a></li>
<li><a class="reference external" href="https://github.com/OCNS/CompNeuroCookBook">https://github.com/<span class="caps">OCNS</span>/CompNeuroCookBook</a></li>
<li><span class="caps">ACTION</span>: Ankur <a class="reference external" href="https://github.com/OCNS/CompNeuroCookBook/issues/7">https://github.com/<span class="caps">OCNS</span>/CompNeuroCookBook/issues/7</a>: <span class="caps">DONE</span></li>
<li><span class="caps">ACTION</span>: Ankur close old ticket on guidelines taskforce with explanation: <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/116">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/116</a></li>
</ul>
</div>
</div>
<div class="section" id="call-for-self-nominations-for-co-chairing-the-wg-129">
<h4>Call for self-nominations for co-chairing the <span class="caps">WG</span> #129<a class="headerlink" href="#call-for-self-nominations-for-co-chairing-the-wg-129" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>Marcel Stimberg is the/a new co-chair</li>
</ul>
</div>
<div class="section" id="use-of-https-gitter-im-ocns-softwarewg">
<h4>Use of <a class="reference external" href="https://gitter.im/OCNS/SoftwareWG">https://gitter.im/<span class="caps">OCNS</span>/SoftwareWG</a><a class="headerlink" href="#use-of-https-gitter-im-ocns-softwarewg" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>Create new issue to highlight gitter channel: <span class="caps">DONE</span></li>
<li>Ankur stress on Gitter channel in logs e-mail</li>
<li>Use video call feature in Gitter/Element for future meetings: <span class="caps">DONE</span></li>
<li>Pin message to <span class="caps">GH</span> Discussions pointing users to Gitter: <span class="caps">DONE</span></li>
</ul>
</div>
</div>
</div>
WG meeting 15 March 20232023-03-20T18:09:22+00:002023-03-20T18:09:22+00:00Ankur Sinhatag:ocns.github.io,2023-03-20:/SoftwareWG/2023/03/20/wg-meeting-15-march-2023.html<p class="first last">These are the minutes from the working group meeting on 15 March, 2023.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 15th March 2023.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in March</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<p>0800</p>
<ul class="simple">
<li>Ankur Sinha</li>
<li>Marcel Stimberg</li>
<li>Shailesh Appukuttan</li>
<li>Chitaranjan Mohaptra</li>
</ul>
<p>1700</p>
<ul class="simple">
<li>Ankur Sinha</li>
<li><span class="caps">AHSAN</span> <span class="caps">UL</span> <span class="caps">HAQ</span> (Masters student in Physics)</li>
<li>KOffivi (Masters student in <span class="caps">HPC</span>)</li>
</ul>
<div class="section" id="agenda">
<h3>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h3>
<ul class="simple">
<li>Tasks from last meeting: <a class="reference external" href="https://ocns.github.io/SoftwareWG/2023/03/08/wg-meeting-14-february-2023.html">https://ocns.github.io/SoftwareWG/2023/03/08/wg-meeting-14-february-2023.html</a></li>
<li><span class="caps">RFC</span> <span class="caps">CNS2023</span>: <span class="caps">RFC</span>: <span class="caps">WG</span> presence at <span class="caps">CNS</span> 2023: <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/125">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/125</a></li>
<li>Tasks force updates</li>
</ul>
</div>
<div class="section" id="minutes">
<h3>Minutes<a class="headerlink" href="#minutes" title="Permalink to this headline">⋆</a></h3>
<div class="section" id="tasks-from-last-meeting">
<h4>Tasks from last meeting<a class="headerlink" href="#tasks-from-last-meeting" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>All actions complete</li>
<li><span class="caps">ACTION</span>: Shailesh open new ticket for new co-chair: <span class="caps">DONE</span><ul>
<li><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/129">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/129</a></li>
<li>Please self-nominate, or speak to colleagues and nominate them.</li>
<li>To nominate, e-mail the current chairs (ankur <span class="caps">DOT</span> sinha <span class="caps">AT</span> ucl <span class="caps">DOT</span> ac <span class="caps">DOT</span> uk; appukuttan <span class="caps">DOT</span> shailesh <span class="caps">AT</span> gmail <span class="caps">DOT</span> com)</li>
<li>End of nomination period: March 31, 2023.</li>
</ul>
</li>
</ul>
</div>
<div class="section" id="cns-2023">
<h4><span class="caps">CNS</span> 2023<a class="headerlink" href="#cns-2023" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>Definitely do a social gathering</li>
<li>Defer decision on tutorial/workshops until next meeting so we have information on submissions/scheduling</li>
<li>Raise question of extra day/dedicated day for community development sessions (student/postdoc related, career, funding, <span class="caps">DEI</span>, general training that’s not specific to tools)</li>
<li><span class="caps">ACTION</span>: Ankur e-mail board to ask if there’s someplace we can feature the SoftwareWG</li>
<li><span class="caps">ACTION</span>: Ankur e-mail president to suggest Software <span class="caps">WG</span> be added to members meeting agenda</li>
</ul>
</div>
<div class="section" id="task-force-updates">
<h4>Task force updates<a class="headerlink" href="#task-force-updates" title="Permalink to this headline">⋆</a></h4>
<div class="section" id="simselect">
<h5>Simselect<a class="headerlink" href="#simselect" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li>working on <span class="caps">UI</span>, dockerised prototype</li>
<li><a class="reference external" href="https://fly.io/">https://fly.io/</a></li>
<li><a class="reference external" href="https://www.netlify.com/pricing/#features">https://www.netlify.com/pricing/#features</a></li>
<li><a class="reference external" href="https://www.heroku.com/pricing">https://www.heroku.com/pricing</a></li>
</ul>
</div>
<div class="section" id="cookbook">
<h5>Cookbook<a class="headerlink" href="#cookbook" title="Permalink to this headline">⋆</a></h5>
<ul class="simple">
<li><span class="caps">ACTION</span>: Ankur rename software development guidelines repo for cookbook: <a class="reference external" href="https://github.com/OCNS/SoftwareDevelopmentGuidelines">https://github.com/<span class="caps">OCNS</span>/SoftwareDevelopmentGuidelines</a></li>
<li><span class="caps">ACTION</span>: Ankur set up template and submission process</li>
</ul>
</div>
</div>
<div class="section" id="misc">
<h4>Misc<a class="headerlink" href="#misc" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li><span class="caps">INCF</span> neuroinformatics assembly: September 18-20 2023, online: <a class="reference external" href="https://neuroinformatics.incf.org/">https://neuroinformatics.incf.org/</a><ul>
<li>Call for workshops: <a class="reference external" href="https://www.incf.org/update/call-workshops-incf-neuroinformatics-assembly-2023">https://www.incf.org/update/call-workshops-incf-neuroinformatics-assembly-2023</a></li>
</ul>
</li>
<li>GSoC: <a class="reference external" href="https://neurostars.org/c/gsoc/5">https://neurostars.org/c/gsoc/5</a></li>
<li>Outreachy: <a class="reference external" href="https://www.outreachy.org/">https://www.outreachy.org/</a><ul>
<li>Open Science pot for academic/research projects</li>
</ul>
</li>
<li>Next meeting in 3rd week of April, on account of the Easter break</li>
</ul>
</div>
</div>
</div>
WG meeting 14 February 20232023-03-08T17:35:35+00:002023-03-08T17:35:35+00:00Ankur Sinhatag:ocns.github.io,2023-03-08:/SoftwareWG/2023/03/08/wg-meeting-14-february-2023.html<p class="first last">These are the minutes from the working group meeting on 14 February, 2023.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 14th February 2023.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in March</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<p>0800</p>
<ul class="simple">
<li>Shailesh Appukuttan</li>
<li>Ankur Sinha</li>
</ul>
<p>1700</p>
<ul class="simple">
<li>Ankur Sinha</li>
<li>Marcel Stimberg</li>
<li>Chitaranjan Mohaptra</li>
</ul>
</div>
<div class="section" id="agenda">
<h2>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h2>
<p><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/126">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/126</a></p>
<ul class="simple">
<li>plans for <span class="caps">CNS2023</span> (if any)<ul>
<li><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/125">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/125</a></li>
</ul>
</li>
<li>(Shailesh): about having a new co-chair to replace myself. I have been finding it difficult in recent months to devote much time to the admin activities of the group, and it would therefore be useful to have someone else step-up and help manage the <span class="caps">WG</span>. I will naturally continue to contribute as a member of the <span class="caps">WG</span>. Forming the task forces (for the two ongoing tasks) was a nice example of how some of the workload could be distributed and managed.</li>
<li>Code of Conduct<ul>
<li><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/123">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/123</a></li>
</ul>
</li>
<li>Task force updates</li>
</ul>
</div>
<div class="section" id="notes">
<h2>Notes<a class="headerlink" href="#notes" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li><span class="caps">CNS2023</span>: do not do satellite tutorials this year<ul>
<li>continue with dev sessions and software highlights</li>
<li>if/when possible, do more things of general interest<ul>
<li>reproducibility</li>
<li>model visualisation</li>
<li>etc.</li>
</ul>
</li>
<li><span class="caps">ACTION</span>: Ankur comment on ticket with updates (<span class="caps">DONE</span>)<ul>
<li>See: <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/125#issuecomment-1460539119">ticket</a></li>
</ul>
</li>
</ul>
</li>
<li><span class="caps">ACTION</span>: Ankur mention in notifications that we’re looking for a new co-chair<ul>
<li>if we do have lots of candidates, we can consider an election</li>
</ul>
</li>
<li>Code of Conduct:<ul>
<li>point to <span class="caps">OCNS</span> Code of Conduct</li>
<li>let co-chairs be in-charge of enforcement, with possibility of reaching out to externals when necessary</li>
<li><span class="caps">ACTION</span>: Ankur update website (<span class="caps">DONE</span>)</li>
</ul>
</li>
<li>Task force updates<ul>
<li>Simselect: lots of steady progress<ul>
<li>core team meets every two weeks</li>
<li>agreement on database/data description</li>
<li>consensus on general idea of what the resource needs to look like</li>
<li>at stage where prototyping is required to flesh out more details</li>
<li>more information on ticket: <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/117">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/117</a></li>
</ul>
</li>
<li>Guidelines task force<ul>
<li>no sense in writing another programming guide etc., which already exist in plenty</li>
<li>needs to be something that addresses a niche that the Software <span class="caps">WG</span> has expertise in</li>
<li>replace with something like an informal cookbook that includes useful tips/tricks/snippets that can be used in computational neuroscience<ul>
<li>See, for example: <a class="reference external" href="https://web.archive.org/web/20170227062636/http://neuralensemble.org/cookbook/">https://web.archive.org/web/20170227062636/http://neuralensemble.org/cookbook/</a></li>
</ul>
</li>
<li><span class="caps">ACTION</span>: Ankur comment on <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/116">ticket</a> suggesting we (<span class="caps">DONE</span>):<ul>
<li>add section on “guidelines” to the <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/resources.html">resources page on our website</a></li>
<li>close <a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/116">ticket</a></li>
<li>suggest “cook book” instead of guidelines</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
Software highlight: Kay Robbins: HED (Hierarchical Event Descriptors)2023-02-17T11:45:56+00:002023-02-17T11:45:56+00:00Ankur Sinhatag:ocns.github.io,2023-02-17:/SoftwareWG/2023/02/17/software-highlight-kay-robbins-hed.html<p class="first last"><a class="reference external" href="https://www.utsa.edu/sciences/computer-science/faculty/KayRobbins.html">Kay Robbins</a> will introduce and discuss <span class="caps">HED</span>, a practical system for describing an experiment using an analysis-ready framework.</p>
<p><a class="reference external" href="https://www.utsa.edu/sciences/computer-science/faculty/KayRobbins.html">Kay Robbins</a> will introduce and discuss <span class="caps">HED</span>, a practical system for describing an experiment using an analysis-ready framework.</p>
<ul class="simple">
<li>Zoom (<a class="reference external" href="https://ucl.zoom.us/rec/share/h-tszrMXevUhADQHl9CGwgP08ofJ77vmvFchUjrGZunm6MZB4F1txnUvuIXPAU2l.EiVd5lEKg7r-bh2M">recordings</a>)</li>
<li><a class="reference external" href="https://ocns.github.io/SoftwareWG/extras/other/INCF2023_SoftwareHighlightsFinal.pptx">Slides</a></li>
</ul>
<!--
</center>
<br />
<center>
<iframe width="560" height="315" style="height: 315px" src="https://www.youtube.com/embed/V3e_2OSfPsI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</center>
<br />
--><p>In human neuroimaging experiments, a record of what a participant experiences together with a clear understanding of the participant (task) intent are key to interpreting recorded brain dynamics.
<span class="caps">HED</span> (Hierarchical Event Descriptors, <a class="reference external" href="https://www.hedtags.org">https://www.hedtags.org</a>) annotations and supporting infrastructure can provide human-understandable machine-actionable descriptions of events experienced during laboratory and/or real-world time series recordings.
<span class="caps">HED</span>, which is well-integrated into <span class="caps">BIDS</span> (<a class="reference external" href="https://bids.neuroimaging.io/">Brain Imaging Data Structure</a>) has an ecosystem of tools supporting researchers at various stages including data acquisition, annotation, sharing, and analysis.
This talk will describe <span class="caps">HED</span> principles, focusing on basic representations of an experiment and its design.
Various tools in the <span class="caps">HED</span> ecosystem to support search, summary and analysis will be introduced and demonstrated.
Finally, we’ll discuss how tool developers can leverage the <span class="caps">HED</span> infrastructure to build advanced analysis tools capable of automated analysis in support of machine learning.
<span class="caps">HED</span> is an entirely open-source project, and the <span class="caps">HED</span> Working Group welcomes contributors and contributions.</p>
<p>Papers and resources:</p>
<ul class="simple">
<li>Capturing the nature of events and event context using Hierarchical Event Descriptors (<span class="caps">HED</span>). NeuroImage. <a class="reference external" href="https://www.sciencedirect.com/science/article/pii/S1053811921010387">Link</a>,</li>
<li>Building <span class="caps">FAIR</span> functionality: Annotating events in time series data using Hierarchical Event Descriptors (<span class="caps">HED</span>). Neuroinformatics. <a class="reference external" href="https://link.springer.com/article/10.1007/s12021-021-09537-4">Link</a>.</li>
<li>Resources: <a class="reference external" href="https://www.hed-resources.org">https://www.hed-resources.org</a></li>
<li>GitHub organization: <a class="reference external" href="https://github.com/hed-standard">https://github.com/hed-standard</a></li>
</ul>
WG meeting 16 January 20232023-02-01T10:30:55+00:002023-02-01T10:30:55+00:00Ankur Sinhatag:ocns.github.io,2023-02-01:/SoftwareWG/2023/02/01/wg-meeting-16-january-2023.html<p class="first last">These are the minutes from the working group meeting on 16 January, 2023.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 16th January 2023.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in February</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<p>1700</p>
<ul class="simple">
<li>Marcel Stimberg</li>
<li>Ankur Sinha</li>
<li>Chitaranjan Mahapatra</li>
</ul>
<p>Apologies:</p>
<ul class="simple">
<li>Shailesh Appukuttan</li>
</ul>
</div>
<div class="section" id="agenda">
<h2>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h2>
<p><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/120">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/120</a></p>
<ul class="simple">
<li>task force updates</li>
<li>ideas for sessions (dev sessions, hightlights etc.)</li>
<li>initial discussion on whether or not we want to host satellite tutorials along with (before?) <span class="caps">CNS</span>*2023 (the conference is in Leipzig from July 15-19)</li>
<li>tasks from last meeting (no pending tasks from last meeting)</li>
</ul>
<div class="section" id="task-force-updates">
<h3>Task force updates<a class="headerlink" href="#task-force-updates" title="Permalink to this headline">⋆</a></h3>
<div class="section" id="guidelines-task-force">
<h4>Guidelines task force<a class="headerlink" href="#guidelines-task-force" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>unsure of scope at the moment</li>
<li><span class="caps">ACTION</span>: Chitaranjan set up new doodle to plan next meeting: meeting in week starting 30 January to allow time for doodle filling</li>
</ul>
</div>
<div class="section" id="simulator-selection-resource">
<h4>Simulator selection resource<a class="headerlink" href="#simulator-selection-resource" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li>consolidated updates document: <a class="reference external" href="https://hackmd.io/LWjtz9ykQbm7yg5X_RKpCQ?view">https://hackmd.io/LWjtz9ykQbm7yg5X_RKpCQ?view</a></li>
<li>progress on scope</li>
<li>progress on inclusion criteria</li>
<li>progress on “front end” design</li>
<li>focus more on information useful to user/newcomer rather than technical information/criteria</li>
<li>regular meeting schedule: alternate Wednesdays on 14 <span class="caps">UTC</span>. Next meeting is 25th January at 1400 <span class="caps">UTC</span></li>
<li>4-5 regular task force members (more are always welcome!)</li>
</ul>
</div>
<div class="section" id="ideas-for-sessions">
<h4>Ideas for sessions<a class="headerlink" href="#ideas-for-sessions" title="Permalink to this headline">⋆</a></h4>
<ul class="simple">
<li><span class="caps">ACTION</span>: Ankur e-mail list asking for ideas</li>
<li><span class="caps">ACTION</span>: Marcel e-mail Dendrify devs about software hightlight/dev session and <span class="caps">CC</span> Ankur/Shailesh (<a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/93">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/93</a>) (<span class="caps">DONE</span>)</li>
</ul>
</div>
<div class="section" id="initial-discussion-on-satellite-tutorials-at-cns-2023">
<h4>Initial discussion on Satellite tutorials at <span class="caps">CNS</span> 2023<a class="headerlink" href="#initial-discussion-on-satellite-tutorials-at-cns-2023" title="Permalink to this headline">⋆</a></h4>
<p><a class="reference external" href="https://www.cnsorg.org/">https://www.cnsorg.org/</a></p>
<ul class="simple">
<li>2022: <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/software-wg-satellite-tutorials-at-cns-2022.html">https://ocns.github.io/SoftwareWG/pages/software-wg-satellite-tutorials-at-cns-2022.html</a></li>
<li>unsure if people are interested in live teaching sessions when they can go through documentation/videos/notebooks at their own pace when required</li>
<li>if we do a repeat of last year, we will charge a small registration fee to filter out people that are registering for meetings but not necessarily attending: it will be a small fee, that can be waived without requiring documentation (similar to Neuromatch conferences)</li>
<li>we will use something like <a class="reference external" href="https://sched.com">Sched</a> to ensure regular reminders are sent to registrants</li>
<li>we will ask either <span class="caps">INCF</span>/<span class="caps">OCNS</span> to fund us, and they get whatever registration fees are collected in return</li>
<li>alternatives<ul>
<li>software wg open day with a mix of user and dev focussed sessions, open to everyone to attend</li>
<li>short software highlights some time before the conference to give people an idea of the tools (and what to expect from tutorials at <span class="caps">CNS</span>): open to everyone</li>
<li>reproduction projects:<ul>
<li>tutors (tool devs) list some models that they would like reproduced in their simulators</li>
<li><span class="dquo">“</span>students” work with them to reproduce them</li>
<li>submit to rescience</li>
<li>Issue: probably not doable in a day, so if done, will be a longer term project requiring multiple meetings</li>
</ul>
</li>
</ul>
</li>
<li>internships
- usually require some buy in from institutions, so not easy to do</li>
<li><span class="caps">ACTION</span>: Ankur put all this in a GitHub issue for discussion</li>
<li><span class="caps">ACTION</span>: Ankur e-mail tutors from last year to see what they think and what they are ready to do</li>
</ul>
</div>
</div>
</div>
Software highlight: Michalis Pagkalos: Dendrify2023-01-27T11:01:32+00:002023-01-27T11:01:32+00:00Ankur Sinhatag:ocns.github.io,2023-01-27:/SoftwareWG/2023/01/27/dev-session-michalis-pagkalos-dendrify.html<p class="first last"><a class="reference external" href="https://dendrites.gr/?page_id=265">Michalis Pagkalos</a> will introduce and discuss <a class="reference external" href="https://github.com/Poirazi-Lab/dendrify">Dendrify</a>, a framework for incorporating dendrites to spiking neural networks, in this session.</p>
<p><a class="reference external" href="https://dendrites.gr/?page_id=265">Michalis Pagkalos</a> will introduce and discuss <a class="reference external" href="https://github.com/Poirazi-Lab/dendrify">Dendrify</a>, a framework for incorporating dendrites to spiking neural networks, in this session.</p>
<ul class="simple">
<li>Zoom (<a class="reference external" href="https://ucl.zoom.us/rec/share/tEgyFcXjPflMGLmSclnH5p-qKGyjJ_4IdRdxF70wJPiN_T6dZQtmLXxnvYbKn6L3.tzGYABjJOHer90o4">recordings</a>)</li>
</ul>
<!--
</center>
<br />
<center>
<iframe width="560" height="315" style="height: 315px" src="https://www.youtube.com/embed/V3e_2OSfPsI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</center>
<br />
--><p>The abstract for the talk is below:</p>
<p>Current SNNs studies frequently ignore dendrites, the thin membranous extensions of biological neurons that receive and preprocess nearly all synaptic inputs in the brain.
However, decades of experimental and theoretical research suggest that dendrites possess compelling computational capabilities that greatly influence neuronal and circuit functions.
Notably, standard point-neuron networks cannot adequately capture most hallmark dendritic properties.
Meanwhile, biophysically detailed neuron models can be suboptimal for practical applications due to their complexity, and high computational cost.
For this reason, we introduce Dendrify, a new theoretical framework combined with an open-source Python package (compatible with Brian2) that facilitates the development of bioinspired SNNs. Dendrify allows the creation of reduced compartmental neuron models with simplified yet biologically relevant dendritic and synaptic integrative properties.
Such models strike a good balance between flexibility, performance, and biological accuracy, allowing us to explore dendritic contributions to network-level functions while paving the way for developing more realistic neuromorphic systems.</p>
<ul class="simple">
<li>Manuscript: <a class="reference external" href="https://www.nature.com/articles/s41467-022-35747-8">Introducing the Dendrify framework for incorporating dendrites to spiking neural networks | Nature Communications</a></li>
<li>Source code: <a class="reference external" href="https://github.com/Poirazi-Lab/dendrify">Poirazi-Lab/dendrify: Introducing dendrites to spiking neural networks. Designed for the Brian 2 simulator.</a></li>
<li>Documentation: <a class="reference external" href="https://dendrify.readthedocs.io/en/latest/">https://dendrify.readthedocs.io/en/latest/</a></li>
</ul>
Dev session: Denis Alevi: Brian2CUDA2022-10-18T10:38:20+01:002022-10-18T10:38:20+01:00Ankur Sinhatag:ocns.github.io,2022-10-18:/SoftwareWG/2022/10/18/dev-session-denis-alevi-brian2cuda.html<p class="first last"><a class="reference external" href="https://www.sprekelerlab.org/denis/">Denis Alevi</a> will introduce the <a class="reference external" href="https://brian2cuda.readthedocs.io/en/latest/">Brian2CUDA</a> tool in this session, and discuss its development. We will also have a discussion on <span class="caps">GPU</span> based simulation in neuroscience after the presentation.</p>
<p><a class="reference external" href="https://www.sprekelerlab.org/denis/">Denis Alevi</a> will introduce the <a class="reference external" href="https://brian2cuda.readthedocs.io/en/latest/">Brian2CUDA</a> tool in this session, and discuss its development. We will also have a discussion on <span class="caps">GPU</span> based simulation in neuroscience after the presentation.</p>
<ul class="simple">
<li>Date: Thursday, November 3, 2022, 1600 <span class="caps">UTC</span> (Click <a class="reference external" href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=Dev+session%3A+Denis+Alevi+Brian2CUDA&iso=20221103T16&p1=136&ah=1">here</a> to see your local time).</li>
<li>Location (Zoom): <a class="reference external" href="https://ucl.zoom.us/j/95692778384?pwd=VldIQ3hPTU1zczNpYjQxSSt4Z25xdz09">Link</a> (Zoom login required)</li>
<li><a class="reference external" href="/extras/ics/20221103-dev-session-denis-alevi-brian2cuda.ics">Click here to download the calendar invite to add this meeting your calendar</a></li>
</ul>
<p>The abstract for the talk is below:</p>
<p>Graphics processing units (GPUs) are widely available and have been used with
great success to accelerate scientific computing in the last decade. These
advances, however, are often not available to researchers interested in
simulating spiking neural networks, but lacking the technical knowledge to
write the necessary low-level code. Writing low-level code is not necessary
when using the popular Brian simulator, which provides a framework to generate
efficient <span class="caps">CPU</span> code from high-level model definitions in Python. Here, we
present Brian2CUDA, an open-source software that extends the Brian simulator
with a <span class="caps">GPU</span> backend. Our implementation generates efficient code for the
numerical integration of neuronal states and for the propagation of synaptic
events on GPUs, making use of their massively parallel arithmetic capabilities.
We benchmark the performance improvements of our software for several model
types and find that it can accelerate simulations by up to three orders of
magnitude compared to Brian’s <span class="caps">CPU</span> backend. Currently, Brian2CUDA is the only
package that supports Brian’s full feature set on GPUs, including arbitrary
neuron and synapse models, plasticity rules, and heterogeneous delays. When
comparing its performance with Brian2GeNN, another <span class="caps">GPU</span>-based backend for the
Brian simulator with fewer features, we find that Brian2CUDA gives comparable
speedups, while being typically slower for small and faster for large networks.
By combining the flexibility of the Brian simulator with the simulation speed
of GPUs, Brian2CUDA enables researchers to efficiently simulate spiking neural
networks with minimal effort and thereby makes the advancements of <span class="caps">GPU</span>
computing available to a larger audience of neuroscientists.</p>
<p>References:</p>
<ul class="simple">
<li>Publication: <a class="reference external" href="https://www.frontiersin.org/articles/10.3389/fninf.2022.883700/abstract">Brian2CUDA: flexible and efficient simulation of spiking neural network models on GPUs (Frontiers in Neuroinformatics)</a></li>
<li>Documentation: <a class="reference external" href="https://brian2cuda.readthedocs.io/en/latest/">https://brian2cuda.readthedocs.io/en/latest/</a></li>
<li>Source code: <a class="reference external" href="https://github.com/brian-team/brian2cuda">https://github.com/brian-team/brian2cuda</a></li>
</ul>
WG meeting 10 October 20222022-10-17T12:02:04+01:002022-10-17T12:02:04+01:00Ankur Sinhatag:ocns.github.io,2022-10-17:/SoftwareWG/2022/10/17/wg-meeting-10-october-2022.html<p class="first last">These are the minutes from the working group meeting on 10 October, 2022.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 10th October, 2022.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in November</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<p>0800</p>
<ul class="simple">
<li>Ankur Sinha</li>
<li>Dinara Issagaliyeva (<span class="caps">INCF</span>/Charite)</li>
</ul>
<p>1700</p>
<ul class="simple">
<li>Katarzyna Piekarz</li>
<li>Marcel Stimberg</li>
<li>Ankur Sinha</li>
<li>Rahaf Albalkhi</li>
</ul>
</div>
<div class="section" id="agenda">
<h2>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h2>
<div class="section" id="tasks-from-last-meeting">
<h3>Tasks from last meeting<a class="headerlink" href="#tasks-from-last-meeting" title="Permalink to this headline">⋆</a></h3>
<p><a class="reference external" href="https://ocns.github.io/SoftwareWG/2022/09/27/wg-meeting-19-september-2022.html">https://ocns.github.io/SoftwareWG/2022/09/27/wg-meeting-19-september-2022.html</a></p>
<ul class="simple">
<li>Ankur send out e-mail to try and set up task forces for the two long running tasks: <span class="caps">DONE</span></li>
</ul>
</div>
<div class="section" id="setting-up-task-forces">
<h3>Setting up task forces<a class="headerlink" href="#setting-up-task-forces" title="Permalink to this headline">⋆</a></h3>
<ul class="simple">
<li>Wait for 2 weeks, till 23 October, for folks to join before initialising task forces</li>
<li>Once deadline has passed, task forces organise initial meeting to get started</li>
<li>Wait for responses before reaching out to more public channels</li>
<li><span class="caps">ACTION</span>: Ankur mention deadline in tickets/<span class="caps">ML</span></li>
<li><span class="caps">ACTION</span>: Ankur e-mail <span class="caps">OCNS</span> asking to e-mail membership about task forces if required</li>
<li>Software development guidelines<ul>
<li><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/116">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/116</a></li>
</ul>
</li>
<li>Resource to allow users to select simulator to use<ul>
<li><a class="reference external" href="https://github.com/OCNS/SoftwareWG/issues/117">https://github.com/<span class="caps">OCNS</span>/SoftwareWG/issues/117</a></li>
</ul>
</li>
</ul>
</div>
<div class="section" id="open-floor">
<h3>Open floor<a class="headerlink" href="#open-floor" title="Permalink to this headline">⋆</a></h3>
<ul class="simple">
<li><span class="caps">ACTION</span>: Ankur ping dev session/software highlight/tutorial tickets</li>
<li><span class="caps">HED</span> tools, Brian2CUDA in pipeline</li>
<li><span class="caps">OCNS</span> board election candidate period is open: strongly encourage folks from under-represented groups to self-nominate<ul>
<li><a class="reference external" href="https://www.cnsorg.org/board-of-directors">https://www.cnsorg.org/board-of-directors</a></li>
<li><a class="reference external" href="https://www.cnsorg.org/election-procedures">https://www.cnsorg.org/election-procedures</a></li>
<li>open to members: sign up for membership here: <a class="reference external" href="https://www.cnsorg.org/join-ocns">https://www.cnsorg.org/join-ocns</a></li>
</ul>
</li>
</ul>
</div>
</div>
WG meeting 19 September 20222022-09-27T11:00:24+01:002022-09-27T11:00:24+01:00Ankur Sinhatag:ocns.github.io,2022-09-27:/SoftwareWG/2022/09/27/wg-meeting-19-september-2022.html<p class="first last">These are the minutes from the working group meeting on 19 September, 2022.</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Daria Nepriakhina on Unsplash" class="img-responsive" src="https://ocns.github.io/SoftwareWG/images/20210107-meeting-logs.jpg" style="width: 40%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on Unsplash.</p>
</div>
</center>
<br /><p>These are the meeting logs (and additional progress notes) from the Software <span class="caps">WG</span> meeting that was held on 19th September, 2022.
The next progress meeting will be held <a class="reference external" href="https://ocns.github.io/SoftwareWG/pages/contact.html">in October</a>.
For any clarifications and suggestions, please open a new ticket.</p>
<div class="section" id="attendees">
<h2>Attendees<a class="headerlink" href="#attendees" title="Permalink to this headline">⋆</a></h2>
<p>0800</p>
<ul class="simple">
<li>Ankur Sinha (<span class="caps">UCL</span>/Open Source Brain/NeuroML)</li>
<li>Dinara Issagaliyeva (<span class="caps">INCF</span>/Charite Universitätsmedizin Berlin)</li>
<li>Malin Sandström (<span class="caps">INCF</span>)</li>
<li>Shailesh Appukuttan (<span class="caps">CNRS</span>/<span class="caps">EBRAINS</span>)</li>
<li>Chitaranjan Mahapatra (<span class="caps">CNRS</span>/<span class="caps">EBRAINS</span>)</li>
<li>Stewart Heitmann (Victor Chang Cardiac Research Institute)</li>
</ul>
<p>1700</p>
<ul class="simple">
<li>Ankur Sinha</li>
<li>Reema Gupta (<span class="caps">LMU</span>/In2PrimateBrains Consortium)</li>
</ul>
</div>
<div class="section" id="agenda">
<h2>Agenda<a class="headerlink" href="#agenda" title="Permalink to this headline">⋆</a></h2>
</div>
<div class="section" id="tasks-from-last-meeting">
<h2>Tasks from last meeting<a class="headerlink" href="#tasks-from-last-meeting" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li>No pending tasks from last meeting (or to be discussed in their own topics)</li>
</ul>
</div>
<div class="section" id="updates-from-cns-2022">
<h2>Updates from <span class="caps">CNS</span> 2022<a class="headerlink" href="#updates-from-cns-2022" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li>Stewart: software showcase very useful (only one showcase this year)</li>
<li>Showcases: excellent opportunity to quickly introduce tool to community</li>
<li>Lower turnout at Melbourne</li>
<li>Will be good to see how next year at Leipzig is attended</li>
<li>People seem to prefer learning in their own time rather than attend live tutorials—-also because we’re spending more time on documentation and improved video tutorials<ul>
<li>Try <a class="reference external" href="https://en.wikipedia.org/wiki/Flipped_classroom">flipped classroom format</a>?</li>
<li>pre-recorded videos/tutorials, and the live meting would then be to work interactively on something bigger/student projects etc.?</li>
<li>unclear how much work this would be to organize</li>
<li>standard tutorial not very useful if also already available as video</li>
</ul>
</li>
<li>Idea: include showcases in next year’s satellite tutorials (online)</li>
<li>Question: will <span class="caps">CNS2023</span> have an online component?</li>
</ul>
<div class="section" id="brief-update-from-the-ocns-board-meeting-malin">
<h3>Brief update from the <span class="caps">OCNS</span> Board Meeting (Malin)<a class="headerlink" href="#brief-update-from-the-ocns-board-meeting-malin" title="Permalink to this headline">⋆</a></h3>
<ul class="simple">
<li>discussed diversity</li>
<li>satellite tutorials were good to improve diversity</li>
<li>SIGs/WGs are good for diversity, equity, and inclusivity (<span class="caps">DEI</span>)</li>
<li>endorsement of tools<ul>
<li>good to do but the board doesn’t have the bandwidth to take this on</li>
<li>sensitive issue: must focus on positives</li>
<li>Software <span class="caps">WG</span> would be the logical place for endorsement; we have related tasks in the pipeline:<ul>
<li>guidelines (<span class="caps">WIP</span>): set of principles that everyone agrees on as required for a good tool</li>
<li>page on picking tools, which lists featured (<span class="caps">WIP</span>)</li>
</ul>
</li>
<li>software prizes?<ul>
<li>similar issues with not stepping on toes</li>
<li>could have many prizes in many different categories to cover lots of different software</li>
</ul>
</li>
<li>possible collaboration with <a class="reference external" href="https://www.pyopensci.org/blog/new-executive-director-leah-wasser">pyOpenSci</a>?</li>
</ul>
</li>
<li>best to set up a task force for longer <span class="caps">WG</span> activities that works intensively on the selected task (guidelines/form)<ul>
<li>incentives<ul>
<li><span class="caps">CV</span>: task forces are important volunteering/service opportunities</li>
<li>learning/participation experience</li>
<li>possible citation: could be published in the F1000 <span class="caps">INCF</span> journal or pre-print/Zenodo/etc.</li>
</ul>
</li>
</ul>
</li>
<li><span class="caps">ACTION</span>: Ankur send out e-mail to try and set up task forces for the two long running tasks</li>
<li><span class="caps">NOTE</span>: new guidelines/etc. must be kept up to date</li>
<li>Also ask wider community for task force contributions</li>
<li>Make <span class="caps">DEI</span> regular event at <span class="caps">OCNS</span> conference: Board positive response<ul>
<li>have a community development component at each annual conference<ul>
<li><span class="caps">DEI</span></li>
<li>student/post-doc development</li>
<li>software showcases</li>
<li>grant applications</li>
<li>software best-practices</li>
</ul>
</li>
<li>larger discussion that needs to be held at Board level</li>
</ul>
</li>
</ul>
</div>
</div>
<div class="section" id="updates-from-incf-assembly">
<h2>Updates from <span class="caps">INCF</span> assembly<a class="headerlink" href="#updates-from-incf-assembly" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li>videos publicly available before end of the year<ul>
<li><span class="caps">DEI</span> sessions to be publicised widely</li>
</ul>
</li>
<li>need more time for <span class="caps">DEI</span> discussion</li>
<li>good session for start</li>
<li>lots of good points (but overlapping also)</li>
<li>Gather: limitation: cannot directly record, had to use specific tool</li>
<li>Ask <span class="caps">INCF</span> if possible to prevent clash with Bernstein/other conferences</li>
</ul>
</div>
<div class="section" id="satellite-tutorials-feedback-form">
<h2>Satellite tutorials feedback form<a class="headerlink" href="#satellite-tutorials-feedback-form" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li>small data set</li>
<li>people seem to be happy to pay a small amount<ul>
<li>have waiver in place similar to NeuroMatch conference</li>
<li>organization that funds the platforms will receive the registration fees</li>
</ul>
</li>
<li>find sponsors to reduce the token registration fee?<ul>
<li><span class="caps">WG</span> unlikely to have bandwidth to look for sponsors</li>
<li>will need to lean on <span class="caps">OCNS</span>/<span class="caps">INCF</span> sponsors (<span class="caps">OCNS</span> has a sponsorship chair on the board)</li>
</ul>
</li>
<li>see how much <span class="caps">INCF</span> ended up paying for the platforms at the Assembly (Malin will see if this info is available)</li>
<li>registration fee important to get better idea of actual attendance numbers.</li>
</ul>
</div>
<div class="section" id="other">
<h2>Other<a class="headerlink" href="#other" title="Permalink to this headline">⋆</a></h2>
<ul class="simple">
<li><a class="reference external" href="https://www.nitrc.org/">https://www.nitrc.org/</a> -> add to resources</li>
<li>Guidelines: add use-cases as examples</li>
</ul>
</div>