General Category > Unofficial F/A-18 Acceleration Pack board
Greenie Board Possibilities?
GOONIE:
FSXNavyPilot,
Great news! ;D It sounds like you have figured out SimConnect?
I like your idea of mimicking APARTS. Does NATOPS give any guidance on how deviations and their severity are used to determine a Grade? I feel this is the tricky part of the logic, for example would three minor deviations (glideslope IM, IC, AR) equate to one severe deviation AR (ie being low/slow) and affect the landing grade in a similar way. The APARTS output looks like a great format to show deviations (glideslope/lineup/power) and wire caught. The final grade (OK3) could be fed into a Greenie Board format like Raz put together.
FSXNavyPilot, do you have the originial TGS files? I do not know how to open the ATG.mission3.spd and look at the file in its entirety (I use notepad and can see most of the file). I used this file when I generated my updated LSO audio files, and while looking through the file I noticed a large section which appears to contain all of the conformance monitoring criteria and proximity triggers which I assume fed SimConnect to upload your approach for grading online when the website still was operating. If you are able to look at the .spd file provided with the mission it might provide some clues on how to collect performance metrics during the approach and then send them to an external script via SimConnect for collection and further analysis (APARTS output).
Thoughts?
SpazSinbad:
This PDF here has some great info about LSO grading parameters (whether it is actual used today - who knows):
OUTER-LOOP CONTROL FACTORS FOR CARRIER AIRCRAFT Robert K. Heffley 1 December 1990
http://robertheffleyengineering.com/docs/CV_environ/RHE_NAV_90_TR_1.pdf
GOONIE:
Thanks Spazsinbad!
The docs contain a lot of detailed criteria for grading each aspect of the approach; however, I am still unclear how it is used to surmise the final grade or score for the trap.
SpazSinbad:
You will have to educate yourself by reading these publications. Remember ordinary USN pilots selected/volunteering to become LSOs go to LSO school. Excerpts from both LSO PDFs attached below.
LSO NATOPS 01 May 2009:
http://www.wings-of-gold.com/cnatra/LSONATOPSMAY09.pdf (2Mb)
OK _OK_ Perfect pass
OK OK Reasonable deviations with good corrections
(OK) (OK) Fair. Reasonable deviations
— -- No-grade. Below average but safe pass
C Cut. Unsafe, gross deviations inside waveoff window
B Bolter
NC NC No count (used in grade column)
( ) ( ) Parentheses around any symbol signifies “a little” (e.g., (F) means “a little fast”)
_______ _Comment_ Underline. For emphasis
______________________________
LANDING SIGNAL OFFICER REFERENCE MANUAL (Rev B):
http://63.192.133.13/VMF-312/LSO.pdf (5.6Mb)
GOONIE:
Thanks Spaz, I understand the real world LSO grades, what I am trying to understand is how we would generate an automated LSO grade or score (not real world) using an automated Greenie Board that this thread is trying to discuss.
First you need the parameters for the approach, which the NATOPS docs provide, and collect performance against these parameters during the approach via an automated system (simconnect). Then you need to sum up all the deviations/performance values throughout the approach (X, IM, IC, AR) to get a final automated LSO grade (OK, (OK), --, C, B). Does that make sense?
Both an OK and (OK) say "reasonable deviations" which sounds pretty subjective if we are going to automate scoring each pass, not saying it is impossible, just saying it needs to be discussed. Thoughts?
Here is an example for an automated LSO grade, if you received (LUL) at X, IM, IC, AR, would you receive a OK, or (OK)? I guess we would need to monitor corrections and determine what is considered a "good correction" to receive a OK vs a (OK). FSXNavyPilot, do you have any ideas on how to judge good correction? Would it be a trend analysis or can you monitor corrections at each point during the approach? For example if you are LUL at the start and LUL in the middle, you would assume a good correction was not made and thus an (OK) is possible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version