Rename P300 to ERP
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 264
- Avg merge
- 1d 13m
- Merged PRs (30d)
- 23
Description
Minor annoyance, but currently the default ERP paradigm is called "P300", which may be a well-known ERP component, but is not necessarily the dominant one when it comes to classification between Target / Non-Target, especially in fast visual paradigms.
There are two options to deal with this:
- Make P300 and ERP synonymous via aliases etc.
- Replace usages of P300 with ERP. This would require advance deprecation warning etc. and could be a larger change in the code base.
I would be okay with either option.
Contributor guide
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
The issue does not name files or tests; start by searching the repository for the default P300 paradigm and every user-facing usage. Determine whether compatibility aliases or a deprecation-and-rename path is appropriate, then verify that the default is presented as ERP without breaking existing P300 references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100