# \[ANN\] AccessibleOptimization: optimization with arbitrary objects instead of vectors

**URL:** <https://discourse.julialang.org/t/ann-accessibleoptimization-optimization-with-arbitrary-objects-instead-of-vectors/99695>\
**Category:** Package Announcements\
**Created:** [May 31, 2023, 10:16pm UTC](https://discourse.julialang.org/t/ann-accessibleoptimization-optimization-with-arbitrary-objects-instead-of-vectors/99695 "2023-05-31T22:16:14Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [September 14, 2025, 3:53am UTC](https://discourse.julialang.org/t/ann-accessibleoptimization-optimization-with-arbitrary-objects-instead-of-vectors/99695/15 "2025-09-14T03:53:53Z")

</div>

Check out [AccessibleModels.jl: Automatic UI and Model Fitting for Arbitrary Objects](https://discourse.julialang.org/t/accessiblemodels-jl-automatic-ui-and-model-fitting-for-arbitrary-objects/132363) : it builds on the positive experience creating and using this package, improving further.

AccessibleModels.jl provides a uniform model definition syntax for a bunch of backends instead of Optimizationjl-only here. Backends include optimization, MCMC sampling, and even UI generation.

I consider AccessibleOptimization.jl effectively deprecated now: it still works fine, but AccessibleModels.jl has all its features & more, and I recommend using that package instead.

---

_[View the full topic](https://discourse.julialang.org/t/ann-accessibleoptimization-optimization-with-arbitrary-objects-instead-of-vectors/99695)._