VSPAERO with Python API behaving differently after upgrade

[Tim Swait]

I recently upgraded Open VSP from 3.31 to 3.36. I've noticed that there now seems to be a bit of glitch when running VSPAERO through the Python API.

I typically open a "filename.vsp3" file, which may be in a different folder to where I'm running the script from, do some changes to it, run an analysis, read the results. Previously (with 3.31) then it would create all the analysis files (CompGeom, DegenGeom, etc) in the folder containing filename.vsp3 and all these files would be called things like "filename_CompGeom.txt", etc. Now these files are created in the folder that I run the script from and have names like "Unnamed_CompGeom.txt", etc. Also I notice this in the output from the run:

Error Code: 5, Desc: FindResultsID::Can't Find Name VSPAERO_History at index 1 /home/timbo/anaconda3/envs/vsppytools/lib/python3.10/site-packages/openvsp/vspaero -omp 16 Unnamed_DegenGeom VSPAERO v.6.4.8 --- Compiled on: Oct 27 2023 at 22:37:53 PST

Mostly, it seems to work fine anyway, but it seems like it's getting confused about where these files are getting placed. The only situation I've found where it doesn't work at all is if I do a Panel mode analysis without first having done a VLM. In this case it quits with a file not found error. If I run a VLM analysis first (so all the Unnamed_DegenGeom files do exist) then it seems to work.

Tim

[Tim Swait]

Actually, it seems that Panel just isn't working properly, the results seem very spurious, so I think it's picking up the wrong files somewhere.