I have a question about the DegenGeom csv file being used in OpenVSP 3.13.3 and VSPAero 4.2. I noticed that there is a new section within the DegenGeom file, which specifies the following parameters:
"lex,ley,lez,tex,tey,tez,cgShellx,cgShelly,cgShellz,cgSolidx,cgSolidy,cgSolidz,toc,tLoc,chord,Ishell11,Ishell22,Ishell12,Isolid11,Isolid22,Isolid12,sectArea,sectNormalx,sectNormaly,sectNormalz,perimTop,perimBot,u,t00,t01,t02,t03,t10,t11,t12,t13,t20,t21,t22,t23,t30,t31,t32,t33,it00,it01,it02,it03,it10,it11,it12,it13,it20,it21,it22,it23,it30,it31,it32,it33,toc2,tLoc2,anglele,anglete,radleTop,radleBot,"
Without this section, VSPAero produces the following error: "GeomIDFlags are NOT defined!" As I have mentioned previously, I am developing Matlab functions capable of converting an *.hrm wireframe geometry directly to a DegenGeom file and running VSPAero's VLM solver manually. The code that I had developed for previous versions no longer works with the new release because of this error, but I'm wondering if it's necessary to make all of these calculations or not. Inserting dummy values for the entire section produces a segmentation fault, so some of the parameters are obviously utilized in the solver. I was hoping that you might be able to clarify which values are critical to the analysis and which could be omitted/replaced with a dummy value.
Thank you!
Jason