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

Update interface for control kernel code #3

Open
bcdaniels opened this issue Dec 6, 2023 · 0 comments
Open

Update interface for control kernel code #3

bcdaniels opened this issue Dec 6, 2023 · 0 comments

Comments

@bcdaniels
Copy link
Member

Code for computing control kernels currently lives in controlkernel.modularity.attractors using the find_control_kernel argument. It would make more sense for this to be integrated into neet's other computations for attractors. So we might run something like

atts = net.attractors()
cks = net.control_kernels(attractors=atts)

where the attractors argument might optionally take the known list of attractors to save time.

The issue is that the (exact) control kernel code relies on a different (modular) method for computing attractors as compared to the original neet code. So we might need to switch to using modular code to compute attractors in neet, or at least have it as an option.

If we change the interface for computing control kernels, we would need to change at least the functions in controlkernel/control_kernel_analysis.py.

Note also that we have "sampled" versions of attractor and control kernel calculations in modularity—it would be nice to integrate these in a nice way, too, e.g.

atts = net.attractors(sampled=True)
cks = net.control_kernels(attractors=atts,sampled=True)
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