VSPAERO Output files

[Ben H]

I'm using the GUI and can't figure out how to get the history, LOD, FEM, etc. output files. I am just launching the solver and exporting those results to csv. This file is very messy and kind of unusable.

[Rob McDonald]

Look on your hard drive where your *.vsp3 file is located.  The history, LOD, FEM are all written there.  You can parse them yourself as you like.

OpenVSP parses some (most) of that data for you.  We then plot it in the GUI Results Manager -- which also has a button to write out what it parsed into a *.csv file.  That file is not the origin -- it has been read in and then written back out.

Since OpenVSP parses much of the data written by VSPAERO, you can also get to that data through the API -- *.vspscript, Python, Matlab, or whatever you have set up to use the API.  If you access it this way -- and OpenVSP has read the data you need, then you don't need any other files, the data is available in memory for you.

If my answer isn't helpful, perhaps I'm missing the point.  Could you be more specific what you're doing, what you're seeing, and what you would like to see instead?  Or, say what you'd like to accomplish at a top level and we can help point you in the right direction.

The Results Manager GUI in OpenVSP is not meant to be a general purpose plotting program or to produce publication ready plots.  It is meant to be a quick and dirty way of looking at results and performing a sanity check.  My experience is that checking plots is very important for getting quality results -- but that most users don't take the time to make the plots they need to check.  The Results Manager is there to take away any excuses -- it makes the quick plots very easy and immediate.

Rob

On Fri, Nov 20, 2020 at 12:45 PM Ben H <407yo...@gmail.com> wrote:

I'm using the GUI and can't figure out how to get the history, LOD, FEM, etc. output files. I am just launching the solver and exporting those results to csv. This file is very messy and kind of unusable.

--
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/32a75fc7-70c3-4dce-877d-14322b7d0361n%40googlegroups.com.

[Ben H]

Really helpful. I was expecting to see a history file that looked like the one in this tutorial http://openvsp.org/wiki/doku.php?id=vspaerotutorial&s[]=vspaero#history_file but I guess I need to parse it myself. Looking at my output file it looks like this information is included, but is just not formatted/consolidated as neatly. This is what my output looks like https://docs.google.com/spreadsheets/d/1CYodQ-879r5Lt2zGDPbDrV0HobZ8q-T6t1PO20okxVk/edit?usp=sharing. Do you have an idea of how I could get my data to look like the one from the tutorial. At a high level I want to just be able to get the results similar to the history file in the tutorial for easy viewing.

[Rob McDonald]

When I run a generic wing.vsp3 in an otherwise empty directory (default settings for VSPAERO, VLM mode), I end up with the attached image listing files in the directory...

OpenVSP file:

wing.vsp3  -- Standard OpenVSP model file

Files written by OpenVSP to be read by VSPAERO:

wing_DegenGeom.csv  -- DegenGeom file with VLM geometry

wing_DegenGeom.vspaero  -- VSPAERO Solver conditions control file

Files written by VSPAERO during / after solution:

wing_DegenGeom.adb  -- Binary file with full solution data, don't try parsing it, read by vspviewer for pretty pictures

wing_DegenGeom.adb.cases  -- Simple file giving names to the cases in the *.adb file.  Not really useful.

wing_DegenGeom.fem  -- File giving loads in a format useful for coupling with a simple beam FEA code.

wing_DegenGeom.group.1  -- Loads of group 1 components in global reference frame

wing_DegenGeom.history  -- Total loads and convergence history information

wing_DegenGeom.lod  -- Wing load distribution information

wing_DegenGeom.polar  -- Simplified overall force/moment output data

If you do unsteady cases, you will have a groups file (no numbers) written by OpenVSP for input to VSPAERO.  It is the guide that describes how to group components and describes the motion -- rotors rotating about axes, 6DOF simulation of bodies (center of mass, inertias, etc).  Likewise, you will then have multiple groups.# files and possibly rotor.# files with loads on those bodies.

If you do stability cases, you will have at least a .stab file with the stability derivatives summarized in it.

There are other options that will kick out other output files as well.

Most of these are pretty straightforward and human readable.  The only binary one is the *.adb file.

If you haven't looked through them, I suggest you do.  In particular, the *.history and *.polar file are probably what you want.

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/1b4d6aac-31f5-4a1e-9483-eb6c1668396cn%40googlegroups.com.

[Ben H]

Oh, I just didn't look carefully enough. Thank you.

[Franco Staub]

Rob,

I am running OpenVSP 3.31.1 and am looking to get an *.slc file via command prompt.

I defined the cut locations through the GUI, and turned on the "Activate Slicer" button there.

When I run VSPAERO through the GUI, the ".slc file generates, but when I run vspaero via command prompt it does not. 

I guess I need to run vspslicer with an *.adb file created by vspaero to generate an *.slc file via command prompt, but in the version I am using, there is no vspslicer exec file (I'm guessing the documentation is behind the updates on this issue?).

Anyhow, I'm not sure where my problem lies (my .vspaero file def, incorrect installation, missing info about vspslicer, etc), but what do you suggest I try in order to get the *.slc file generated via command prompt?

Thanks always,

Franco

[Rob McDonald]

The vspslicer program grew in functionality and is now incorporated into vsploads.  To get at the old functionality, you run

vsploads -slice filename

Although slicing runs automatically when you generate a solution, if you manually run a slicing operation through the GUI, I think it will output the command to the console...  I just checked, it looks like we fail to do that.

If you want to see where the Cp slicing command is constructed, look here.

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/baeae459-28a7-4e8a-aa1c-e931c6e0d7c1n%40googlegroups.com.

[Franco Staub]

Rob,

Thanks for the help as always. That solution works perfectly. This will be of great help for a first pass prediction of leading edge stall.

Best regards,

Franco

You received this message because you are subscribed to a topic in the Google Groups "OpenVSP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openvsp/EPMe0K97QP4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openvsp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/CAEppYpHrQGp-mK8e_dk250-t_DMT%3D7J1LbCBZ2rH_C08uSb5FA%40mail.gmail.com.