I started the task of implementing BatchNormalization in rcudnn last night and a thought occurred to me. Might it be easier to auto generate all of the ParamaterNotSupported error strings by parsing them per function from the cuDNN API reference pdf?
Whoops I meant “CUDNN_STATUS_BAD_PARAM”
Technically yes, but I think the effort required to impl such a tool would be very high compared to doing 10 to 100 manual error strings
Hi @drahnr, I’m about halfway through the process you laid out for implementing BatchNormalization in juice but have become stuck with regard to implementing the ‘descriptor’ step. It seems like the non-LRN/non-divisive normalization cuDNN functions are quite different in their usage API than functions like LRN and Activation functions. Despite spending a solid half an hour reading the cuDNN API reference trying to decipher the correct way to implement this in juice I’m quite confused and stuck. Can we arrange to have a synchronous chat in the next few days so I can hopefully figure this out and proceed with implementing this set of cuDNN functions in juice? Cheers :)
Sure, how about Friday or Saturday?
Preferably in the evening hours
Could create a draft PR upfront with your current changes?