Tutorial 1 step 3

Open
#208 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reproducing Tutorial 1 step 3 with Python 3.8.5, NEURON 8.0.0, and the commands involving components/mechanisms and modfiles. Check why nrnivmodl does not produce sim_ch01/config.simulation.json; done means the documented step completes and the tutorial can proceed.

Written by the indexing model from the issue text.

Description

I encountered the highlighted issue about compiling NEURON mechanisms. There is by default no mechanisms folder by default in components, and after creating one and trying the suggested fix 'nrnivmodl modfiles' from /.../mechanisms, it fails. Creating a modfiles folder lets'nrnivmodl modfiles' run, but the sim_ch01/config.simulation.json file does not get created and I cannot move past step 3.

For reference I am using Python 3.8.5, neuron 8.0.0.

I would assume that there is trouble with the path for neuron like the warning suggests in step 3, but I can import neuron in Jupyter. Does bmtk need to be downloaded in a certain location? If I knew what mechanisms were required, could I manually make the folder and then run nrnivmodl modfiles (or does that line normally populate the folder)?

Dominant language
Python
Stars
339
Forks
103
Avg merge
2h 7m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AllenInstitute/bmtk

All issues in AllenInstitute/bmtk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.