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
When we forked this repo and made a few more flexible changes, there was a missed change. NOTE: This is not a breaking code issue. It is more of an inconsistency.
I am specifically referencing the kernel_size changes we made. The original package by Kyle didn't let you change the convolutional kernel size from the top level method (e.g., models.unet(...)). This made for a limited hyperparameter search for many using unets. Thus, if you go back into the history of the pulls here you will see how we passed the kernel_size paramater up to the top level method.
When we forked this repo and made a few more flexible changes, there was a missed change. NOTE: This is not a breaking code issue. It is more of an inconsistency.
I am specifically referencing the
kernel_size
changes we made. The original package by Kyle didn't let you change the convolutional kernel size from the top level method (e.g.,models.unet(...)
). This made for a limited hyperparameter search for many using unets. Thus, if you go back into the history of the pulls here you will see how we passed thekernel_size
paramater up to the top level method.The issue opened here arises from the changes. Unfortunately, it looks like
kernel_size
was not passed into the output layer of the 3+ unets. The code issue is here, which is from https://github.com/dopplerchase/keras-unet-collection/blob/main/keras_unet_collection/_model_unet_3plus_2d.pyIt is possible that this hard coded kernel with size 3 is in other places, but I have not checked elsewhere yet.
The text was updated successfully, but these errors were encountered: