Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Define entry points for the debug running mode

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
tooling

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.

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.

Dominant language
JavaScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 MetaCell/PsyNeuLinkViewSource

All issues in MetaCell/PsyNeuLinkViewSource

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.