# Latest recommendations for global optimization

**URL:** <https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718>\
**Category:** Optimization (Mathematical)\
**Tags:** package\
**Created:** [November 19, 2018, 3:51pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718 "2018-11-19T15:51:05Z")\
**Posts on this page:** 13\
**Page:** 5

<div class="post-metadata">

**Author:** ![Oscar\_Smith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oscar_smith/32/25343_2.png) [@Oscar\_Smith](https://discourse.julialang.org/u/Oscar_Smith)\
**Post date:** [October 23, 2020, 5:50pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/81 "2020-10-23T17:50:08Z")

</div>

One place where this isn’t fully applicable is that Julia code is much more likely to use gradient based methods since autodiff often “just works”

---

<div class="post-metadata">

**Author:** ![microprediction](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@microprediction](https://discourse.julialang.org/u/microprediction)\
**Post date:** [October 23, 2020, 6:19pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/82 "2020-10-23T18:19:40Z")

</div>

For local search I agree. But the combination of gradient based methods with homological global intrigues me

---

<div class="post-metadata">

**Author:** ![jonathanBieler](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@jonathanBieler](https://discourse.julialang.org/u/jonathanBieler)\
**Post date:** [October 23, 2020, 6:58pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/83 "2020-10-23T18:58:54Z")

</div>

Porting it might be an fun project, it’s doesn’t look horribly complex (there’s some more code in libs though) :

[https://github.com/scipy/scipy/blob/v1.5.3/scipy/optimize/\_shgo.py](https://github.com/scipy/scipy/blob/v1.5.3/scipy/optimize/_shgo.py)

---

<div class="post-metadata">

**Author:** ![jmcastro2109](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmcastro2109/32/38427_2.png) [@jmcastro2109](https://discourse.julialang.org/u/jmcastro2109)\
**Post date:** [May 13, 2021, 5:21pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/84 "2021-05-13T17:21:07Z")

</div>

What is the state of the art on global optimization these days? Just wanted to see if there are major updates on this topic.

---

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [May 13, 2021, 5:44pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/85 "2021-05-13T17:44:16Z")

</div>

Maybe Baron and SHOT.

---

<div class="post-metadata">

**Author:** ![pierre-haessig](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pierre-haessig/32/217129_2.png) [@pierre-haessig](https://discourse.julialang.org/u/pierre-haessig)\
**Post date:** [July 11, 2022, 2:19pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/86 "2022-07-11T14:19:15Z")

</div>

For the reference, I find the “[Global Optimization Benchmarks](http://infinity77.net/go_2021/)” by Andrea Gavana (updated in 2021) quite useful.

Since he is working in Python, not all tested algorithms can be used easily in Julia, but at least **CRS2** and **DIRECT** from NLopt can be used with [NLopt.jl](https://github.com/JuliaOpt/NLopt.jl/). Too bad that the [MLSL multistart algorithm recommended by @stevengj](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/49) is not included in the benchmark.

[http://infinity77.net/go\_2021/](http://infinity77.net/go_2021/)

---

<div class="post-metadata">

**Author:** ![jonathanBieler](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@jonathanBieler](https://discourse.julialang.org/u/jonathanBieler)\
**Post date:** [July 11, 2022, 3:09pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/87 "2022-07-11T15:09:06Z")

</div>

Looks like we have a variation on the winner (MCS) here :

> **[GitHub - timholy/QuadDIRECT.jl: Global optimization without derivatives](https://github.com/timholy/QuadDIRECT.jl)**
>
> Global optimization without derivatives . Contribute to timholy/QuadDIRECT.jl development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [July 11, 2022, 11:53pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/88 "2022-07-11T23:53:18Z")

</div>

> [@pierre-haessig](#):
>
> For the reference, I find the “[Global Optimization Benchmarks](http://infinity77.net/go_2021/)” by Andrea Gavana (updated in 2021) quite useful.
> 
> Since he is working in Python, not all tested algorithms can be used easily in Julia, but at least **CRS2** and **DIRECT** from NLopt can be used with [NLopt.jl](https://github.com/JuliaOpt/NLopt.jl/). Too bad that the [MLSL multistart algorithm recommended by @stevengj](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/49) is not included in the benchmark.
> 
> [http://infinity77.net/go\_2021/](http://infinity77.net/go_2021/)

It would be nice to get a version of that benchmark on the SciMLBenchmarks with Optimization.jl so we can extend it to all of the solvers there and have it run on a reproducible open machine automatically each time a new PR is opened. I’d need some help getting it started though.

---

<div class="post-metadata">

**Author:** ![pierre-haessig](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pierre-haessig/32/217129_2.png) [@pierre-haessig](https://discourse.julialang.org/u/pierre-haessig)\
**Post date:** [July 13, 2022, 7:27am UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/89 "2022-07-13T07:27:01Z")

</div>

Perhaps a first issue is that the benchmark, although well documented, is not open source (unless I missed the link to the source code).

Neither are the algorithms specifically implemented in Python by the author (AMPGO, BiteOpt or MCS which @jonathanBieler mentioned to be “the winner”).

---

<div class="post-metadata">

**Author:** ![jonathanBieler](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@jonathanBieler](https://discourse.julialang.org/u/jonathanBieler)\
**Post date:** [July 13, 2022, 9:30am UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/90 "2022-07-13T09:30:39Z")

</div>

Apparently it’s a straight translation of the original Matlab code, not sure that makes it easier to run though…

[http://infinity77.net/go\_2021/mcs.html#mcs](http://infinity77.net/go_2021/mcs.html#mcs)

---

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [July 13, 2022, 9:18pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/91 "2022-07-13T21:18:26Z")

</div>

Theoretically, there are reasons to hope that QuadDIRECT is even better than MCS, but I’d love to be able to test that (many "probably"s founder on the rocks of reality).

---

<div class="post-metadata">

**Author:** ![pierre-haessig](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pierre-haessig/32/217129_2.png) [@pierre-haessig](https://discourse.julialang.org/u/pierre-haessig)\
**Post date:** [August 22, 2022, 9:25am UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/92 "2022-08-22T09:25:07Z")

</div>

By the way, I just came across a quite recent (2020) open access discussion of the many possible paths for extending the original 1993 DIRECT, by its author:

> **[The DIRECT algorithm: 25 years Later - Journal of Global Optimization](https://link.springer.com/article/10.1007/s10898-020-00952-6)**
>
> Introduced in 1993, the DIRECT global optimization algorithm provided a fresh approach to minimizing a black-box function subject to lower and upper bounds on the variables. In contrast to the plethora of nature-inspired heuristics, DIRECT was...

---

<div class="post-metadata">

**Author:** ![eirikeb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eirikeb/32/11674_2.png) [@eirikeb](https://discourse.julialang.org/u/eirikeb)\
**Post date:** [August 23, 2022, 12:29pm UTC](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718/93 "2022-08-23T12:29:08Z")

</div>

What an exceptionally well written article.

[Previous page](https://discourse.julialang.org/t/latest-recommendations-for-global-optimization/17718.md?page=4)
