MetaCell / MetaCell/PsyNeuLinkViewSource
Define entry points for the debug running mode
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
provide tech spec of where the debugger entry point(s) should be placed in psyneulink, as per last call the Report class provides an enter and exit method that we could leverage since they already have the entire context.
The source of truth for the data to be plotted will always and only be the log/text file so that we keep consistency between the normal running simulation mode and the debug one.
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 by reviewing the Report class and its existing enter and exit methods, then trace how the normal running simulation produces the log/text file. Define where debug-mode entry points belong and how they use that context while keeping the log/text file as the sole plotting source. Done means an agreed technical specification, but the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100