-
Notifications
You must be signed in to change notification settings - Fork 5
Update notebooks #77
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
base: main
Are you sure you want to change the base?
Update notebooks #77
Conversation
|
Big thanks for cleaning up and polishing the notebooks! 👏 👏 👏 I only had a brief look. Things look already pretty good. The only thing I would definitely change is the colormap. Not because I do not like viridis, but in the dark regions one cannot see the gauge and CML locations. Also the contrast of viridis is not optimal. With turbo more details are visible. But of course, the choice of colormap is a bit personal taste... |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #77 +/- ##
=======================================
Coverage 95.37% 95.37%
=======================================
Files 11 11
Lines 800 800
=======================================
Hits 763 763
Misses 37 37 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@cchwala I find the poligrain plotting functions very nice, but for plotting several figures in one row with one shared colorbar using I also changed the colormap, better now? The introduction notebook could maybe need some short review. Note that I will keep working on these notebooks while doing parallel work on the OpenMRG2 notebooks. So should we wait with merging? |
I assume you mean the part of plotting the maps with
The hexbin plotting function from poligrain is indeed a bit restrictive and not very adjustable.
I just had a brief look because I am too busy now to go into the details. Overall it looks good, maybe a bit long for an introduction. You can leave it as it is since it gives a nice overview. If you want to spend time on this, you could rename it to "overview" and start a very short notebook that just shows the basic concept for doing the merging using only one method, just to make clear how things are applied. But this is not a priority now IMO.
Yes, let's wait with merging. |
W.I.P
Closes #58 and #75.
This PR updates the notebooks according to suggestions in #58. It also adds a introduction notebook where we show more detailed how mergeplg works.