Hello COMPAS friends.
I know I’m late to the party, but what happened to the Plotter and the compas_plotters package!? I’m migrating my codebase to version 2.15 and I find that good ol’ matplotlib and company are silently gone after version 1.17.10 (not only that, but the CHANGELOG.md file on GitHub does not report the disappearance). Will compas_plotters make a come back from the ashes as some other package, or is it forever gone? :')
Yours,
A matplotlib aficionado.
From the last chats with @tomvanmele it seems like the plotter is indeed gone with no plans to come back. Perhaps @tomvanmele wants to have a separated - community backed - compas_plotter like compas_viewer? Not sure.
Yes, I think there were no plans to bring them back, however, I gave it a go at migrating them using Claude, and it turns out to be quite straight-forward. I created a port repo of it on my personal github, and I will discuss with the association if we want to bring this back officially, or if it should stay a community contrib.
@arpastrana please give it a go and let me know if it works, I have tested it only superficially
Cheers!
Gonzalo
I did a few more tweaks to it, now it’s aligned with the `Scene` model of `compas` core and `compas_viewer`
Thanks, @gonzalocasas - it took me a while to get back to this, but the revived compas_plotters works for me! See the animation of the optimization of a funicular arch below, which we generated using Plotter.on() (after including the changes proposed in this PR).
I noticed the package moved back to the compas organization. Is the plan to make it an officially supported library? It would be fantastic to see a release on pypi in any case to pin it as a dependency in my projects 
Also, should the package be renamed compas_plotter for symmetry with compas_viewer and compas_notebook (i.e., name change from plural to singular)?
Done! All of those things: merged your PR, renamed to singular, and release to pypi compas_plotter v1.0.0 ! compas-plotter · PyPI
Cheers
Gonzalo
Pawsome 
- and compas_plotter now ships as a viz dependency of jax_fdm! Thanks for the quick turnaround, Gonzalo. Cheers!
Found a tiny issue with the plugin management system that compas_plotter is interfering with, and made a PR with a potential fix a couple of days ago. Please let me know if this looks good to you, @gonzalocasas!
Awesome! Merged and released!
I added `jax_fdm` to our “mission control” dashboard: COMPAS Mission Control (btw, you can use the badge to link there)!
The Mission Control dashboard is pretty neat. Thanks for adding jax_fdm - the dashboard is helpful to identify rough edges!
I wonder though where it pulls the jax_fdm stats from: the package supports Python 3.12 and does not use compas.artists anymore (since 2 versions ago), but the dashboard reports the opposite. Any chance we can update the red indicators?
The other cool thing about the dashboard is that made me realize that compas_cem needs some love. It is still deep in the weeds of compas<2. Is there a migration guide I can peek at to bring compas_cem back to the future?
You’re right! I just fixed both checks!
The other cool thing about the dashboard is that made me realize that
compas_cemneeds some love. It is still deep in the weeds ofcompas<2. Is there a migration guide I can peek at to bringcompas_cemback to the future?
Mmm.. we don’t have officially, but I put together this as an extraction and summarization of CHANGELOG: migration.rst · GitHub
Cheers!
Great. I’ll check out the migration summary to, hopefully, modernize compas_cem soon.
Back to the dashboard stats, is there a particular reason why support for python 3.13 is tested? I checked the TOML file of COMPAS and the latest python it supports is version 3.12. I based the jax_fdm python versioning based on that scope. Just double-checking here and happy to update my package
Cheers!
No absolutely critical reason to support 3.13, but on the other hand, 3.13 is almost half-life now, so, ideally, it should be supported. COMPAS core itself is red on a number of checks, which I’m hoping we’ll tackle soon!
That’s a good idea. I just added support python 3.13 in jax_fdm, and now it shows lovely green on the Mission Control dashboard. The badge is now part of the readme too! P.S. the compas_cem resuscitation is underway. Thanks again!