# Need help wrapping cuOpt in julia

**URL:** <https://discourse.julialang.org/t/need-help-wrapping-cuopt-in-julia/129808>\
**Category:** Optimization (Mathematical)\
**Created:** [June 11, 2025, 2:15pm UTC](https://discourse.julialang.org/t/need-help-wrapping-cuopt-in-julia/129808 "2025-06-11T14:15:06Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![amontoison](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/amontoison/32/218741_2.png) [@amontoison](https://discourse.julialang.org/u/amontoison)\
**Post date:** [June 11, 2025, 9:14pm UTC](https://discourse.julialang.org/t/need-help-wrapping-cuopt-in-julia/129808/5 "2025-06-11T21:14:53Z")

</div>

I was at Stanford a few months ago and discussed with Chris Maes (lead developer of cuOpt).  
Based on the current implementation and our discussion, I don’t really see the advantage compared to cu-pdlp or HiGHS with the support of it.

JuMP / MOI is also not GPU-oriented so I am not sure what you want to achieve at the end except maybe a proof-of-concept or testing the accuracy.

If you want to work on it, be aware that it is not a small task.

---

_[View the full topic](https://discourse.julialang.org/t/need-help-wrapping-cuopt-in-julia/129808)._