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

Expose multiplexing through AssignmentData #19

Open
kernfel opened this issue Aug 19, 2020 · 0 comments
Open

Expose multiplexing through AssignmentData #19

kernfel opened this issue Aug 19, 2020 · 0 comments
Assignees

Comments

@kernfel
Copy link
Member

kernfel commented Aug 19, 2020

Currently, assigning conductance instances to particular channel combinations, particularly in the case of model prototype channels, is handled during clamp setup by implementation-specific ConductanceProxy::instantiate(). As a result, the UI is blind to multiplexing and can't present multiplexed conductances e.g. for plotting. Furthermore, while multiplexed conductances can be data-saved and are indexed with unique multiplex_ids, no information is exposed about the relationship between multiplex_id and model instances.

It would be preferable for multiplexing to be a function of AssignmentData and its descendants. While this admittedly muddles the separation of data and functionality, it would open multiplexing to UI access, as well as provide a convenient and logical place to add information about instantiated (multiplexed) assignments. Besides, this facility could be used to provide finer-grained control over multiplexing without overburdening implementations of ConductanceProxy::instantiate.

@kernfel kernfel self-assigned this Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant