User-defined engine deck support #85
Description
Description of feature
It'd be nice to have a general turbofan deck component that loads a user-provided deck data file and build surrogate, like we currently do for CFM56 and N+3 engine decks. Currently the input data file is in npy so it's hard for a user to prepare their data in the format OpenConcept requires. So we can either document how the npy data is organized or support other file format like CSV.