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
Colormaps are converted internally and renamed. This caused a bug in #82 but is recently fixed in main. The issue can be seen from
importultraplotaspltforname, cmapinplt.colormaps.items():
print(f"{cmap.name=}{name=}")
# prints for example cmap.name='_BR_copy' name='br'
The name of the colormaps if correct, and hence all the functions work correctly. I have the intuition by integration mpl's colormaps and ultraplot's colormaps that this renaming is performed to avoid potential naming collision. I believe this would be unnecessary and is rather confusing.
The relevant code can be found in colors.py
def_make_name(self, suffix=None):
""" Generate a default colormap name. Do not append more than one leading underscore or more than one identical suffix. """name=self.namename=nameor""ifname[:1] !="_":
name="_"+namesuffix=suffixor"copy"suffix="_"+suffixifname[-len(suffix) :] !=suffix:
name=name+suffixreturnname
The text was updated successfully, but these errors were encountered:
For the user this may never cause an issue unless the explicit cmap.name is used. I don't really know why the maps are internally converted to this plus the suffix, but I think it should be removed.
Colormaps are converted internally and renamed. This caused a bug in #82 but is recently fixed in main. The issue can be seen from
The name of the colormaps if correct, and hence all the functions work correctly. I have the intuition by integration mpl's colormaps and ultraplot's colormaps that this renaming is performed to avoid potential naming collision. I believe this would be unnecessary and is rather confusing.
The relevant code can be found in
colors.py
The text was updated successfully, but these errors were encountered: