Replies: 2 comments
-
All the transforms are customized transforms, more like a usage issue, so move it into discussions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
BTW, instead of using your customized transforms, I would suggest you using the existing transforms from the repo. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I am training a model for image segmentation. Using a custom transform pipeline, I found that clearing the background using a ratio with a Gaussian blurred image and histogram equalisation helps model convergence. However, when I used Monai compose to do the same, I ran into the issue that the transforms of one image seemed to affect other images. This is how I write the
Compose
:And these are the individual compose:
Note that the
ComposeInspect
is there for debugging purposes. With this code, what I see is something like:Which is odd, because it seems that the transformations on one image, also happen on other image and then the values seems to accumulate and get out of hand.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would like the transformations to be calculated everytime de novo or to be calculated once and not to accumulate spilling over other images.
Environment
Ensuring you use the relevant python executable, please paste the output of:
Additional context
Not required
Any help will be more than welcome.
Beta Was this translation helpful? Give feedback.
All reactions