Current versus Time graph poorly designed in "Current in a Wire"
Nobody has claimed this yet.
- Dominant language
- NetLogo
- Stars
- 125
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
If one changes the voltage it takes a very long time for the graph to react appropriately. That is because it is plotting charge-flow / ticks and charge_flow only increases with time so it is plotting the average since the beginning of the run.
If it just plots charge-flow and after the call to tick one inserts set charge-flow 0 then the graph responds immediately. And one sees that the current measurement is noisy which seems appropriate in this model.
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
Open the "Current in a Wire" model and run it while changing the voltage to observe the Current versus Time graph. Inspect how the graph uses charge-flow around tick and verify that the completed behavior responds promptly to voltage changes and shows the expected current signal.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100