Skip to content
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

support pytorch2.0 #500

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

support pytorch2.0 #500

wants to merge 4 commits into from

Conversation

RangiLyu
Copy link
Owner

No description provided.

@codecov
Copy link

codecov bot commented Mar 21, 2023

Codecov Report

Merging #500 (4d85d0c) into main (d3fb34f) will increase coverage by 0.79%.
The diff coverage is 73.21%.

@@            Coverage Diff             @@
##             main     #500      +/-   ##
==========================================
+ Coverage   74.84%   75.63%   +0.79%     
==========================================
  Files          71       71              
  Lines        4691     4663      -28     
  Branches      728      726       -2     
==========================================
+ Hits         3511     3527      +16     
+ Misses        983      940      -43     
+ Partials      197      196       -1     
Flag Coverage Δ
unittests 75.63% <73.21%> (+0.79%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
nanodet/data/collate.py 100.00% <ø> (+46.51%) ⬆️
nanodet/model/arch/one_stage_detector.py 55.81% <0.00%> (-4.19%) ⬇️
nanodet/trainer/task.py 71.18% <82.00%> (+15.95%) ⬆️

... and 4 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@cansik
Copy link
Contributor

cansik commented Dec 31, 2023

@RangiLyu Thanks for the port to pytorch2.0. I just tested it on MacOS and it seems that MPS backend is currently not working. Also, the CPU inference seems to be broken, because the devices argument of the pl.Trainer has to be set to the amount of CPUs that can be used (instead of None).

Do you already know when you are going to merge this into main?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants