-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix bug in computation aware latency #96
base: main
Are you sure you want to change the base?
Conversation
Fixed a bug where non-ca latency (e.g. AL) and ca latency (e.g. AL_CA) results are consistent when using --computation-aware.
Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
latency_scorers[name] = get_scorer_class("latency", name).from_args(args) | ||
latency_args=deepcopy(args) | ||
latency_args.computation_aware=False | ||
latency_scorers[name] = get_scorer_class("latency", name).from_args(latency_args) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this line always setting latency_args.computation_aware
as false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this line is for creating non-ca latency, so computation_aware should be set to False. Line 290 is used to determine whether ca latency needs to be created based on the incoming parameters (--computation-aware).
We have tested it on simultaneous text-to-text speech-to-text and speech-to-text tasks, and can partially solve the bug when using --computation-aware.
Hi @zhangshaolei1998 thank you so much for the PR and sorry for the late response. |
Fixed a bug where non-ca latency (e.g. AL) and ca latency (e.g. AL_CA) results are consistent when using --computation-aware.