Switch to new specification (N+1) and improve testing coverage
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4
- Forks
- 10
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
This is a roadmap for what is coming after a meeting with @anibalsolon.
To help development I will generate more exotic .TRX (un/compressed, small/large, with single/overlapping/no points, mismatched dpv&dps, etc).
- Test
examples/load_trx.cpp - Run benchmark on V1 of Figshare
- Change the code to support the N+1 offsets change both at load & save
- Run benchmark on V2 of Figshare
- Explore which Unit Tests could be useful (same as trx-python?)
- Deploy C++ Unit Tests on GitHub
- Autorun benchmark on GitHub (maybe using a command in PR?)
- Add a bit of detail to the
README.md
@arokem had links in #1 for C++ and CI
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 with examples/load_trx.cpp and review the completed N+1 load/save change before examining the linked Figshare V1 and V2 benchmark data. The remaining roadmap covers testing, benchmarks, GitHub automation, and README.md updates; done means the unchecked checklist items have been completed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, documentation, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100