Hi Dr. Leduc,

So I re-did the bilevel test cases (level-wise cont/NB as well as
check-all) and as mentioned in your email (and our discussion over the
phone), I noticed some discrepancies with regards pop-ups:

  * for the bdd tests, in cases where LD interface consistency fails,
    the pop-up sometimes prompts the user for a counter-example and
    sometimes doesn't. Based on our discussion, it shouldn't when LD
    interface consistency fails, correct?
      o When you do a "check all" under BDD tests for testHISC10,
        testHISC13 and testHISC14, the pop-up will not mention a
        counter-example.Whereas earlier cases (I forget which exactly)
        that fail LD interface consistency will prompt you for a
        counter-example.

  * testHISC14 is behaving strangely under the DESpot algorithms.
      o When you do a "Check All", you do not get a pop-up whatsoever
      o If I recall correctly, it fails interface consistency but passes
        controllability and non-blocking. The output is correct. It's
        just that no pop-up is produced. When you use the bddhisc
        algorithms, however, there /is/ a pop-up.


rjl: perhaps I should set the hisc to give pop up if no counter
example always when things fail?


- make sure I remove the debug output


- test the per subsystem checks as well.  for bi-level, just chest pop
  ups.  set info for what to test. indiovidal and checkall, reg and
  bdd.
- then test multi-level for pop ups, and then correctness.


Bi-level testing
================

- do per-subsystem and check all, and individual checks. bdd and non-bdd
  + make sure correct pop only

tested all for passing
tested failures: intf con (not ld intf) low and low lwnb, lw cont low,
high lwnb, intf con (not ld intf) high, 



Multi-level testing
===================

- check for correct result
- do per-subsystem and check all, and individual checks. bdd and non-bdd
  + make sure correct pop

testing all for passing
tested failures pop ups: nb and icnsist (not ld intf), lw cont


Node1: Interface consistent condition Point 6 check failed state:

