You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different users have different priorities for how the scaling should look like. The scales should therefore be easily changeable (e.g. via the aeroval config file)
Describe the solution you would like to see
make the scales an optional part of the aeroval config file
Additional context
color bars are used at the contours:
The same values are also used here:
The text was updated successfully, but these errors were encountered:
In addition, default color-maps should be defined by frequency, i.e. a range of 0-80 of hourly PM is fine, while it should be rather 0-35 for daily averages and 0-20 (or even less) for yearly averages.
In addition, default color-maps should be defined by frequency, i.e. a range of 0-80 of hourly PM is fine, while it should be rather 0-35 for daily averages and 0-20 (or even less) for yearly averages.
Is your feature request related to a problem? Please describe.
The clour scales are right now defined globally here:
pyaerocom/pyaerocom/aeroval/glob_defaults.py
Lines 2 to 10 in 26df81b
Different users have different priorities for how the scaling should look like. The scales should therefore be easily changeable (e.g. via the aeroval config file)
Describe the solution you would like to see
make the scales an optional part of the aeroval config file
Additional context
color bars are used at the contours:
The same values are also used here:
The text was updated successfully, but these errors were encountered: