Originally posted by mikel
If we combine the 2 sets of data then 0 damage occurred in (163 + 157) / (200 +200) = 80.0% of the hours.
If combat is resolved on an hourly basis then 1 GD blocked 80% of the shots (not 67.7%).
My questions are:
Is combat resolved hourly or is a daily resolution "allocated" to each hour?
If combat is resolved hourly is it worth doing anymore tedious tests with Attack = 1 and GD = 1?
I think we can assume around 80%. We can only get a better estimate by checking a huge number of round 1 (since STR reducation possibly influences the P(block)) battles.
Another good thing is that we can now eliminate the P(hit) (did-we-hit?) we've been talking about (perhaps it was introduced when you presented the data with round1 and round 0 mixed up). Unless, of course, there's something like that but it's restricted to when a unit has GD (unlikely since Paradox didn't design units to have 0 GD).
Regarding hourly vs. day, I don't think they have gone through the trouble of first simulating a whole day and then applying the results on an hourly basis. It wouldn't make any sense. It would also lead to strange results when 'retreating' in the midst, or at least force the code to be more complex as it must signal to all units that a unit has retreated and re-calculate a partial day and then apply again.
Right now I can't think of any reason we might want to do more single 1/1 tests. No, wait I have two reasons we might want to :
1. To check how STR reduction works (using a variety of STR values from start). It would
a) Confirm that A is always >= 1
b) Confirm the rounding scheme of HoI.
2. Calculate a very precise value for P(blocked). We have 80%, which should be a good estimate, but one that might be effected by STR reductions. Actual value might be higher due to STR reduction, or it might not if STR reduction only effects the value of GD.
But these things can rest.. as you should
/F