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.

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

Merge fixes for IFS output #26

Closed
lkluft opened this issue Nov 1, 2023 · 3 comments
Closed

Merge fixes for IFS output #26

lkluft opened this issue Nov 1, 2023 · 3 comments

Comments

@lkluft
Copy link
Contributor

lkluft commented Nov 1, 2023

During the preparation of the NextGEMS hackathon several fixes for IFS output have been tested that didn't find there way back to gribscan, yet. Some of these fixes seem to be useful for other use cases as well.

@lkluft
Copy link
Contributor Author

lkluft commented Feb 6, 2024

As far as I can tell, some of the recent changes (basic regular_ll support, additional timeRangeIndicators) might close this issue.

@trackow is there still some raw cycle 3 output available so I could test this?

@trackow
Copy link
Contributor

trackow commented Feb 6, 2024

Yes, our FDB for Cycle 3 is here: /work/bm1235/a270046/cycle3/multio_cycle3/fdb.dir.multio/

In there you find different streams. Would be good to test it for an example file from all of those streams, at least for the bold ones to test across different grids and frequencies:

rd:hzfy:lwda:20200120:0000:g (hourly, native high res grid)
rd:hzfy:monr:20200115:0000:g (monthly means, native high res grid)

rd:hzfy:msda:g (monthly, regular grid)
rd:hzfy:mdfa:g (monthly, regular grid)

rd:hzfy:scda:20200120:0000:g (hourly, regular grid)
rd:hzfy:dcda:20200120:0000:g (hourly, regular grid)

rd:hzfy:lwwv:20200120:0000:g (wave model output)

@lkluft
Copy link
Contributor Author

lkluft commented Feb 6, 2024

I tested gribscan-index on random files from each of the highlighted directories. I was able to always create indices without crashes and also create datasets using gribscan-build -m ifs. In my opinion, we can close this issue and see how far we come during the preparation of the next hackathon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants