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

Determine how the min/max value for each variable should be obtained #42

Open
sebastien-lenard opened this issue Nov 1, 2023 · 2 comments

Comments

@sebastien-lenard
Copy link
Collaborator

The planned implementation of the min/max value for each variable is to determine these values for each root region. However, this min/max values won't be updated for the subdivisions of the root region, which can have different range of values, for instance if the root region includes mountains and the subdivisions only plains.

This task is to decide that this working is ok (or not) for Karl.

@sebastien-lenard
Copy link
Collaborator Author

sebastien-lenard commented Nov 1, 2023

I realized that this has much more implication for the user experience. It can be confusing for him that if he change of regions, the variable legend colormap range value changes too. This definitely asks for clarification by Karl before implementing this feature.

A simple solution (to implement on the supercomputer side) would be first to have different, fixed, range values for north and south hemisphere, and for start and end of the season. This would make 4 range values per variable.

The range of values will be sent in the root region file.

This also implies that there would be different legends per variable per region. This point is to clarify on the way we want it to work on the web-app side.

@mfisher87
Copy link
Member

This also implies that there would be different legends per variable per region

Currently, the ingest code generates each legend, one per super-region/variable combination, based on the config using Matplotlib.

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

No branches or pull requests

2 participants