I'm not sure that I'm much help. Most of that work is done in vorSlice.cpp
The hard part isn't finding mean camber surfaces of arbitrary airfoils
-- the tricky part is fuselages and engines and combinations of
components merged together.
Roughly speaking, Vorview starts with the XSec/Hermite *.hrm wireframe file.
Vorview looks for discontinuities in planform and places Key Slices
there. The user can also manually place key slices. It then
distributes the desired number of slices (which become spanwise
panels).
Vorview slices through the wireframe geometry creating a composite of
all components which intersect that slice. The camber points
(chordwise panels) are distributed along each slice. Vorview looks
for the upper and lower surface envelope of the slice to determine the
mean camber surface.
The routine for just finding the mean camber is here:
https://github.com/OpenVSP/OpenVSP/blob/master/src/vsp/vorSlice.cpp#L5961
However, the entire slicing process is more complicated than just this
bit of code(that is where the magic is).
I hope this helps,
Rob
Glad to help out.
I thought that might be what you were after -- I almost included that
discussion in my response.
I think that when you consider the large number of gross
approximations which go into Vorlax, you won't be particularly worried
about whether the mean camber surface is what VSP uses or the 'true'
definition.
In my experience, Vorlax works amazingly well -- frankly, it works far
better than we have any right to expect.
Due diligence will require you to do some validation for your problem,
but I doubt you will be able to trace any error to the definition of
the mean camber surface.
Rob