-
Notifications
You must be signed in to change notification settings - Fork 85
Lightning integration #991
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
base: master
Are you sure you want to change the base?
Conversation
- basic primitves for lightning port
Port lightning corrected
Co-authored-by: Sarthak Pati <[email protected]>
Co-authored-by: Sarthak Pati <[email protected]>
Co-authored-by: Sarthak Pati <[email protected]>
Co-authored-by: Sarthak Pati <[email protected]>
Co-authored-by: Sarthak Pati <[email protected]>
Co-authored-by: Sarthak Pati <[email protected]>
Co-authored-by: Sarthak Pati <[email protected]>
- added calculation of overall metrics - added proper handling of data formats for both progress bar logging and gandlf custom logging - added tests for regression and classification - little refactoring of tests
Forward pass lightning - training pipeline
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
This comment was marked as outdated.
This comment was marked as outdated.
No idea where it came from, had to just downsize the patch size. It is caused during evaluation of efficient net, and not always
@benmalef can you help us with the code covergae? I think it is mostly related to the files that are no logner used and some lines in new code. Can you take a look? |
Yes, of course. I will take a look. 😁 |
# Conflicts: # .spelling/.spelling/expect.txt # GANDLF/config_manager.py # testing/test_full.py
Update lighting integration branch
Fixes #
Proposed Changes
Checklist
CONTRIBUTING
guide has been followed.typing
is used to provide type hints, including and not limited to usingOptional
if a variable has a pre-defined value).pip install
step is needed for PR to be functional), please ensure it is reflected in all the files that control the CI, namely: python-test.yml, and all docker files [1,2,3].logging
library is being used and noprint
statements are left.