It can be confusing to have separate recipes for stash codes and field name filtering.
Describe the solution you'd like
Input stash codes in the same way as variable names. That way we can have one input list. The constraint generation can decide to generate a stash constraint if it starts with "m01s??i???", otherwise a variable name constraint.
Then we can work on adding a conversion between UM field names and LFRic field names.
The variable name constraint should probably be upgraded with this capability, while the STASH constraint should be deprecated.
Describe alternatives you've considered
While we could entirely drop STASH code support, they are well known for current users of the UM, and some UM fields don't have meaningful names otherwise.
What problem does your feature request solve?
It can be confusing to have separate recipes for stash codes and field name filtering.
Describe the solution you'd like
Input stash codes in the same way as variable names. That way we can have one input list. The constraint generation can decide to generate a stash constraint if it starts with "m01s??i???", otherwise a variable name constraint.
Then we can work on adding a conversion between UM field names and LFRic field names.
The variable name constraint should probably be upgraded with this capability, while the STASH constraint should be deprecated.
Describe alternatives you've considered
While we could entirely drop STASH code support, they are well known for current users of the UM, and some UM fields don't have meaningful names otherwise.