MetOffice / MetOffice/lfric_core
JediBones : An example
- Dominant language
- Fortran
- Stars
- 26
- Forks
- 73
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
### Core PoC Branch
https://github.com/mo-rickywong/lfric_core/tree/Jedi_Two_Cfg_Example
### Brief description
**JediBones**
* Based on LFRic Core Skeleton app.
* Takes two configuration namelists from command line
* Added to Rose-Stem test suite so that 2 configuration files are created before calling program.
* Example uses base Rose-Metadata from skeleton along with local Rose metadata as specified by JediBones. Rose metadata could be imported from other sources. Crucially only one "superset" of rose-meta.conf is generated (for the configurator) to work.
* ClI modified, though is a temporary hack
**NOTE:** The branch is a Proof of Concept (PoC) and not for commit to trunk. Whatever app is used for Jedi, it should be on the the LFRic_apps repo
### Further details of the issue.
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Jedi_Two_Cfg_Example branch and compare it with the LFRic Core Skeleton app. Read how the Rose-Stem test suite creates the two configuration files and how the temporary CLI change passes them to the program. Done means defining whether JediBones belongs in lfric_core or LFRic_apps and replacing the PoC with an accepted implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100