-
Notifications
You must be signed in to change notification settings - Fork 1
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
Consider integration with ioos checker plugin #44
Comments
Note that it would be nice to have you all at the code sprint for other topics unrelated to ugrid. Hopefully the remove alternative will make it easier to attend. However, it would be awesome to have you for the in person event. |
@ocefpaf thanks Noticing in
Maybe we could present on Geovista / PyVista ? (
proper docs in the pipeline, but bjlittle did just promise to slightly improve it -- ?? didn't you @bjlittle ?!? |
P.S.
@trexfeathers suggests this from the Iris docs : https://scitools-iris.readthedocs.io/en/v3.2.1/further_topics/ugrid/partner_packages.html#geovista |
The "main" event is focused on Software discussion/hacking but there will be lightning talks and I believe geovista is definitely worth mentioning in one of them. |
If there's still space, then we could inject a lightning talk on GeoVista, as you suggest. |
I believe there is. Did you all register for it? Are you in touch with @MathewBiddle? |
Actually no, I wasn't sure who to approach. Regarding possible use of the ugrid-checks codeI have already created a proof-of-concept solution (incomplete, and not yet visible here) to provide checking results in a suitable form for inclusion in an IOOS-style Report object. |
Folks are discussing that today and tomorrow during the compliance-checker sprint. If you reach out to Matt he will send you the URLs you need to connect. It is be zoom for discussion and slack for async/pasting text. |
See https://github.com/ioos/cc-plugin-ugrid
@ocefpaf suggests a code sprint : ioos/ioos-code-sprint#6
Potentially, this would be April 25 - 28, 2022
The text was updated successfully, but these errors were encountered: