User-defined engine deck support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 62
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
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.
Potential solution
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing CFM56 and N+3 engine-deck implementations and inspect how their npy input is organized. Decide whether the contribution should document that format or add CSV support, then define the user-defined component and verify that it can load a user deck and build a surrogate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100