User feedback: Sodium leakage channel, Na-K pump.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start by locating the neuron simulation code that models sodium leak currents and the Na-K pump. Compare its resting-potential behavior with the issue description; done means the model accounts for sodium leakage and Na-K pump activity at rest.
Written by the indexing model from the issue text.
Description
I really like your App PheT. But for the stimulation of a Neuron there is a little mistake in it. Unfortunately in real there are no sodium-Channels, which are permanently opened. That would prevent the resting potential. Of course there are leak currents of sodium. Thus the Na-K Pump is even at the resting potential necessary. This Pump doeśnt appear in your App. Would it be possible, to improve this parts?
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 phetsims/neuron
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
type:user-feedback
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
dev:typescript priority:5-deferred
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
status:blocks-sim-publication
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
saadeghi/daisyui#4780 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
accessibility bug embed websites
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quarto-dev/quarto-cli#14972 ·
Maintainers usually reply within 1 day
-
has-readme needs-attention new-tool repo-verified
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
shanselman/TinyToolTown#834 · 2 comments ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
siderolabs/talos-design-system#16 ·
Maintainers usually reply within 1 day