-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
A suggestion about palette. #1150
Comments
maybe the same question~ |
aravind-h-v
pushed a commit
to aravind-h-v/mmsegmentation
that referenced
this issue
Mar 27, 2023
…n-mmlab#1150) * StableDiffusion: Decode latents separately to run larger batches * Move VAE sliced decode under enable_vae_sliced_decode and vae.enable_sliced_decode * Rename sliced_decode to slicing * fix whitespace * fix quality check and repository consistency * VAE slicing tests and documentation * API doc hooks for VAE slicing * reformat vae slicing tests * Skip VAE slicing for one-image batches * Documentation tweaks for VAE slicing Co-authored-by: Ilmari Heikkinen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I read the implementation of the palette function, I find a personal dataset with CLASSES defined but PALETTE being None will skip generating a random palette because the
get_classes_and_palette
returns atmmsegmentation/mmseg/datasets/custom.py
Lines 308 to 311 in 520ec8e
The
get_palette_for_custom_classes
which containing random palette generation will not execute.As a result, a random palette will be generated in each iteration of testing at
mmsegmentation/mmseg/models/segmentors/base.py
Lines 246 to 252 in 520ec8e
The colors of classes are different in each iteration.
The text was updated successfully, but these errors were encountered: