Regarding to my previous issue #19 , I find it is a bug in libtorch 1.0.1 and the bug disappears when using libtorch 1.2.0 in my little demo.
Do you have any plan to migrate the code to libtorch 1.2.0? Currently the code can't compile using libtorch-1.2.0 due to the API changes.
I'll work on this anyway, and I'm willing to submit a PR in the future. Just wonder do you have any work in progress so we can prevent some redundant work.
Regarding to my previous issue #19 , I find it is a bug in libtorch 1.0.1 and the bug disappears when using libtorch 1.2.0 in my little demo.
Do you have any plan to migrate the code to libtorch 1.2.0? Currently the code can't compile using libtorch-1.2.0 due to the API changes.
I'll work on this anyway, and I'm willing to submit a PR in the future. Just wonder do you have any work in progress so we can prevent some redundant work.