BGonline.org Forums

Accounting for uncertainty

Posted By: neilkaz
Date: Saturday, 9 July 2016, at 4:48 p.m.

In Response To: Accounting for uncertainty (Casper Van der Tak)

Yes I was using the generic "you".

But Rick states, "I think they may be close takes." (Referring to when we enter quickly with the bar pt open.)

To which I reply, then, indeed this cannot likely be a repeater error situation, which was my point in replying initially. If we dance, no problem just take another roll and if we enter and you still haven't made the bar, just cube. If we enter after you decide to roll in the initial position just cube us. If after a couple of rolls, you've rolled some awkward numbers and fear making a mess of the position, just cube us.

Many similar situations with low G chances can be repeater error situations but this one isn't noting that you can't lose much equity by waiting to cube when we enter.

The fact that you state, "I think they may be close takes" and then would cube lets us off the hook as we cannot make a cube error after entering.

So, to me, this situation is different than many real repeater error situations.

Is there the worry that this might only be .98 if you play on but then next turn it is .99 for example? Sure, maybe one cannot evaluate it as TG now, but with most rolls, more checkers come to aim at the bar pt, and more checkers get closer to home, making it almost a sure cash vs any entry and therefore a small playon for a small number of G's.

Messages In This Thread

• Accounting for uncertainty
  Bob Koca -- Friday, 8 July 2016, at 4:27 p.m.
  • Accounting for uncertainty
    Casper Van der Tak -- Friday, 8 July 2016, at 4:41 p.m.
    • Accounting for uncertainty
      Bob Koca -- Friday, 8 July 2016, at 4:59 p.m.
    • Accounting for uncertainty
      neilkaz -- Saturday, 9 July 2016, at 2:56 a.m.
  • Accounting for uncertainty
    Rick Janowski -- Friday, 8 July 2016, at 4:50 p.m.
    • I am referring to second position there *NM*
      Bob Koca -- Friday, 8 July 2016, at 4:52 p.m.
  • Accounting for uncertainty
    Rick Janowski -- Friday, 8 July 2016, at 5:22 p.m.
    • Accounting for uncertainty
      Bob Koca -- Friday, 8 July 2016, at 5:29 p.m.
      • Accounting for uncertainty - Agreed *NM*
        Rick Janowski -- Friday, 8 July 2016, at 5:37 p.m.
    • Accounting for uncertainty
      neilkaz -- Saturday, 9 July 2016, at 3:57 a.m.
      • Accounting for uncertainty
        Rick Janowski -- Saturday, 9 July 2016, at 7:56 a.m.
        • Accounting for uncertainty
          neilkaz -- Saturday, 9 July 2016, at 3:00 p.m.
          • Accounting for uncertainty
            Rick Janowski -- Saturday, 9 July 2016, at 3:55 p.m.
            • Accounting for uncertainty
              Casper Van der Tak -- Saturday, 9 July 2016, at 4:21 p.m.
              • Accounting for uncertainty
                neilkaz -- Saturday, 9 July 2016, at 4:48 p.m.
              • Accounting for uncertainty
                Rick Janowski -- Sunday, 10 July 2016, at 3:03 a.m.
  • Accounting for uncertainty--Uncertainty works both ways
    Phil Simborg -- Saturday, 9 July 2016, at 3:08 a.m.
    • Accounting for uncertainty--Uncertainty works both ways
      neilkaz -- Saturday, 9 July 2016, at 3:25 a.m.
    • Accounting for uncertainty--Uncertainty works both ways
      Timothy Chow -- Saturday, 9 July 2016, at 9:13 p.m.
  • XGR++ RO
    neilkaz -- Saturday, 9 July 2016, at 2:56 p.m.
  • Accounting for uncertainty - Variant Position
    Rick Janowski -- Sunday, 10 July 2016, at 3:45 a.m.
    • Accounting for uncertainty - Variant Position
      Casper Van der Tak -- Sunday, 10 July 2016, at 6:43 a.m.
      • Accounting for uncertainty - Variant Position
        Rick Janowski -- Sunday, 10 July 2016, at 9:30 a.m.
        • Accounting for uncertainty - Variant Position
          Casper Van der Tak -- Sunday, 10 July 2016, at 10:17 a.m.
          • Accounting for uncertainty - Variant Position
            Rick Janowski -- Sunday, 10 July 2016, at 6:32 p.m.