Hi folks,
I was thinking about dropping the comp-neuro spin for the next Fedora release. The different tools we provide are quite easy to install individually, and we also have the dnf package group for simulation software if someone does want to install the simulation tools all at once.
The tools are all computational neuroscience related, but they are different enough (different levels of modelling, for example) that a user probably won't use them all together. For example, someone simulating point neurons will tend to use NEST or Brian, but not NEURON/NetPyNE. On the other hand, someone simulating multi-compartmental cells will tend to use NEURON/NetPyNE and not NEST/Brian. I think people are more likely to install their preferred Fedora variant (Gnome/KDE/whatever) and then install the individual packages on top of that. That's sort of what I do too.
So, I think it'll be better to document how to create containers/remixes etc. using our packages so that people can create custom environments for themselves rather than providing a spin.
As an extension, I was also thinking of writing up use cases for the neuro-sig to help us focus our efforts and deliverables. I'll open a separate ticket for that.
Thoughts?
OK, based on the discussion we've had on the channels, we'll go ahead with this. Tasks:
Metadata Update from @ankursinha: - Issue assigned to ankursinha
Related: are we able to add a searchable package list somewhere, similar to the search function included in the licensing docs for the license list?
Log in to comment on this ticket.