More Picky Data!
Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition
More Picky Data!
I'm currently working my way through parsing the various naval actions in the combat reports.
Here is my approach with the many-headed set of naval actions. I've found that some have introductory messages, such as "31 Coastal gun shots fired in self defense." or "TF 15 troops unloading over beach at Makin, 135,135." Others have no introductory messages at all (after the title line of course). I can pick my way past those because they are predictable based on the type of naval action.
There is a large central section which, varying greatly, might include sections for:
Japanese aircraft
Allied aircraft
Japanese aircraft losses
Allied aircraft losses
Japanese Ships
Allied Ships
Japanese ground losses
Allied ground losses
base/city damages done
After that central section some - not all - actions have a series of lines chronicling the action, such as "CL Capetown firing at 144th Infantry Regiment", "CL Ceres firing at Ambon" and others pertaining to surface combat, etc. Most I will ignore but some will identify LCUs present and I will parse them. What might be in the lower section depends on the type of action, so that is where the code will treat different naval actions differently.
The various blocks of the central section (listed above) are not reliable insofar as which ones are present. I need to key on something to know when the central section has ended and the lower section is beginning. To that end I am going to look for certain key phrases that should never appear in the central section but that do appear in the first line of the lower section. So far I have this list.
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
"Maximum visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
I have made this a list in the config.ini file so it can be updated quickly and easily because I have a suspicion that AE might hold some rare messages that I haven't seen.
If you know of any other strings that appear in first lines of that lower section please let me know!
Here is my approach with the many-headed set of naval actions. I've found that some have introductory messages, such as "31 Coastal gun shots fired in self defense." or "TF 15 troops unloading over beach at Makin, 135,135." Others have no introductory messages at all (after the title line of course). I can pick my way past those because they are predictable based on the type of naval action.
There is a large central section which, varying greatly, might include sections for:
Japanese aircraft
Allied aircraft
Japanese aircraft losses
Allied aircraft losses
Japanese Ships
Allied Ships
Japanese ground losses
Allied ground losses
base/city damages done
After that central section some - not all - actions have a series of lines chronicling the action, such as "CL Capetown firing at 144th Infantry Regiment", "CL Ceres firing at Ambon" and others pertaining to surface combat, etc. Most I will ignore but some will identify LCUs present and I will parse them. What might be in the lower section depends on the type of action, so that is where the code will treat different naval actions differently.
The various blocks of the central section (listed above) are not reliable insofar as which ones are present. I need to key on something to know when the central section has ended and the lower section is beginning. To that end I am going to look for certain key phrases that should never appear in the central section but that do appear in the first line of the lower section. So far I have this list.
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
"Maximum visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
I have made this a list in the config.ini file so it can be updated quickly and easily because I have a suspicion that AE might hold some rare messages that I haven't seen.
If you know of any other strings that appear in first lines of that lower section please let me know!
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
Don't forget "No activity spotted on shore"! Or whatever it is.
RE: More Picky Data!
Got it - thanks!ORIGINAL: Lokasenna
Don't forget "No activity spotted on shore"! Or whatever it is.
No activity noticed on shore.
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
I had several naval actions last turn. The descriptive section after the action results always starts with the visual range and weather info. See pic below:
- Attachments
-
- NavalCombat.jpg (241.74 KiB) Viewed 288 times
No matter how bad a situation is, you can always make it worse. - Chris Hadfield : An Astronaut's Guide To Life On Earth
RE: More Picky Data!
Yes, I am catching surface combat central section with "Maximum visibility ", thanks. I should have been more clear that I am talking about the various action types of naval combats.ORIGINAL: BBfanboy
I had several naval actions last turn. The descriptive section after the action results always starts with the visual range and weather info. See pic below:
"Pre-Invasion action"
"Invasion Support action"
"Amphibious Assault"
"Naval bombardment"
"Night Naval bombardment"
"Day Time Surface Combat"
"Night Time Surface Combat"
"encounters mine field"
"ASW attack"
"Submarine attack"
"Midget Sub attack"
"Sub attack"
"Sub vs Sub:"
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
So, things like "**MAGAZINE EXPLODES** on [ship]" or "**MASSIVE EXPLOSION** on [ship]"?
[ship] hits rocks while unloading troops at [hex] (not sure the syntax is exactly correct)
[ship] hits rocks while unloading troops at [hex] (not sure the syntax is exactly correct)
No matter how bad a situation is, you can always make it worse. - Chris Hadfield : An Astronaut's Guide To Life On Earth
RE: More Picky Data!
ORIGINAL: BBfanboy
So, things like "**MAGAZINE EXPLODES** on [ship]" or "**MASSIVE EXPLOSION** on [ship]"?
Those are already extracted by the air attacks code, where they form the very last group of messages in any battle. They will also be extracted in the naval battles code, where they are mixed into the lower section. Like so:
Capturing those messages is one of the reasons I need to detect where the lower section begins.Reduced visibility due to Rain with 7% moonlight
Maximum visibility in Rain and 7% moonlight: 1,000 yards
Range closes to 21,000 yards...
Range closes to 19,000 yards...
Range closes to 17,000 yards...
Range closes to 15,000 yards...
Range closes to 13,000 yards...
Range closes to 11,000 yards...
Range closes to 10,000 yards...
Range closes to 9,000 yards...
Range closes to 8,000 yards...
Range closes to 7,000 yards...
Range closes to 6,000 yards...
Range closes to 5,000 yards...
Range closes to 4,000 yards...
Range closes to 3,000 yards...
Range closes to 2,000 yards...
Range closes to 1,000 yards...
Magazine explodes on DD Yukikaze
DD Yukikaze sunk by BB Prince of Wales at 1,000 yards
BB Prince of Wales engages xAP Koan Maru at 1,000 yards
DD Bulmer engages xAP Koan Maru at 1,000 yards
Range increases to 2,000 yards
BB Prince of Wales engages DD Karii at 2,000 yards
BB Prince of Wales engages xAP Koan Maru at 2,000 yards
xAP Koan Maru sunk by DD Express at 2,000 yards
Range increases to 4,000 yards
DD Karii engages DD Express at 4,000 yards
DD Vampire engages DD Karii at 4,000 yards
Japanese Task Force Manages to Escape
Task forces break off...
I thought that was in a different report? I'll search the sample combat reports I'm using.[ship] hits rocks while unloading troops at [hex] (not sure the syntax is exactly correct)
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
In the combat reports I am finding that ' rock ' only appears in ship names.
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
This is the current triggers list:
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
Updated list:
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
" accidentally lost "
" damaged beyond repair "
" lost from landing craft "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" mines cleared"
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
" accidentally lost "
" damaged beyond repair "
" lost from landing craft "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" mines cleared"
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
" rescues 7 castaways on 3 hour cruise ".ORIGINAL: witpqs
Updated list:
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
" accidentally lost "
" damaged beyond repair "
" lost from landing craft "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" mines cleared"
RE: More Picky Data!
That messages only occurs on the last turn of the game... [:'(]ORIGINAL: Zorch
" rescues 7 castaways on 3 hour cruise ".ORIGINAL: witpqs
Updated list:
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
" accidentally lost "
" damaged beyond repair "
" lost from landing craft "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" mines cleared"
BTW, did they get rescued? I never saw the last episode. [&:]
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
Lots of great midget sub messages.[;)]
RE: More Picky Data!
Another update:
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
" accidentally lost "
" damaged beyond repair "
" lost from landing craft "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" mines cleared"
"Poor visibility "
"Low visibility "
" firing at "
" fire at "
" fired at "
" lost overboard "
" lost in surf "
" accidentally lost "
" damaged beyond repair "
" lost from landing craft "
"Maximum visibility "
"Reduced visibility "
" launches "
" is sighted "
" eludes ASW attack "
" cannot establish contact "
"No activity noticed on shore."
" mines cleared"
"Poor visibility "
"Low visibility "
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
Ya know, it might be a genetic predisposition or something but midget subs almost always kick my butt at Pearl Harbor!ORIGINAL: Lowpe
Lots of great midget sub messages.[;)]
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
And yet a newer list:
" Battery engaging "
" Ships Reported to be Approaching!"
" accidentally lost "
" cannot establish contact "
" damaged beyond repair "
" elects not to launch "
" eludes ASW attack "
" fire at "
" fired at "
" firing at "
" firing to "
" is located "
" is sighted "
" launches "
" lost from landing craft "
" lost in surf "
" lost overboard "
" mine cleared"
" mines cleared"
"Low visibility "
"Maximum visibility "
"No activity noticed on shore."
"Poor visibility "
"Reduced sighting "
"Reduced visibility "
" Battery engaging "
" Ships Reported to be Approaching!"
" accidentally lost "
" cannot establish contact "
" damaged beyond repair "
" elects not to launch "
" eludes ASW attack "
" fire at "
" fired at "
" firing at "
" firing to "
" is located "
" is sighted "
" launches "
" lost from landing craft "
" lost in surf "
" lost overboard "
" mine cleared"
" mines cleared"
"Low visibility "
"Maximum visibility "
"No activity noticed on shore."
"Poor visibility "
"Reduced sighting "
"Reduced visibility "
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
RE: More Picky Data!
" Raises shields and fires photon torpedo ".ORIGINAL: witpqs
And yet a newer list:
" Battery engaging "
" Ships Reported to be Approaching!"
" accidentally lost "
" cannot establish contact "
" damaged beyond repair "
" elects not to launch "
" eludes ASW attack "
" fire at "
" fired at "
" firing at "
" firing to "
" is located "
" is sighted "
" launches "
" lost from landing craft "
" lost in surf "
" lost overboard "
" mine cleared"
" mines cleared"
"Low visibility "
"Maximum visibility "
"No activity noticed on shore."
"Poor visibility "
"Reduced sighting "
"Reduced visibility "
" Finds Amelia Earhart ".
" Raises skull & crossbones flag ".
Yes, they did rescued in a TV movie after the series was canceled.
RE: More Picky Data!
The other two I'll put in but this one yields an error:ORIGINAL: Zorch
" Raises shields and fires photon torpedo ".ORIGINAL: witpqs
And yet a newer list:
" Battery engaging "
" Ships Reported to be Approaching!"
" accidentally lost "
" cannot establish contact "
" damaged beyond repair "
" elects not to launch "
" eludes ASW attack "
" fire at "
" fired at "
" firing at "
" firing to "
" is located "
" is sighted "
" launches "
" lost from landing craft "
" lost in surf "
" lost overboard "
" mine cleared"
" mines cleared"
"Low visibility "
"Maximum visibility "
"No activity noticed on shore."
"Poor visibility "
"Reduced sighting "
"Reduced visibility "
" Finds Amelia Earhart ".
" Raises skull & crossbones flag ".
Yes, they did rescued in a TV movie after the series was canceled.
Amelia Earhart not found!
Intel Monkey: https://sites.google.com/view/staffmonkeys/home
- MakeeLearn
- Posts: 4274
- Joined: Sun Sep 11, 2016 1:01 pm
RE: More Picky Data!
"I'm afraid I can't do that. This mission is too important for me to allow you to jeopardize it."
RE: More Picky Data!
The mission is proceeding well, HAL.ORIGINAL: MakeeLearn
"I'm afraid I can't do that. This mission is too important for me to allow you to jeopardize it."
In the last stages of parsing the combat reports for useful info, which was way more involved than I had anticipated. Think the 80/20 rule.
Intel Monkey: https://sites.google.com/view/staffmonkeys/home