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

Set consistent colour ranges on plot_maps_dashboard() #21

Open
byersiiasa opened this issue Jul 10, 2024 · 2 comments · May be fixed by #22
Open

Set consistent colour ranges on plot_maps_dashboard() #21

byersiiasa opened this issue Jul 10, 2024 · 2 comments · May be fixed by #22
Assignees

Comments

@byersiiasa
Copy link
Member

There are two modes for this function

  1. one scenario, multiple indicators
  2. one indicator, multiple scenarios

If #2, it is showing the same indicator for multiple IAM scenarios. In this case the colour range, vmin, vmax etc for cmap should be the same for each plot.
@mwerning - can you investigate if this can be done in hvplot? Presumably Dan had done this before

@byersiiasa
Copy link
Member Author

Can be tested using the files in here:
https://iiasahub.sharepoint.com/:f:/r/sites/eceprog/Shared%20Documents/Research%20Theme%20-%20NEXUS/RIME_GEO/[rime_output_maps](https://iiasahub.sharepoint.com/:f:/r/sites/eceprog/Shared%20Documents/Research%20Theme%20-%20NEXUS/RIME_GEO/rime_output_maps?csf=1&web=1&e=VQNReN)?csf=1&web=1&e=VQNReN

something a bit like the below

from rime.rime_functions import *

ind = 'hw_99_5'
ftype = 'diff'
filename = f"{output_folder_maps}maps_multiscenario_{ind}_{ftype}.nc"
maps = xr.open_dataset(filename)
year =  2050
filename = f"{wd_GEO}/rime_output_maps/dashboard_{ind}_{ftype}_{year}.html"
plot_maps_dashboard(
    maps.sel(variable=temp_variable),
    filename=filename,
    year=year,
    cmap="magma_r",
    shared_axes=True,
    clim=None,
)

There seems even to be clim in the input arguments to the function but it was never implemented.

@mwerning mwerning linked a pull request Jul 12, 2024 that will close this issue
@mwerning
Copy link
Collaborator

Please see pull request. Happy to discuss options for improving the current implementation.

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

Successfully merging a pull request may close this issue.

2 participants