Cp Slice, Viewer, & Output File Questions

[Dennis Haimerl]

 Using version 3.36.0.

When loading previous results I cannot read Cp Slice results in the Results Manager nor can I display any results, such as Trailing Wakes, in the Viewer. Is this normal?

I have found the CP Slice data in the *.slc file that I could import to a spreadsheet, but I haven’t been able to determine where the Trailing Wake data is located.

I have had to evaluate several Geometry Sets using VSPaero. The output files are always placed in the folder where the *.vsp3 model geometry file resides and overwrites previous results. I have not found any information on how to redirect the results to a different folder. Once a set of results are output I move the files to a folder specifically name for those results. Is there a better way to accomplish this?

Thanks for any assistance you can provide. I am slowly creating a list and brief explanation of symbols and files as I work my way through learning OpenVSP. I’m an older dog that doesn’t sleep much and is getting slower, but still trying to learn new tricks. I will post my list for review when I have learned a bit more.

I would like to thank Brandon Litherland and Rob McDonald for their well though out videos that have help me learn the basics rather quickly as well as their general support. This is the first time I have actively joined an aero group since much of my proof-of-concept work (both aero & structural) has been proprietary and could not be shared.

[Brandon Litherland]

Without looking at your specific model it will be tricky to nail down exactly what's going on.  However, the slice issue is related to the Results Manager not executing VSPLOADS when reading in existing solution data.  To get your slice information into the Results display, you need to click "Slice Latest *.adb File" which will execute VSPLOADS and display the data.  The terminal output of this operation is displayed in the VSPAERO window with something like "vsploads.exe -slice modelname_DegenGeom" for VLM.  I'm not sure why you wouldn't be able to see the model in Viewer or show the trailing wakes... I created a model, ran VSPAERO, close then reopened VSP, and launched Viewer with the ADB data showing as usual.  Depending on what you are actually seeing, this could be a miscommunication or a real problem.  What do you mean by the trailing wake "data"?

The second part of your questions can be approached a number of ways.  The two most applicable to you would be to script the analysis and file move operations so it does it automatically or to change the name of the "case" that VSPAERO executes from the GUI.  I'm assuming that you are running from the GUI and picking individual Sets to analyze.  As you point out, VSPAERO doesn't differentiate between the model name and what components you choose to include (Sets).  However, if you click on the Advanced tab, you'll see Degen or Panel directly under Advanced Case Setup.  Clicking the ellipsis (...) will open a dialog box which lets you define the case name.  For example, if you click the button and enter "mySetName_DegenGeom.csv" for a VLM run it will execute on that case name and create input and output files with the same.  You don't strictly _have_ to include the _DegenGeom in the filename but I recommend it anyway to let yourself know that it was a VLM run.  Give this a try and see how it works out for you.  What's more is that you can load in any prior solution data in the Results Manager or Viewer this way.  If you choose a prior analysis as the filename and then click Load Previous Results, it will load the data for that case and not the model you have open.  Same goes for Viewer.

[Rob McDonald]

Not re-loading the Cp slice data from previous results is a known bug that I have fixed locally, but not yet released.

The wake data is held in the binary *.adb file along with the pressures, mesh agglomeration, etc.  Viewer gets almost everything from the *.adb file.

Rob