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

Case study: replace Compat.Vector with python data type #23

Open
WeinaJi opened this issue Jan 30, 2025 · 0 comments
Open

Case study: replace Compat.Vector with python data type #23

WeinaJi opened this issue Jan 30, 2025 · 0 comments
Labels
good first issue Good for newcomers

Comments

@WeinaJi
Copy link
Collaborator

WeinaJi commented Jan 30, 2025

Compat types (https://github.com/openbraininstitute/neurodamus/blob/main/neurodamus/utils/compat.py) were designed to behavior similar to Hoc objects. It was necessary at the time when neurodamus needed to parse the legacy config file (BlueConfig parsed by a hoc parser) as well as the SONATA config file. Now with the only SONATA case, is it possible to replace them with python types?

When I tried to replace Compat.Map in #18, I notice that it is the input of the hoc function inteprete() in RNGSetting.hoc which requires a hoc Map. And Compat.List is required by ConnectionUtils.hoc.

This task is to study whether Compat.Vector can be simply replaced by a Python type, array, list or numpy array. Or is it used in a hoc function?

@WeinaJi WeinaJi added the good first issue Good for newcomers label Jan 30, 2025
@cattabiani cattabiani mentioned this issue Feb 5, 2025
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant