You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on the Brian2Lava project as part of the INRC. In order for our pipeline to work as intended it would be optimal if the @tag for all NcProcessModels was consistent. Instead, in some cases the tag is 'ucoded' (in the case of LIF) while in some others it is 'ucode' (in the case of Dense).
Having a consistent tag would make our life easier since we wouldn't have to rely on:
class names, since in principle users can define their own custom classes
case by case parsing of the tag for every single type of Process we are trying to support.
The text was updated successfully, but these errors were encountered:
Thank you for raising this issue. This house keeping is of course necessary, but probably not of immediate priority from our side. If you would like to change it, feel free to submit a PR :)
User story
I am working on the Brian2Lava project as part of the INRC. In order for our pipeline to work as intended it would be optimal if the
@tag
for all NcProcessModels was consistent. Instead, in some cases the tag is 'ucoded' (in the case of LIF) while in some others it is 'ucode' (in the case of Dense).Having a consistent tag would make our life easier since we wouldn't have to rely on:
The text was updated successfully, but these errors were encountered: