Regression harness fails due to non-initialized variables; timing mismatch; namelist parameters are missing
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 11
- Forks
- 17
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 1
Description
The current source code does not allow creating the test harness and a candidate baseline test result. The following
independent problems make the results scientifically unsuitable as references:
- several output fields contain values from uninitialized Fortran arrays;
- the fuel-strip and observed-perimeter cases never ignite because the first
model advance starts at 4 s and misses their ignition windows; - observed-perimeter data are installed after propagation has already begun;
- atmospheric fields written at an output time contain the preceding forcing
record; - the OpenMP-4 test receives only one computational tile;
- required namelist values are missing from either input or MPI broadcast.
The harness must also require evidence of fire propagation before candidate
validation can pass. Without that check, initializing the affected arrays
would remove the current MPI comparison failure while still allowing two inert
fire cases to become baselines.
The file describe the 8 issues:
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 reading CFBM-RegressionTests-PreBaseline-Issues-v1.md and CFBM-RegressionTests-PreBaseline-Technical-Findings-v1.md, then trace the Fortran regression harness, candidate validation, and namelist/MPI setup described there. Done means all eight listed problems are resolved, fire propagation is required before validation, and a scientifically valid candidate baseline can be created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- hpc, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100