Description
In some cases, it is beneficial to use kernel sizes that are different for each dimension (e.g. when the data is anisotropic). Same goes with stride. Currently, AutoencoderKL does not allow the user to input the kernel size; the latter is hard-coded, same as the stride.
Describe the solution you'd like
It would be useful for users to be able to input a kernel size and stride per level, if desired. This could be an int (same for all the network), a list (different for each level) or a list of lists (if the kernel size differs for each dimension). This would have to leave out the last and first layers. Padding would have to be automatically derived to ensure that things run without errors (e.g.: since there are skip-connections, there needs to be an assurance that the input and output to conv. layers are not getting inadvertently downsized or upsized).