Simulate Early, Simulate Often... In Rhino
What I'd appreciate most for scripting is the possibility to obtain a number (stress, displacement, danger level) at a certain point (also within the volume, if possible). Another feature could be the extraction of a point cloud resembling the Volume (with adjustable resolution), each point again assigned with its value as its object name. I see there is already a way to pick a point and get its value (yet only on the surface) so I hope this is something not too hard to implement.
One more thing on my wishlist (again, not neccessarily as a rhinoscript command, but something to pave the way):
In addition to baking the mesh, it would be helpful to be able to extract the coloured surfaces with their corresponding colour scale.
Both of these features could then be used in rhinoscript for form finding / optimization without there being a specific rhinoscript command.
working with scripts offers several very interesting features to designer's job.
Consider, for example, the possibility to "automate" some analysis tasks, such as re-running SnS analysis with different design configurations that user can set with the actual potential scripting commands.
I worked a lot in the past with rhinoscript with the aim to make easier some design operations, and I believe that SnS, which only requires very few user settings, may be part of this design process.
So, I hope you may make SnS accessible for scripting very soon.
Some method of automating would be very useful for optimizations.
Any command that is accessed via the command line can be automated with rhinoscript or rhinocommon (perhaps other automation methods too, though I can't comment on those from lack of experience).
So simplest way to allow automation is to ensure all of your commands and options for your commands are accessible via the command line. Where this becomes a challenge is when you have commands that call on large dialogue boxes with a lot of options. Rhino command developers usually set up there commands so that a dash (-) prior to the command doesn't bring up a dialogue box but rather provides all of the command settings directly in the command line. Take a look at: '-patch' for example.
Creating commands for native rhinscript use would be nice, but It would be faster and good practice to ensure all of your command options can be accessible via the command line.
Hope this helps and looking forward to getting started with Scan&Solve (soon as you get multi body working, that is :-)