Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize population and connection indexing/labeling #21

Open
pausz opened this issue Aug 14, 2015 · 0 comments
Open

Generalize population and connection indexing/labeling #21

pausz opened this issue Aug 14, 2015 · 0 comments

Comments

@pausz
Copy link
Contributor

pausz commented Aug 14, 2015

From @RomeshA

There should be a way to name populations and give them a single
letter subscript, which would then enable us to refer to populations
with labels like 'e','r','s', and to connections like 'ee','ei'...
rather than population 1, couple 3. This would also make it easier to
compare similar components when the model is changing and thus the
indexes might change.

I could imagine a solution using something like Python dictionaries to have key:value pairs, where the key would be 'ee', 'ei' for connections and 'e', 'i'. I think numeric indexing is more general, so labels are mainly a human readable decoration. Maybe we can generate a mapping between the two?

Apparently the equivalent dictionary structure in C++ is called std::map. However, I've never used it.

@pausz pausz modified the milestones: Mark I, Mark II Aug 14, 2015
@pausz pausz removed this from the Mark II milestone Mar 9, 2017
@stuart-knock stuart-knock added this to the Backlog milestone Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants