How to reference gap junctions in the configuration file
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start with simulator_network.py at load_gap_junc_files, called by PointNetwork.from_config, and inspect the configured gap_juncs files alongside the HDF5 error for the missing source_ids object. Confirm the expected gap-junction file structure and configuration entry points, then verify that loading the supplied files completes without the KeyError.
Written by the indexing model from the issue text.
Description
Hello,
I want to create a network of gap junctions and simulate it using the PointNet simulator, but I'm not sure how to reference the gap junctions in the configuration file.
I have created gap junction connections as follows:
net_pre.import_nodes(nodes_file_name=path_pre_h5,node_types_file_name=path_pre_csv)
net_post.import_nodes(nodes_file_name=path_post_h5,node_types_file_name=path_post_csv)
net_pre.add_gap_junctions(source=net_pre.nodes(pop_name='PV'), target=net_post.nodes(pop_name='SST'), connection_rule=connection_rule,resistance=1250)
net_pre.build()
net_pre.save_edge('network')
Then I referenced these gap junctions in the configuration file as follows:
"networks": {
"nodes": [
{
"nodes_file": "$NETWORK_DIR/test_net_nodes.h5",
"node_types_file": "$NETWORK_DIR/test_net_node_types.csv"
}
],
"edges": [],
"gap_juncs": [
{
"gap_juncs_file":"$NETWORK_DIR/test_net_test_net_edges.h5",
"gap_juncs_types_file":"$NETWORK_DIR/test_net_test_net_edge_types.csv"
}
]
However, I am getting this error:
Traceback (most recent call last):
File "/home/margaux/miniconda3/envs/ENV_NEST/config_command_run_pointnet.py", line 20, in <module>
main(sys.argv)
File "/home/margaux/miniconda3/envs/ENV_NEST/config_command_run_pointnet.py", line 15, in main
network = pointnet.PointNetwork.from_config(configure)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/margaux/miniconda3/envs/ENV_NEST/lib/python3.11/site-packages/bmtk/simulator/core/simulator_network.py", line 260, in from_config
network.load_gap_junc_files(config.gap_juncs)
File "/home/margaux/miniconda3/envs/ENV_NEST/lib/python3.11/site-packages/bmtk/simulator/core/simulator_network.py", line 192, in load_gap_junc_files
self._gap_juncs[network][key] = f[key][()]
~^^^^^
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "/home/margaux/miniconda3/envs/ENV_NEST/lib/python3.11/site-packages/h5py/_hl/group.py", line 357, in __getitem__
oid = h5o.open(self.id, self._e(name), lapl=self._lapl)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5o.pyx", line 190, in h5py.h5o.open
KeyError: "Unable to open object (object 'source_ids' doesn't exist)"
Thank you for your help!
Margaux
- Dominant language
- Python
- Stars
- 339
- Forks
- 103
- Avg merge
- 2h 7m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AllenInstitute/bmtk
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllenInstitute/bmtk#468 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
AllenInstitute/bmtk#337 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
AllenInstitute/bmtk#326 ·
Maintainers usually reply within 1 day
-
tau_syn_basis and weight coefficients for TF synapsesMay be free again @shixnya claimed this 133 days ago, and no pull request is open. Open
AllenInstitute/bmtk#463 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
AllenInstitute/bmtk#457 ·
Maintainers usually reply within 1 day
All issues in AllenInstitute/bmtk
Similar issues
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Official-Space-AI/OpenPhysGraspGen#114 ·
Maintainers usually reply within 2 days
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ramnes/notion-sdk-py#441 ·
-
qa_bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA-NeMo/Gym#5644 ·
Maintainers usually reply within 2 days
-
BUG: catalog database credentials printed to logs at startupPossibly taken @cjboyle claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day