OPS TODO Task List
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 77
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Task List for OPS Release
- OPS Move code generated APPS to OPS-APPS repo - automatically regenerate code for changes in OP2-Common repo
- Add AMD HIP tests to CI test flow
Task list for next Release
- OPS build with SPACK recipies / config
- Upgrade/Update OPS code generator to use OP-CG codegen ideas - see https://github.com/jdjfisher/op-cg
- Add SYCL Parallelization to OPS repo
- OPS Fortran API develop - more applications, updated code generator (in line with C/C++ API/build)
- Test / Add to CI tests the Tridsolver integration testing on non-intel CPUs
- Add to readthedocs documentation - Dev-Docs and other missing sections
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 reviewing the two unchecked tasks in the issue: the OPS build with SPACK recipes/config and Tridsolver integration testing on non-Intel CPUs. Identify the relevant build and CI entry points, then consider the work done when both tasks are implemented and verified in the project’s release workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100