Skip to content
This repository was archived by the owner on Jul 1, 2023. It is now read-only.

Fix tests. #130

Merged
merged 2 commits into from
May 23, 2019
Merged

Fix tests. #130

merged 2 commits into from
May 23, 2019

Conversation

dan-zheng
Copy link
Member

WIP, one remaining test to fix: testUpSampling3D.

dan-zheng added 2 commits May 22, 2019 15:08
UpSampling3D is not trivially fixable. Filed TF-525.
@dan-zheng dan-zheng requested review from rxwei and pschuh May 23, 2019 00:26
@dan-zheng dan-zheng merged commit d398718 into master May 23, 2019
@dan-zheng dan-zheng deleted the fix-tests branch May 23, 2019 00:36
@Shashi456
Copy link
Contributor

@dan-zheng is there no simple fix for this? Doesn't that mean upsampling 3d doesn't work effectively?

@dan-zheng
Copy link
Member Author

There's no trivial fix, unfortunately. Please see TF-525 for more info, including a crash reproducer and a link to Keras's implementation. We can copy Keras to avoid the unsupported broadcasting error.

@Shashi456
Copy link
Contributor

Shashi456 commented May 23, 2019

@dan-zheng so for using resize-volumes, would we have to write a vjp again? I see that the keras implementation uses resize_volumes, which again uses repeat elements, It might not be hard to fix, just looking at a way to do it properly.

@dan-zheng
Copy link
Member Author

@dan-zheng so for using resize-volumes, would we have to write a vjp again? I see that the keras implementation uses resize_volumes, which again uses repeat elements, It might not be hard to fix, just looking at a way to do it properly.

Yes, it will be necessary to define some kind of "repeat elements" helper function that is differentiable.
Are you interested in taking this on? Let me share a quick prototype with you soon.

@Shashi456
Copy link
Contributor

Shashi456 commented May 23, 2019

@dan-zheng yes I would be willing to, but I'm not accustomed to writing vjps for custom functions so that might act as some kind of bottleneck for me there. Still, have a lot more to learn.

Also i personally believe we should comment out Upsampling3d from layer.swift as well. No point keeping it open, when the functionality isn't available. Should i put a PR in for that? Might be quicker for you though.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants