NatLabRockies / NatLabRockies/PRAS
Disallow creating systems where lambda and mu are simultaneously zero
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 76
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
When lambda = mu = 0, long-run availability is undefined, which causes problems both for calculating convolutions as well as for initializing the system state in SequentialMonteCarlo. Resource constructors should include a check that at least one of the two values is nonzero at all times.
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 locating the resource constructors and the SequentialMonteCarlo system-state initialization mentioned in the issue. Trace how lambda and mu are validated before availability or convolutions are calculated, then add coverage showing that both-zero values are rejected while valid nonzero combinations remain accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100