Add updates from NOAA-EMC/fire_behavior to NCAR/fire_behavior
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 11
- Forks
- 17
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 1
Description
A few changes were added to NOAA-EMC/fire_behavior that have never been brought back into NCAR/fire_behavior, despite that being the intention. Here is the diff between NOAA-EMC and NCAR (develop..emc/develop).
When the WM upgrades to spack-stack v2.1.x, an additional small change will be incorporated into NOAA-EMC/fire_behavior that may then need to come into the NCAR repo: https://github.com/NOAA-EMC/fire_behavior/pull/6 .
I'm not sure what the preferred method is, but perhaps when the spack-stack upgrade happens, I can PR to develop with all of the changes at once?
@mkavulich Thoughts?
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 with the linked develop...emc/develop comparison between NCAR/fire_behavior and NOAA-EMC/fire_behavior, then review NOAA-EMC/fire_behavior pull request #6 and the planned spack-stack v2.1.x upgrade. Done means the intended NOAA-EMC changes are incorporated into NCAR/fire_behavior's develop branch after the upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100