bad chrom: 100
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 207
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
## /home/chaofan/software/EIG/bin/convertf version: 5000
warning (mapfile): bad chrom: 100 100_1047 0 1047
warning (mapfile): bad chrom: 100 100_1106 0 1106
warning (mapfile): bad chrom: 100 100_1221 0 1221
warning (mapfile): bad chrom: 100 100_1265 0 1265
warning (mapfile): bad chrom: 100 100_1752 0 1752
warning (mapfile): bad chrom: 100 100_10008 0 10008
warning (mapfile): bad chrom: 100 100_10054 0 10054
warning (mapfile): bad chrom: 100 100_10135 0 10135
warning (mapfile): bad chrom: 100 100_10201 0 10201
warning (mapfile): bad chrom: 100 100_12772 0 12772
Segmentation fault (core dumped)
Hi! @MatthewMah
How to fix this error?
Thank you for your reply!
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 reproducing the reported convertf version 5000 run using the map data that contains chromosome 100 entries. Investigate how convertf handles the repeated “bad chrom” warnings and the subsequent segmentation fault. Done means the input is handled without a crash, with clear behavior for unsupported chromosome values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- bioinformatics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100