New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

For ds2, we should not involve padding data when computing loss and gradient #414

Closed

4 tasks done

pkuyym opened this issue Nov 2, 2017 · 0 comments

Closed

4 tasks done

For ds2, we should not involve padding data when computing loss and gradient #414

pkuyym opened this issue Nov 2, 2017 · 0 comments

Contributor

pkuyym commented Nov 2, 2017 •

edited by kuke

Loading

To solve the problem, two things should be done.

Expose SubSequenceLayer (including bug fixes) Bug fix for SubSequnceLayer Paddle#5335
Add a ScaleSubRegionLayer (support set value for given indices) Add ScaleSubRegion Layer. Paddle#5416
Modify the network configuration. Support padding removing. #444
Adapt tune.py Adapt tuning script to padding removing #444 #447

pkuyym closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment