Yuchen Yang

I met the same errror like @real-lixin while issue#1 for 'blank space / wrong command input error' cannot fix that. I've tried : mex generateEllipseCandidates.cpp -I"D:\opencv2.4.9\build\include" -I"D:\opencv2.4.9\build\include\opencv" -I"D:\opencv2.4.9\build\include\opencv2" -L"D:\opencv2.4.9\build\x64\vc11\lib" -I"C:\Program...

> @AlanLuSun > > Error use mex > C:\Temp\mex_90112112165794_9244\generateEllipseCandidates.obj:generateEllipseCandidates.cpp:(.text+0x8e67): > undefined reference to `cv::Exception::Exception(int, std::string const&, std::string > const&, std::string const&, int)' > > ... Some errors lines ...... >...

> I also met this problem and I wonder have you fixed it yet?

I think I fix it tonight with '**cuda 10.1, torch=1.4.0**, numba=0.53.1'. And it's worth mentioning that **iou3d_nms module** can't be directly set up from the .sh file since it changed...

> I also encounter this problem. > > How to fix it ?? I think numba version may be incompatible with other dependencies. You can try my version plan above...

> It's said that "PyTorch 1.4.0 shipped with CUDA 10.1 by default, so there is no separate package with the cu101 suffix, those are only for alternative versions. " And...

In my case, the values of RGB channels in result picture come so close (e.g. 20/23/32) which contributes to its gray outlook.

> > In my case, the values of RGB channels in result picture come so close (e.g. 20/23/32) which contributes to its gray outlook. > > Any advice to avoid...

Further, I think that using the current implementation in this PR is also helpful in code reuse and reducing redundancy :).

> Same question, any solution now? Not yet :-( And there are so many differences compared with the implementation of ASE. e.g. [this problem](https://github.com/NVIDIA-Omniverse/IsaacGymEnvs/pull/198) you may also need to pay...