Open NotMorven opened 1 month ago
Hello,
Unfortunately we want to avoid making any non bug-fix related changes to the 2.x branch, so we probably won't be able to back-port the Scene/Simulation storage functionality.
We'd be happy however to try to assist you in porting your 2.x code to Scenic 3.x. We have a page here with a guide on how to convert 2.x code to 3.x code, which can then be run in Scenic 3.x with Scenic 2.x semantics using the --2d
flag to enable 2D compatibility mode. Please let us know if there are any issues you encounter during the porting process and we're happy to take a look to see if we can help.
If you'd like to try to back-port the functionality yourself on a fork you're welcome to try. You'd probably have to cherry pick commits going back from this one.
Hi, @Eric-Vin
Thank you for your response. I have read the content in the https://docs.scenic-lang.org/en/latest/porting.html#scenic-2-to-3-converter section and attempted to use it with Scenic 3.
I installed the latest version of the Scenic package via PyPI. However, I could not find the mentioned conversion tool in my environment.
Could you please provide guidance on how to obtain this tool?
You'll need to check out the 2.x branch to get access the to conversion tool. I think this section should have the details you need: https://docs.scenic-lang.org/en/latest/porting.html#scenic-2-to-3-converter
Describe the feature and motivation
Firstly, thanks for the excellent Scenic project. It's been incredibly useful in our work.
I've read the "Storing Scenes/Simulations for Later Use" section in the documentation. However, due to certain constraints, I'm unable to migrate from Scenic 2.x to 3.x at this time.
Could you please provide guidance on how to implement similar scene/simulation storage functionality in Scenic 2.x?
Thank you for your assistance and continued support of the Scenic community.
Additional context
No response
Issue Submission Checklist