Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce an alternative GRIB1 loading using iris_grib.message.GribMessage instead #489

Open
Tracked by #56
trexfeathers opened this issue Jun 18, 2024 · 0 comments
Open
Tracked by #56

Introduce an alternative GRIB1 loading using iris_grib.message.GribMessage instead #489

trexfeathers opened this issue Jun 18, 2024 · 0 comments
Labels
Dragon Sub-Task 🦎 https://github.com/orgs/SciTools/projects/19?pane=info

Comments

@trexfeathers
Copy link
Contributor

trexfeathers commented Jun 18, 2024 •
edited
Loading

Some notes are in #56

Contract: the tests introduced in #488 must always pass

This new behaviour should NOT be activated at this stage

The philosophy is that the loading behaviour will be switchable - choose between legacy and new behaviour - so musn't just replace the existing code.
@trexfeathers trexfeathers mentioned this issue Jun 18, 2024
Open
@trexfeathers trexfeathers added the Dragon Sub-Task 🦎 https://github.com/orgs/SciTools/projects/19?pane=info label Jun 18, 2024
@trexfeathers trexfeathers changed the title Rewrite grib1 loading using iris_grib.message.GribMessage instead Rewrite GRIB1 loading using iris_grib.message.GribMessage instead Jun 18, 2024
@trexfeathers trexfeathers changed the title Rewrite GRIB1 loading using iris_grib.message.GribMessage instead Introduce an alternative GRIB1 loading using iris_grib.message.GribMessage instead Jun 18, 2024
@trexfeathers trexfeathers mentioned this issue Jun 18, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Dragon Sub-Task 🦎 https://github.com/orgs/SciTools/projects/19?pane=info
Projects
🚴 Peloton
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@trexfeathers