Replies: 2 comments 1 reply
|
We are aiming for the following by v1:
|
1 reply
|
incredibly cool! hope to see this into mainline bsk soon! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi all!
Huge fans and users of Basilisk here. @schaubh
Me / @themouli / @madhav-madhusoodanan have been working on a rust translation of basilisk - this includes the core simulation base class, message passing, dynamics modules and FSW modules.
The main motivation behind this is that
LLMs/agents are also increasingly part of everyone's workflows, and due to great compiler errors, rust is easily one of the best languages to iterate on. So this should also enable faster ideation of both dynamics and flight software concepts.
Some parts of the translation were done using LLMs, and we intend to review any automated translation fully by v1 release.
5 scenarios already work and about a dozen modules have been ported so far.
We will add PyO3 in a future release for python bindings. The goal is that existing Basilisk python scripts should just work out of the box.
One of the results from MTB Momentum Management example :
By v1 release, goal is that all module unit tests and example scenarios match within machine level precision.
Thanks to @ChristopherRabotin for the wonderful hifitime and anise libraries, which we used extensively.
This is currently hosted here, we would like to explore avenues where this can be maintained, perhaps under AVSLab Github org.
Feedback / issue reports / contributions most welcome!
All reactions