More Picky Data!

[witpqs]

BTW here is an update of the list that started this thread.

" Battery engaging "
" Ships Reported to be Approaching!"
" accidentally lost "
" cannot establish contact "
" Defenses firing "
" 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 "

[Zorch]

" ramming speed "
" cloaking device activated "

[Will_L]

"You can have this oar when you pry it from my cold, dead fingers."

ORIGINAL: Zorch

" ramming speed "
" cloaking device activated "

[witpqs]

Here is the current list. I suspect there might be more which need including but this list gets me through 1,328 days of combat reports from my latest PBM.

" Battery engaging "
" Defenses firing "
" Ships Reported to be Approaching!"
" accidentally lost "
" acting as spotter "
" cannot establish contact "
" damaged beyond repair "
" dead in the water ..."
" dropped into water "
" 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"
"Ammo storage explosion on "
"Fuel storage explosion on "
"Heavy smoke from fires obscuring "
"Improved night sighting "
"Low visibility "
"Magazine explodes on "
"Massive explosion on "
"Maximum visibility "
"No activity noticed on shore."
"Poor visibility "
"Reduced sighting "
"Reduced visibility "

---

On a slightly different topic, I have a question about ship damage. In the section of a battle where the ships of each side are all listed there is also shown whatever hits each ships is thought to have sustained and certain damage levels. (The lists below use my variable names for each item.)

For hits we have:
"shlhits" - Shell hits.
"trphits" - Torpedo hits.
"bmbhits" - Bomb hits.
"hits" - This is how hits on submarines underwater are reported.
"minhits" - Mine hits.

For damage levels we have:
"dmgonfire" - On fire.
"dmghvfire" - Heavy fires.
"dmghvdmg" - Heavy damage.
"dmgsunk" - Sunk.

There are also additional damage messages that appear in the lower section of the battle report. These are the ones I know about.
"dmgmage" - Magazine explosion.
"dmgmase" - Massive explosion.
"dmgflse" - Fuel storage explosion.
"dmgamse" - Ammunition storage explosion.
"dmgosmk" - Obscured by heavy smoke.
"dmgdead" - Dead in the water.

My question is: are there more of those additional damage messages? Do you have samples?

[BBfanboy]

Are you only interested in ship-ship and amphib combats right now?
Here is an old CR from the Marianas scenario that I dug up. Mostly sub and carrier aircraft action ...

[Zorch]

"warpcoredamage" - call Scotty asap

[inqistor]

Kobayashi Maru?

[witpqs]

ORIGINAL: Zorch

"warpcoredamage" - call Scotty asap

An oldie but a goody!

[witpqs]

ORIGINAL: BBfanboy

Are you only interested in ship-ship and amphib combats right now?
Here is an old CR from the Marianas scenario that I dug up. Mostly sub and carrier aircraft action ...

You blink your eyes you miss a lot! [:'(] [:D]

I have combat report parsing fully functional. [8D]

The thing is, to catch something I have to know about it. Even though I certainly "knew" about all of those additional dmaage messages having seen them at one time or another, I did not recall them all when I put the list together. Out of the 6 there now I had 3 up until two days ago, and 4 up until last night/early this morning. I just let it run on my test data until it found something that did not compute and made barfing sounds. Then I added that damage type. I expect someone to report a damage message "Captain's strawberries missing, crew abandons ship!". When it comes up, I'll add it.

In a similar vein, that long list of trigger messages is how I am alerting to a transition from the upper section of certain battle reports to the lower section (naval battles in this case). So as I ran through the test data I heard "chug, chug, BARF!" whereupon I would add the newly identified trigger message. Then as they say "lather, rinse, repeat...".

It successfully goes all the way through my (I think it is) 1,328 days long test data set, so this is a call for possible missing items. AE is known for having rare messages that might not be in my test set.

[witpqs]

Current list:

" Battery engaging "
" Defenses firing "
" Ships Reported to be Approaching!"
" accidentally lost "
" acting as spotter "
" cannot acquire firing solution "
" cannot establish contact "
" damaged beyond repair "
" dead in the water ..."
" decides to submerge "
" dropped into water "
" 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 "
" low on gun ammo "
" mine cleared"
" mines cleared"
" on the surface"
"Ammo storage explosion on "
"Fuel storage explosion on "
"Heavy smoke from fires obscuring "
"Improved night sighting "
"Low visibility "
"Magazine explodes on "
"Massive explosion on "
"Maximum visibility "
"No activity noticed on shore."
"Poor visibility "
"Reduced sighting "
"Reduced visibility "