As a Data Scientist using PySyft's IntTensor type, I want to leverage a wide range of methods which use our new Unity backend. For this ticket to be complete, the add() should be added to our IntTensor class with the appropriate functionality, returning a new tensor.
Note, it is possible that when you look in the code you'll find that parts of this issue were completed on the backend while implementing another issue. This is par for the course as features do not live in isolation. If this is the case, just take it as a convenience that someone already built that part and press on!
And of course, please consider our Contributor Guidelines for all contributions.
[ ] comment below that you're interested in picking up this issue
While the title says to implement in the IntTensor class, description says add() should be added to our FloatTensor class! I think it is in IntTensor in both cases. Please correct me if I am wrong.
@dikshant2210 you are right! sorry about that. it is intTensor in both the cases.
I'll pick this one up
Going to start with the PySyft interface and the CPU code
Sweet! Once you've got the interface setup, I'll add the GPU side. Feel free to just add an if statement that returns "NotImplementException" if dataOnGpu==True and I'll insert my GPU code there (wherever you'd like it).
Perfect. Works for me!
Hey @gavinuhma , what branch are you working on so that I can collaborate with you?
Hey @iamtrask I'm working from int_add, I started a pull request as a work in progress:
https://github.com/OpenMined/OpenMined/pull/319
Hey @gavinuhma , in https://github.com/OpenMined/OpenMined/pull/322 I uncovered a potential bug in how our shader is initialized which I will report in another bug issue. This implementation does pass your first unit test with a temporary workaround.
Great find @iamtrask ! We're almost done!
Most helpful comment
Hey @gavinuhma , in https://github.com/OpenMined/OpenMined/pull/322 I uncovered a potential bug in how our shader is initialized which I will report in another bug issue. This implementation does pass your first unit test with a temporary workaround.