Colebrook Posted June 25, 2021 Share Posted June 25, 2021 (edited) Don't wait me either, this weekend i'm on a trip and i don't thinkĀ i can find a good internet connection. Edited June 25, 2021 by Colebrook 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted June 26, 2021 Share Posted June 26, 2021 Can someone please send me the AAR and report .htm from the game when it is finished?Ā I would like to use it for a project I'm working on, and will also share some of those results with the group as I glean them.Ā Thank you! 0 Quote Link to comment Share on other sites More sharing options...
TSe419E Posted June 26, 2021 Share Posted June 26, 2021 Here you go. reports.7z AAR.7z 0 Quote Link to comment Share on other sites More sharing options...
Moderators Volcano Posted June 26, 2021 Author Moderators Share Posted June 26, 2021 We ended up playing an alternate, two small missions (which were fun in their own way - a H2H and a coop š). We will try that one again next week to see if we have 12, otherwise we will go the next one in the list. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted June 26, 2021 Share Posted June 26, 2021 3 hours ago, TSe419E said: Here you go. reports.7z 13.95 kB Ā· 0 downloads AAR.7z 42.43 MB Ā· 0 downloads Thank you! 0 Quote Link to comment Share on other sites More sharing options...
BoomsBangsandCans Posted June 26, 2021 Share Posted June 26, 2021 should be there next week, work came up this week 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted June 28, 2021 Share Posted June 28, 2021 On 6/26/2021 at 6:13 AM, BoomsBangsandCans said: should be there next week, work came up this week Same here, I think I will be there on Friday as well this week. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted June 28, 2021 Share Posted June 28, 2021 Following up, I would like to sanity check some statistical analysis I am doing on the report files, so any feedback here will be valuable, many thanks in advance.Ā As an aside, the Mongoose report looks weird... was that maybe a game that crashed, or is there a reason a table wouldn't be generated for what unit killed which? Ā Regardless, I have these stats for the "Jackal" game report, I'm interested if the participants think these are accurate.Ā These are generated by pulling the table from the report that attributes who shot who, filtered for the column "Destroyed" having an "X," and broken down into three target (what was destroyed, not whom)Ā categories -- Tanks, PCs, and personnel. Ā For those not familiar with summary statistics, the count variable is how many times an event (in this case, hitting a vehicle with Damage marked as "X") happened, and the other numbers are range in meters. "mean" is the average min - smallest range in m max - largest range in m std - standard deviation (a measure of the spread from the mean) ...and the others are quartiles, to give a sense of the grouping. Ā Statistics for Report from: Ā .\reports\Brush Fire-Jackal-NG-4264.sce_8_06-25-21_22_47_58.htm Summary statistics on Kill ranges in meters for Tank targets: count Ā Ā Ā 51.000000 mean Ā Ā 1357.725490 std Ā Ā Ā 975.547704 min Ā Ā Ā Ā 73.000000 25% Ā Ā Ā 705.000000 50% Ā Ā Ā 933.000000 75% Ā Ā Ā 2326.000000 max Ā Ā Ā 3862.000000 Ā Summary statistics on Kill ranges in meters for PC targets: count Ā Ā Ā 17.000000 mean Ā Ā Ā 714.470588 std Ā Ā Ā 419.394224 min Ā Ā Ā Ā 42.000000 25% Ā Ā Ā 505.000000 50% Ā Ā Ā 773.000000 75% Ā Ā Ā 833.000000 max Ā Ā Ā 1905.000000 Ā Summary statistics on Kill ranges in meters for personnel targets: count Ā Ā Ā 155.000000 mean Ā Ā Ā 543.451613 std Ā Ā Ā 1209.463502 min Ā Ā Ā Ā 35.000000 25% Ā Ā Ā Ā 119.500000 50% Ā Ā Ā Ā 278.000000 75% Ā Ā Ā Ā 482.500000 max Ā Ā Ā 10421.000000 Ā Are statistics like this interesting?Ā What else might be interesting, e.g., what vehicle/unit made the max kill range?Ā Who had the most kills?Ā Anything else?Ā And am I reinventing the wheel and overlooking more obvious ways to glean this information?Ā Inquiring minds want to know... Ā Ā 1 Quote Link to comment Share on other sites More sharing options...
TankHunter Posted June 29, 2021 Share Posted June 29, 2021 That's some interesting stuff there Valley. Never would have assumed that infantry would get kill on average at such a distance. Always figured they would get ganked at shorter range. 1 Quote Link to comment Share on other sites More sharing options...
Moderators Volcano Posted June 29, 2021 Author Moderators Share Posted June 29, 2021 02 JULĀ 2021: Ā Civil War Mykonos-4265 We will give this one more shot, and if not enough then we will go to the next one. Ā SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 12 NOTES: Remember to play within theĀ TGIF House RulesĀ ļ»æandĀ SB.com Community Rules. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 6, 2021 Share Posted July 6, 2021 GG on Friday. Ā So here are the stats from that day, with some future details coming.Ā Based on feedback from Dark, I filtered out artillery hits/kills, because they were creating massive outliers (think 12km+) and moving the means too much. Ā Is it interesting to highlight (here) things like who had the longest distance kill, and in what platform?Ā It might also help me sanity check accuracy of these figures given extra eyes and egos involved. Ā Statistics for Report from: Ā .\reports\Civil War Mykonos-4265.sce_12_07-02-21_19_16_12.htm without artillery kills Summary statistics on Kill ranges in meters for Tank targets: count Ā Ā 158.000000 mean Ā Ā Ā 477.107595 std Ā Ā Ā 621.043293 min Ā Ā Ā Ā 36.000000 25% Ā Ā Ā 232.750000 50% Ā Ā Ā 306.000000 75% Ā Ā Ā 306.000000 max Ā Ā Ā 3211.000000 Ā Summary statistics on Kill ranges in meters for PC targets: count Ā Ā 105.000000 mean Ā Ā Ā 582.333333 std Ā Ā Ā 756.883878 min Ā Ā Ā Ā 85.000000 25% Ā Ā Ā 162.000000 50% Ā Ā Ā 205.000000 75% Ā Ā Ā 745.000000 max Ā Ā Ā 3699.000000 Ā Summary statistics on Kill ranges in meters for personnel targets: count Ā Ā 216.000000 mean Ā Ā Ā 343.226852 std Ā Ā Ā 414.587404 min Ā Ā Ā Ā 3.000000 25% Ā Ā Ā Ā 73.000000 50% Ā Ā Ā 209.000000 75% Ā Ā Ā 322.000000 max Ā Ā Ā 2150.000000 Ā 0 Quote Link to comment Share on other sites More sharing options...
DarkAngel Posted July 6, 2021 Share Posted July 6, 2021 27 minutes ago, Valleyboy said: So here are the stats from that day, with some future details coming.Ā Based on feedback from Dark, I filtered out artillery hits/kills, because they were creating massive outliers (think 12km+) and moving the means too much. Ā Think it may be interesting to narrow things down further. So for example with Kills on tanks he may be interesting to see this broken down further into "what" caused the kill ie Infantry (rpg), Infantry ATGM, Tank, APC etc Ā Also you may want to check the totals... I'm not convinced there were 158 kills in that mission (I could be wrong). Are you sure you aren't getting hits on things which are already dead?. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 6, 2021 Share Posted July 6, 2021 1 hour ago, DarkAngel said: Think it may be interesting to narrow things down further. So for example with Kills on tanks he may be interesting to see this broken down further into "what" caused the kill ie Infantry (rpg), Infantry ATGM, Tank, APC etc Ā Also you may want to check the totals... I'm not convinced there were 158 kills in that mission (I could be wrong). Are you sure you aren't getting hits on things which are already dead?. I think you hit it on the nose, I think it for sure is getting "non-kill" impacts on killed vehicles mixed in and confusing the numbers.Ā So there's an initial challenge (and thank you for that first sanity-check observation), is there a way in that table to filter for a specific metric to indicate whether it is the actual "kill hit," or is the solution to try to sort chronologically and then disqualify all hits after that on that specific entity?Ā E.g., "T-72 1/1" gets hit with a X on Destroyed for X event, and then after that, all other instances are ignored based on timestamp? 0 Quote Link to comment Share on other sites More sharing options...
Gibsonm Posted July 6, 2021 Share Posted July 6, 2021 51 minutes ago, Valleyboy said: is there a way in that table to filter for a specific metric to indicate whether it is the actual "kill hit," or is the solution to try to sort chronologically and then disqualify all hits after that on that specific entity?Ā E.g., "T-72 1/1" gets hit with a X on Destroyed for X event, and then after that, all other instances are ignored based on timestamp? Ā You can open it in Excel (even though its HTML) and then sort / extract that way. Ā That's how our OPs Analysis people do it. 0 Quote Link to comment Share on other sites More sharing options...
Colebrook Posted July 6, 2021 Share Posted July 6, 2021 Is possible to filter the results not by unit type but by the specific unit model?. Something like the numberĀ of kills/losses between 2 different units like m1 and t-72 can be very helpful for balancing missions. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 6, 2021 Share Posted July 6, 2021 49 minutes ago, Colebrook said: Is possible to filter the results not by unit type but by the specific unit model?. Something like the numberĀ of kills/losses between 2 different units like m1 and t-72 can be very helpful for balancing missions. Yes, I think so, and that is good feedback.Ā I need to solve the "What was the actual kill" chronology problem, but I'm assuming right now that the first time something is marked as "Destroyed," that's probably where I need to deem that unit dead and disqualify all other hits afterwards for the file.Ā Makes for some filtering challenges, but its probably useful code for later in the project anyways. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 6, 2021 Share Posted July 6, 2021 9 hours ago, Gibsonm said: Ā You can open it in Excel (even though its HTML) and then sort / extract that way. Ā That's how our OPs Analysis people do it. Thanks, that is good feedback on how the users engage with the data.Ā Our hope with this project is to help make it more error-free, standardized, faster, and allow batch processing on large amounts of files in the case where multiple cohorts or classes need to be compared, as one of the main use cases. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 7, 2021 Share Posted July 7, 2021 Ok, after some sweat and tears (and Python self-re-education), I have the below, for non-artillery, but not looked at critically yet.Ā Need some rest before tackling more, as I was still seeing unexpected artillery kills in the other version that I need to sanity-check: Ā Statistics for Report from: Ā .\reports\Civil War Mykonos-4265.sce_12_07-02-21_19_16_12.htm without artillery kills Summary statistics on Kill ranges in meters for Tank targets: count Ā Ā Ā 25.00000 mean Ā Ā 1160.84000 std Ā Ā Ā 1000.68292 min Ā Ā Ā Ā 36.00000 25% Ā Ā Ā 225.00000 50% Ā Ā Ā 1315.00000 75% Ā Ā Ā 2106.00000 max Ā Ā Ā 3211.00000 Ā Summary statistics on Kill ranges in meters for PC targets: count Ā Ā Ā 31.000000 mean Ā Ā Ā 994.645161 std Ā Ā Ā 1001.865512 min Ā Ā Ā Ā 85.000000 25% Ā Ā Ā 174.500000 50% Ā Ā Ā 664.000000 75% Ā Ā Ā 1865.500000 max Ā Ā Ā 3699.000000 Ā Summary statistics on Kill ranges in meters for personnel targets: count Ā Ā Ā 66.000000 mean Ā Ā Ā 346.833333 std Ā Ā Ā 446.305366 min Ā Ā Ā Ā 3.000000 25% Ā Ā Ā Ā 73.500000 50% Ā Ā Ā 187.000000 75% Ā Ā Ā 311.500000 max Ā Ā Ā 2150.000000 Ā 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 7, 2021 Share Posted July 7, 2021 (edited) For Tank targets, max kill user and type: (Shooter, Unit)Ā Ā Ā (Shooter, Type)Ā Ā Ā (Target, Target distance) 3/1/Tank Co (Blue) (pancho)Ā Ā Ā Tank (M60A3(TTS))Ā Ā Ā 3211.0 Ā For PC targets, max kill user and type: (Shooter, Unit)Ā Ā Ā (Shooter, Type)Ā Ā Ā (Target, Target distance) 1/3/Mech Co (Red) (-DK-)Ā Ā Ā PC (M901 ITV)Ā Ā Ā 3699.0 Ā Still working on how to generate these in a more user-friendly format with less manual programming.Ā Ideally this would be part of an export fileĀ and also aggregable. Ā Edit: Added on the actual range Edited July 8, 2021 by Valleyboy 0 Quote Link to comment Share on other sites More sharing options...
DarkAngel Posted July 8, 2021 Share Posted July 8, 2021 I t might be nice also to aggregate PC carried infantry kills into the PC kill if it died with it's infantry on board.Ā 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 8, 2021 Share Posted July 8, 2021 42 minutes ago, DarkAngel said: I t might be nice also to aggregate PC carried infantry kills into the PC kill if it died with it's infantry on board.Ā For those, would they have the same time-stamp in terms of death, game-wise, as the vehicle they were in? 0 Quote Link to comment Share on other sites More sharing options...
Moderators Volcano Posted July 8, 2021 Author Moderators Share Posted July 8, 2021 09 JULĀ 2021: Ā TGIF Watan Saraf Ekhlas V9-smaller_4265 Ā SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 10 (Red [4]Ā vsĀ Blue [4]Ā & Green [2]) NOTES: Remember to play within theĀ TGIF House RulesĀ ļ»æandĀ SB.com Community Rules. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 12, 2021 Share Posted July 12, 2021 So, to keep things fresh, I have some new stats to try to tell a story about this past game.Ā Note that the below are now filtered to exclude artillery and mine kills: Ā Unit and type for max range Tank type kill: Ā Ā (Shooter, Unit) Ā Ā Ā (Shooter, Type) Ā (Target, Target distance) 4/1/A (Red) Ā Tank (Challenger 2) Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā 3355.0 Unit and type for max range PC type kill: Ā Ā Ā Ā Ā Ā (Shooter, Unit) Ā Ā Ā (Shooter, Type) Ā (Target, Target distance) 2/1/A (Red) (Volcano) Ā Tank (Challenger 2) Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā 3422.0 Ā Tanks were killed by these unit types: Tank (Challenger 2) Ā Ā Ā Ā 14 Tank (T-72B1 m.1985) Ā Ā Ā Ā 12 Tank (T-72M m.1980) Ā Ā Ā Ā 11 personnel (Missile team) Ā Ā 8 PC (CV90/30-FI) Ā Ā Ā Ā Ā Ā Ā 7 Tank (Piranha DF90) Ā Ā Ā Ā Ā 5 Tank (T-62 m.1972) Ā Ā Ā Ā Ā 3 personnel (Rifle squad) Ā Ā Ā 1 PCs were killed by these unit types: PC (CV90/30-FI) Ā Ā Ā Ā Ā Ā 7 personnel (Rifle squad) Ā Ā 7 personnel (Missile team) Ā Ā 5 Tank (T-62 m.1972) Ā Ā Ā Ā Ā 3 Tank (T-72B1 m.1985) Ā Ā Ā Ā 2 Tank (Challenger 2) Ā Ā Ā Ā 2 Tank (Piranha DF90) Ā Ā Ā Ā 2 personnel (LMG team) Ā Ā Ā Ā 1 Ā Ā 1 Quote Link to comment Share on other sites More sharing options...
Moderators Volcano Posted July 13, 2021 Author Moderators Share Posted July 13, 2021 16 JULĀ 2021: Ā TGIF Watan Saraf Ekhlas V9-smaller_4265 We will try this again, we ended up playing a different scenario for various reasons. Ā SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. Minimum # players: 12 (Red (Insurgents) [5]Ā vsĀ Blue (Registani Army) [4]Ā & Green (NDF)Ā [3]) NOTES: Remember to play within theĀ TGIF House RulesĀ ļ»æandĀ SB.com Community Rules. 0 Quote Link to comment Share on other sites More sharing options...
Valleyboy Posted July 14, 2021 Share Posted July 14, 2021 I have a family trip that day, so it doesn't look like I'll be making our game this week.Ā This is the case the following Friday as well. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.