parsecsp fails to read uncompressed data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 82
- Forks
- 21
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
I have a device that stores uncompressed data in section 6 (4500 samples in 9000 bytes). Parsescp fails to parse such files, as it tries to unconditionally apply Huffman decompression algorithm. This results in errors such as this:
Warning: 63006 extra bits in lead 0
I have no patch because I have no access to the spec, and do not know how to check if compression was used or not.
(could someone give me a pointer to the spec?)
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 at the parsecsp parsing path and investigate how section 6 is identified as compressed. Use the reported 4,500 samples in 9,000 bytes as the reproduction case; done means uncompressed data is parsed without the Huffman warning while compressed input continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100