Differences between the FIM MOPS and the Aircraft Control Model on GitHub
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- documentation
Research direction
Start by comparing the Aircraft Control Model on GitHub with FIM MOPS Appendix H and the paper “Derivation of a Point-Mass Aircraft Model used for Fast-Time Simulation,” focusing on sections H.2.3 and H.6 and paper section 4.3. Document the missing condition, Energy Share Factor difference, and increased-drag details in the appropriate future documentation version; completion means these discrepancies are accurately captured.
Written by the indexing model from the issue text.
Description
There are some discrepancies between the Aircraft Control Model code on GitHub and what is described in the FIM MOPS in Appendix H (and the paper referenced on GitHub called “Derivation of a Point-Mass Aircraft Model used for Fast-Time Simulation”):
• In the FIM MOPS section H.2.3 and in section 4.3 “Derivation of a Point-Mass Aircraft Model used for Fast-Time Simulation”, the condition is missing from the MOPS Aircraft Control Model that is provided on GitHub.
• The Energy Share Factor algorithm (Algorithm H.4) in the FIM MOPS section H.2.3 last Else statement is slightly different than what is in the Aircraft Control Model on GitHub and in section 4.3 “Derivation of a Point-Mass Aircraft Model used for Fast-Time Simulation” which is below.
else if(eV > Vthreshold)
ES F = 1.7
• There is a lot more code for the increased drag than what is described in Algorithm H.6 in Section H.2.3 in the FIM MOPS and in section 4.3 “Derivation of a Point-Mass Aircraft Model used for Fast-Time Simulation”.
These differences don't seem to be causing any major issues for testing. But the documentation should be updated to capture these in a future version. Thank you.
- Dominant language
- C++
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
More from mitre/im_sample_algorithm
-
Remove old code Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mitre/im_sample_algorithm#14 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
mitre/im_sample_algorithm#15 ·
-
example analysis Opendocumentation
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in mitre/im_sample_algorithm
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·