A15     A19      A33     A35     A37     A52     A68     A69
------------------------------------------------------------------------     
Prob1   1550    2000     NA      1550    1700*   1700    1450    1450
Prob2   558681  538826           659808  429817  407034  403792  394418
Prob3   87494   CRDMP            LONG    37575   HF      38530   37209
Prob4   77626   LONG             LONG    68828*  HF      71809   69677 
Prob5   48759   LONG             LONG    48102*  HF      50744   46895
Prob6   50380   LONG             LONG    PE      HF      52977   46994
Prob7   58581   LONG             LONG    51382*  HF      52710   50630
Prob8   58229   LONG             LONG    PE      HF      53631   52736
Prob9   152187  LONG             LONG    PE      HF      155336  139906
Prob10  129212  LONG             LONG    PE      HF      89935   90040
Prob11  68317   LONG             LONG    63366*  HF      66887   70934
Prob12  125577  LONG             LONG    PE      HF      122788  130329 


NOTE: * Prob 1 and Prob2 are the examples posted on the website. 
      * A19 and A68 are developed on Linux/Unix, the others are on Windows.
      * Not fair to compare CPU time since they are on different platforms.
      * The run time for A15 and A68 is less than 1 minute while A69 runs more than 2 h for most cases (some cases more than 1 day)

LONG: Running too long, not completed after more than 2 hours. The program
      does not print out any messages on its current state.

HF  : Running long and writing out very huge file, have to terminate it.
NA  : Not able to run the program.
PE  : Parser error


Comments
========
A15: stable and robust. Wrong output format. In the schedule output 
     section, it prints out TAM_width,  BIST resources which are
     not needed. 

     GUI not working.

        The output on the end test time is inconsistent with the example shown in the document. 
        
        i.e. 
        BIST 		core_1 test_2	(700,900)
	External	core_1 test_1	(900,1200)

        Overlapping end test time between test_1 and test_2. A legal schedule
        can be:    
        BIST 		core_1 test_2	(700,899)
	External	core_1 test_1	(900,1199) 

A19: Only runs through the two open testcases.
     Working GUI for the two testcases.

A33: Can not find a working executable.

A35: Only runs through the two open testcases.
     No GUI.

A37: Written in Phyton. Have to install Phyton to run. 
     Parser errors in most cases. GUI works for prob2 and prob3, though
     ugly and not useful. Do not print out total schedule length for
     Prob1, 4, 5, 7, 11 (print out Test_time None) 

        The output on the end test time is inconsistent with the example shown in the document.  
        
        i.e. 
        BIST 		core_1 test_2	(700,900)
	External	core_1 test_1	(900,1200)

        Overlapping end test time between test_1 and test_2. A legal schedule
        can be:    
        BIST 		core_1 test_2	(700,899)
	External	core_1 test_1	(900,1199) 

     
A52: Only runs through the two open testcases.
     Working GUI for the two testcases. Can not resize.

A68: Stable and robust. Seems like no preamption support.
     No GUI.

A69: Takes a long time time to run (simulated annealing), but since it
     prints out the status, we can expect that it will finish. 
     

     GUI not working. 

Only A15, A68, A69 run through all the testcases and produce correct
schedules.