Author Topic: July FSO Frame 2 analytics  (Read 72 times)

Offline RedBeard

  • Copper Member
  • **
  • Posts: 199
July FSO Frame 2 analytics
« on: Yesterday at 04:14:44 PM »
I've been working on an after action report generator and July Frame 2 got it confused.  I'd like to know what happened so I can figure out a way to improve it.  I've stripped out most of the details between the stats reporting.  What I'm curious about is what was going on with offense/defense on both sides.

The algorithm I use for determining which squads are offense and which are defense essentially boils down to a game of tag.  If you take off in a bomber, you're a squad on offense.  If you destroy ground objects, you are a squad on offense.  The rest is a game of tag where if you engage someone and the opponent is offense, you must be playing defense.  If you engage someone on defense, you must be offense.  Friendly fire is ignored.

The algorithm correctly figured out who was playing offense/defense on the Allied side, but something happened on the Axis side that messed things up.  It looks like the 367th might have been tasked with defense as they didn't go destroy any ground objects, but there was an engagement early on between the AKs and 367th and it looks like the tagging algorithm said if AKs are defense, then the 367th must be offense.

So how come two defensive squads were engaging early in the frame?  Who wandered into the "wrong" airspace?


2025-07-18   Battle of Okinawa   Frame 2   CM: SNO

Squads

Allied Offensive              Axis Offensive               
------ ---------              ---- ---------               
162ndFG""Purple*Hearts""      325th__Checkertails_VFG       
364th_C-Hawks                 327th_Steel_Talons           
9GIAP_VVS_RKKA                367th_FG_Dynamite_Gang       
LCA_RAIDERS                   JG11_Sonderstaffel           
ZZZ_NO_SQUADAllies            JG54_Grunherz                 
                              Kommando_Nowotny             

Allied Defensive              Axis Defensive               
------ ---------              ---- ---------               
Arabian_Knights                                             
CLAIM_JUMPERS                                               

Allied Neutral                Axis Neutral                 
------ -------                ---- -------                 

Pilots

Allied:              37 (56%) Axis:                29 (44%)
Offensive:           22 (59%) Offensive:           29 (100%)
Defensive:           15 (41%) Defensive:            0 ( 0%)
Neutral:              0 ( 0%) Neutral:              0 ( 0%)

...

22:10:00

22:12:07 12 F4U-1Cs defenders engaged 2 N1K2-Js, 1 Ki-84-Ia and shot down 2 N1K2-Js, 1 heavy Ki-84-Ia while losing 1 F4U-1C
...

Current Statistics as of 23:05:00

Allies                                  Axis                               
Offensive sorties:               55     Offensive sorties:              114
Heavy sorties:                   53     Heavy sorties:                  106
Heavy sorties with dmg:          17     Heavy sorties with dmg:          21
Heavy lost on ingress:            6     Heavy lost on ingress:           39
Heavy lost on egress:            19     Heavy lost on egress:            40
 
Fighters lost:                   39     Fighters lost:                   65
Bombers lost:                     8     Bombers lost:                    19
 
Hangars destroyed:                5     Hangars destroyed:                5
Bunkers destroyed:               15     Bunkers destroyed:               13
Ships destroyed:                  0     Ships destroyed:                  0
 
Heavy sortie effectiveness:   42.6%     Heavy sortie effectiveness:   26.9%

Defensive sorties:               44     Defensive sorties:                0
Defensive sorties lost:          21     Defensive sorties lost:           0
Defensive effectiveness:     386.4%     Defensive effectiveness:     3600.0%

...

Current Statistics as of 24:05:00

Allies                                  Axis                               
Offensive sorties:               95     Offensive sorties:              196
Heavy sorties:                   89     Heavy sorties:                  178
Heavy sorties with dmg:          36     Heavy sorties with dmg:          39
Heavy lost on ingress:           14     Heavy lost on ingress:           76
Heavy lost on egress:            26     Heavy lost on egress:            54
 
Fighters lost:                   77     Fighters lost:                  120
Bombers lost:                     9     Bombers lost:                    20
 
Hangars destroyed:                5     Hangars destroyed:                5
Bunkers destroyed:               18     Bunkers destroyed:               15
Ships destroyed:                 12     Ships destroyed:                  6
 
Heavy sortie effectiveness:   46.7%     Heavy sortie effectiveness:   25.5%

Defensive sorties:               66     Defensive sorties:                0
Defensive sorties lost:          43     Defensive sorties lost:           0
Defensive effectiveness:     315.9%     Defensive effectiveness:     5300.0%



« Last Edit: Yesterday at 04:28:18 PM by RedBeard »

Offline AKKuya

  • Gold Member
  • *****
  • Posts: 2694
Re: July FSO Frame 2 analytics
« Reply #1 on: Yesterday at 04:34:07 PM »
You will need to get in touch with each squad CIC per frame and request a copy of their orders.
This chapter has ended?

Offline RedBeard

  • Copper Member
  • **
  • Posts: 199
Re: July FSO Frame 2 analytics
« Reply #2 on: Yesterday at 04:46:29 PM »
Yeah, I have the Allied orders, which is how I could verify the tasking for Allies was correct.

Given that the AKs were tasked with patrolling NW, just how far out were AKLogan and AKRocco when the engagement occurred?

I also see that Kommando Nowotny was involved in that engagement, though they did some ground pounding later in the frame.

Offline Devil 505

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 9237
Re: July FSO Frame 2 analytics
« Reply #3 on: Yesterday at 05:13:24 PM »
As the Axis CiC, here's what I'll tell you.

Nobody wandered into the wrong airspace.

I just had the defensive squads in the Ki-84's and N1K2's sweep over the offensive target on their first leg as that was the likely point where they would meet a direct path Allied attack. This seemed the most sound defensive strategy given the proximity of the objectives and the Axis take off base. Sure enough that's just what we found. Had we more players on our side, this part of plan might have worked better. As it was, we got mauled by the Corsairs, with just a handful of kills for us.

But it forced the fighters to get low and to drop their bombs - if they carried any. The Peggy's and Tony's got relatively clean attack runs.

Also, the plan for subsequent sorties with downed pilots was to take bomb-laden Tony's and attack. Nobody was to defend the base after the first sortie.

And if not for a bunch of guys saying that we had sunk all but one of the Hour 2 ships, I would have pressed the Hour 2 attacks that entire hour too. As it was, the Allied fleets were so far apart that it was hard to see all the ships at any given time. I made the call to move to defending our fleets thinking we had sunk 11 boats. By the time our last attacker spotted the surviving destroyers in the Allied CV fleet, it was too late to go attack some more.

Cost us the frame.
Kommando Nowotny

FlyKommando.com

Offline RedBeard

  • Copper Member
  • **
  • Posts: 199
Re: July FSO Frame 2 analytics
« Reply #4 on: Yesterday at 05:51:52 PM »
Thanks for that info.  I think I'm going to have to adjust my algorithm to be more selective when target fields are close.