MeasureTransport / MeasureTransport/MParT
Create a testing suite for GPU
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
This is going to be a slog unfortunately, but we need to do something about testing. Ideally we would have tests for
PythonJuliaMatlab- GPU
- GPU/Bindings
Julia is basically set up (in fact it tests in its own repository), and Python will be "easy" once we have a test running script for it, and Matlab might be easy (see here), but the latter two will not. I know how we can make GPU tests at a high-level (we take a machine in ACDL, self-host an actions runner, connect it to github), but it will inevitably take a good chunk of time to actually implement it in practice. If we do figure that out, then we could also always self-host a runner for the MATLAB tests if the GitHub-hosted runners are giving us trouble.
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
No files, tests, or entry points are named. Start by reviewing the proposed ACDL self-hosted GitHub Actions runner approach and define how GPU and GPU/bindings tests should run. Done means a working GPU testing suite is integrated and executes reliably in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100