-
Notifications
You must be signed in to change notification settings - Fork 240
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.
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
[Good First Issue] [NNCF] Make NNCF common accuracy aware training code pass mypy checks #2492
Comments
.take |
Thank you for looking into this issue! Please let us know if you have any questions or require any help. |
@vshampor missed this!! will wait for the next one!! thanks for informing!! |
@tvilight4 I have created #2491 now, take a look. |
@vshampor thanks!! got assinged for it. |
Hello @tvilight4, are you still working on that issue or can we reassign it? |
@vshampor could you please either link the PR to the development section of the issue or grant me some permissions in NNCF repo to do this myself? I'd prefer the latter since I'm keeping an eye on all GFIs weekly. |
@p-wysocki Is this issue being actively worked on? If not, I'm down to work on it! |
Sure, thank you very much! I have already started working on it. |
Hi @p-wysocki, what is the update regarding the assignment? I was off for some time due to my dissertation submission. I am resuming work on this issue now. |
Done, please let us know if you have any questions @anzr299. :) |
Sure, I am following the current types that are mentioned in some files. For arguments with kwargs and args, I am planning on using "...", is that fine? |
I found some good tips here, I think you can pick one you'd like to use and it's going to be fine - worst case scenario we'll change it. |
Also, I was wondering if the the |
@p-wysocki @vshampor I've created a PR #2637 |
## Changes: mypy checks for accuracy_aware_training pass. type: ignore is used in some places due to one of the following reasons: 1. Using Generic type causes a mismatch between some instances and their assignments which causes mypy to throw an error. Bounding does not solve the problem either. 2. Other issues related to the use of TypeVar such as bounding OptimizerType, LRSchedulerType, and TensorboardWriterType. 3. Error related to named arguments not being defined in `self._train_epoch_fn` 4. attribute not available Extra Changes: 1. The argument type and return type of `configure_accuracy_aware_paths` were changed to include pathlib.Path. 2. **kwargs was removed from abstract method `initialize_training_loop_fns` due to mypy bug regarding a mismatch of the function type. ## Reasons for changes: Passing mypy checks in issue #2492 ## Related tickets: Closes #2492
This is exactly like #2495 (see the description and tasks there), but the target code path for this one is nncf/common/accuracy_aware_training instead of nncf/common/graph.
The text was updated successfully, but these errors were encountered: