error: no suitable constructor exists to convert from "c10::ScalarType" to "at::Type"
See original GitHub issueI encounter this error when executing
python setup.py build develop
det3d/ops/sigmoid_focal_loss/src/sigmoid_focal_loss_cuda.cu(121): error: no suitable constructor exists to convert from “c10::ScalarType” to “at::Type”
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
C++ no suitable constructor exists to convert from
Here is our assignment operator and our standard overloaded constructor, but Visual studio gives us a weird error: Error 2 error LNK2019: ...
Read more >error #415: no suitable constructor exists to convert from 'const...
IBM Rational Test RealTime 8.0.1 delivers an attolcc4 and atostart4 based on EDG 4.7 parser. USE_ATTOLCC4 must be set in the TDP basic...
Read more >"no suitable constructor exists to convert from" error when i'm ...
I made LPFEED class and I declared pFeed by it. And it is the data of the m_FeedMap(cocos2d::Map Container).
Read more >IntelliSense: no suitable constructor exists to convert from "std ...
The program should first prompt the user to input the data for each monkey, starting with "Sunday" for monkey #1, then monkeys #2...
Read more >int2 i = 0; // error: no suitable constructor ? - CUDA ...
int2 i = 0; // error: no suitable constructor exists to convert from “int” to “uint2” (I can only guess that this is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If you are using pytorch 1.0, you will face this error(same as me). there is some api changed between torch 1.0 and 1.3 check this part in the sigmoid_focal_loss_cuda.cu file
@muzi2045 Thanks. Updating torch solves this problem.