Geometry Validity Check

[Nick-Hemenway]

I think we should add some sort of check to make sure the geometry entered is actually valid but I'm not sure if we should do this in the backend, or if we should do this on the front end. For example, for the inner rotor PM stator: If there are 8 teeth, the span angle of each tooth could not be 180 degrees. In other words, this would be an invalid geometry.

We could either have the cross section check that it is valid and return an error if not, or we could put checks in place at the optimization level to make sure no invalid geometries are ever inputted.

[elsevers]

I agree that this is needed and I think each cross-section should be responsible for checking that its own geometry is valid. We have already started to do this with validateattributes() ensuring that dimensions are non-negative.

(It may also make sense to do this at the optimization level, but regardless, an individual cross-section should validate that it is valid)