Merging with brian2tools
Closed this issue · 6 comments
Shouldn't we close brian2modelfitting and merge with brian2tools? (see wiki)
It's possible that installation of brian2modelfitting might be more complicated than the other things in brian2tools if it uses the GPU as before, so maybe it would be better to keep them separate?
I think the idea here was to port over the full functionality of the modelfitting toolbox which would justify a full repository of its own I think. In particular because it would be based on code generation and therefore need tests on various architectures and so on while I'd prefer brian2tools to stay Python-only.
But then, we could remove this repository until someone is actually working on this...
I see. Well it was created in 2014 and hasn't changed since then...
I wrote some code for model fitting to traces (not spike trains) that
has basic functionality. It's a branch of brian2tools (which doesn't
appear on github so I guess I didn't properly push it). It would be nice
to be able to use standalone mode but currently not possible (see note
on brian2tools wiki).
Le 18/05/2016 à 16:38, Marcel Stimberg a écrit :
I think the idea here was to port over the full functionality of the
modelfitting toolbox which would justify a full repository of its own
I think. In particular because it would be based on code generation
and therefore need tests on various architectures and so on while I'd
prefer |brian2tools| to stay Python-only.
But then, we could remove this repository until someone is actually
working on this...—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1 (comment)
I see. Well it was created in 2014 and hasn't changed since then...
Yes, we created a few of these placeholder repositories (same for brian2hears) a while ago... Their advantage is that the readme states where to look for the Brian 1 version, but maybe their presence is more confusing than not having them in the first place...
It's a branch of brian2tools (which doesn't appear on github so I guess I didn't properly push it).
On older versions of PyCharm you had to explicitly tick a checkbox next to the branch name when you wanted to push a new branch -- if you did not do it, it silently did not push anything... Happened to me more than once :-)
Would it be useful to have a brian2wip work in progress repository for things like this where we haven't quite worked out how we'll package it and release it etc.?
Closing this very old issue, for now we have decided to keep brian2modelfitting as a separate package.