Fix typos in get_next_train_batch and get_next_eval_batch in auto_unit #916
Conversation
The old comments have "PredictUnit" in `get_next_train_batch`, `get_next_eval_batch`, which could be a copy-pasta typo from `get_next_predict_batch`. The new comments change from "PredictUnit" to "TrainUnit" in `get_next_train_batch` and "EvalUnit" in `get_next_eval_batch`
|
Hi @iamyifan! 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! |
In
torchtnt.framework.auto_unit.py,The old comments have "PredictUnit" in
get_next_train_batchandget_next_eval_batch, which could be a copy-pasta typo fromget_next_predict_batch.The new comments change from "PredictUnit" to "TrainUnit" in
get_next_train_batchand "EvalUnit" inget_next_eval_batch.