OpenVSP does not work with python

[Yifan Fu (be happy)]

I came across a rather urgent problem that has been bothering me for many days. That is, when I change some settings in python about OpenVSP, the calculation result does not change, it seems that the modified settings do not help. I really need your help to solve my problem!

[Brandon Litherland]

Your script was missing the part where you run VSPAEROComputeGeometry.  I went back and took some pieces of Tim Swait's post to your prior thread and inserted it into your script.  See attached.

For future posts, please don't repost an existing thread into a new message as this makes it very difficult to track prior responses.  If you need to bring your thread back up to the top of the forum, just post again in the same thread.  Don't create new ones for the same problem.

I'll also note that my insertion into your script may not be ideal so you will want to debug it a bit to make sure that everything is updating properly.  I also tested that the script is analyzing the correct diameter (per another prior post of yours) and the thrusts are changing with diameter as expected.  I'm running VSP 3.32.2 which can still sometimes hang when cutting the solution, particularly for unsteady runs.  I recommend deleting all cut planes from your model and analysis before you execute to avoid this lengthy post-processing.

[Yifan Fu (be happy)]

First of all, I apologize for my previous double posting.

I recently encountered another problem with 'vsploads.exe' not running properly. As with the previously modified code, when I repeatedly call 'vspaero.exe' for propeller calculations to get propeller thrust, the code will call 'vsploads.exe' after calling 'vspaero.exe' to get the results, but again 'vsploads.exe' will continue to run and cannot be closed, and take up CPU for a long time. only when I kill the task manager again 'vsploads.exe' can continue to work only after I kill the task manager. I would like to ask if there is a solution?

[Rob McDonald]

Please confirm what version of OpenVSP  you are running.  This sounds like a bug that was fixed recently.

Try running 3.33.1

Rob

--
You received this message because you are subscribed to the Google Groups "OpenVSP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/fdbb3bb5-109a-49ef-97e3-bfb0fef9d72en%40googlegroups.com.

[Yifan Fu (be happy)]

Thank you for your answer!
I previously used the version is 3.32.1, now I will 3.33.1 reconfigured to my environment, vsploads.exe will still appear to have been occupying the CPU can not be closed, I would like to ask if there is another solution, or can I add some command can be vsploads.exe can not be properly closed to kill the process?

[Brandon Litherland]

Unless you need the slice to process the Cp distribution at some location or to visualize the volumetric flow in Viewer, I recommend just removing the default Y=0 slice which will stop vsploads from running after vspaero.

[Yifan Fu (be happy)]

Thanks for your suggestion, I removed slice from the GUI and indeed no longer call 'vsploads.exe', but I can't find the API  command in python to use to remove slice. Can you tell me what is the code that corresponds to delete slice? thanks for your help!

[Brandon Litherland]

I haven't found the Analysis Manager setting that controls this but there is a parm in VSPAEROSettings, VSPAERO group called "CpSliceFlag" that deactivates the Slicer.