MetOffice / MetOffice/fab

Next Fab Release

Open
#593 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
9
Forks
9
Avg merge
12d 12h
Merged PRs (30d)
2

Description

Here the list of issues to be fixed/PRs to be merged for the next release (and reason why I added them):
- #588/#592
Required for MONC, and ideally allows us to update all build scripts to replace the deprecated `grab_folder` with `grab_files`.
- #567/#584
Adds transmute support for LFRic_atm
- #590/#591
Adds support for application-specific flags (which can add/overwrite site-specific flags). Required for lfric_atm (to e.g. add UM-specific flags)
- #594
This adds the capability to Fab script to do checkout only, or build only (from a single script). This is a requirement for platforms where e.g. the compute nodes do not have internet access (so the checkouts run on a small set of nodes with internet connection, but the build then on a larger compute node to allow parallel builds). #595
- #596/#597
Being able to properly define preprocessing flags in the preprocessor makes compiler-specific options cleaner to handle (used in Jules, which adds its own compiler defined, e.g. GNU_FORTRAN, INTEL_FORTRAN etc)
- #589
While not urgent, fixing the documentation would be good so we don't document a feature that does not exist. Plus if we should decide to add nf_config to Fab, it can be removed from MONC.
- #582
UKMO to decide if this is important and provide a PR.
- #566
UKMO to decide if this is needed.
- #599 / #601
Improvements to compilation profiles.
- #563
Add DependencyInfo class to Fab (currently used in LFRic and UM)

Update this ticket as more issues are identified. I also can't seem to add a milestone we could use to tag tickets/PRs.

Contributor guide

Open the contributing guide

Research direction

Review the referenced issues (#588, #592, #567, #584, and the other listed tickets) to understand the proposed fixes and their release dependencies. Start by checking which items are ready to merge and which still require decisions or pull requests. Done means the release work is resolved, the ticket is updated with any newly identified issues, and a milestone or equivalent release marker is established if available.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.