Constants
Open
Nobody has claimed this yet.
discussion
help wanted
question
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
singularity-opac has a constants and unit systems infrastructure. singularity-eos does not. These are inconsistent and also should ideally be shared. I wonder if this infrastructure should in fact live in ports-of-call?
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
Compare the constants and unit-systems infrastructure in singularity-opac with what is present in singularity-eos. Then evaluate whether the shared infrastructure belongs in ports-of-call. Done should mean the project has a decided location and consistent, shared constants and unit systems, but the issue does not identify files or tests to start from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100