Parsing transmission issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 28/100
Research direction
Start by reading io._parse_transmission around line 791 and inspect how it handles the two transmission-value naming examples. Reproduce the case of a nexus file with no transmission values, then confirm the intended completed behavior for that input before adding coverage and verifying the parser handles it.
Written by the indexing model from the issue text.
Description
Current format of io._parse_transmission on line 791 does not account for nexus files which are missing any transmission values. Only has two examples of naming instances for where to find the transmission value
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100