kinetic schemes are not initialised to steady state
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 11
- Avg merge
- 8h 6m
- Merged PRs (30d)
- 1
Description
Just for the record - especially because it conflicts with generated neuron code, which accounts for initialisation correctly.
The effect is clearly seen in a default NeuroML2 example.
Acknowledged in a TODO comment.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the TODO in src/main/java/org/lemsml/jlems/core/run/KSchemeInst.java and reproduce the effect using the linked NeuroML2 example, LEMS_NML2_Ex4a_KS.xml. Compare the initialization behavior with generated neuron code, which the issue says handles initialization correctly. Done means kinetic schemes begin in steady state for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100