VSPAero error: xDoubleData.size() and yDoubleData.size() must be equal AND greater than 0

[Valentin Ouart]

Hello,

When I try to run a VSPAero analysis, I get the following repeated warning message in the console (see screenshot attached):

WARNING: xDoubleData.size() and yDoubleData.size() must be equal AND greater than 0
        xDoubleData.size()=1
        yDoubleData.size()=3

        File: D:\a\OpenVSP\OpenVSP\src\gui_and_draw\VSPAEROPlotScreen.cpp       Line:2722

The computation does not proceed correctly afterwards.

• OpenVSP version: 3.44.4

• Operating system: Windows 10

Has anyone encountered this issue before, or does anyone know what might be causing it?

Thanks in advance for your help!

[Rob McDonald]

Those errors are thrown by the XY plotting code when the data selected for plotting do not agree for some reason.  Most likely a problem with parsing the output files.

Please try migrating to 3.45.2 -- VSPAERO has been majorly updated there.

Rob

[Valentin Ouart]

Hello,

Thanks for your answer. I try migrating to 3.45.2 but I am still experiencing some issues.
A geometry that used to run fine in version 3.44 no longer works in 3.45.

When I try to run VSPAERO, I get the following error messages:

ERROR 7: Could not open History file: C:/001 - Valentin/ADS/ADSv467-Data/ADS-Data/Airplanes/Light Airplane/VSP/01/03/Export/VSP3/VSP-01-03_01.history
        File: D:\a\OpenVSP\OpenVSP\src\geom_core\VSPAEROMgr.cpp         Line:2187
ERROR 7: Could not open Polar file: C:/001 - Valentin/ADS/ADSv467-Data/ADS-Data/Airplanes/Light Airplane/VSP/01/03/Export/VSP3/VSP-01-03_01.polar
        File: D:\a\OpenVSP\OpenVSP\src\geom_core\VSPAEROMgr.cpp         Line:2462
ERROR 7: Could not open Load file: C:/001 - Valentin/ADS/ADSv467-Data/ADS-Data/Airplanes/Light Airplane/VSP/01/03/Export/VSP3/VSP-01-03_01.lod
        File: D:\a\OpenVSP\OpenVSP\src\geom_core\VSPAEROMgr.cpp         Line:2774

It seems like VSPAERO cannot create or open the output files (.history, .polar, .lod).
I did not change the geometry or my workflow, only the OpenVSP version.

Has something changed in the way VSPAERO runs between 3.44 and 3.45?
Do I need to adjust some settings or file paths to make it work again?

Thanks in advance for your help!

Valentin

[Rob McDonald]

Those messages are given by OpenVSP when it is not able to read the output files that should be created by VSPAERO.

This usually means that VSPAERO crashed for some reason.

There were many and varied changes to VSPAERO between 3.44 and 3.45.

You will want to review your settings and to some extent start over gaining experience with different input parameters.

As always, start with something simple, build up from there.

Rob