Changes between Version 10 and Version 11 of assign+


Ignore:
Timestamp:
Aug 7, 2013 11:14:07 AM (7 years ago)
Author:
sunshine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • assign+

    v10 v11  
    3131      * OUTPUT: success or failure of allocation, time the allocation took, number of nodes and interswitch links allocated
    3232* '''runtests.pl'''
    33       * PURPOSE: run a number of tests with ''assign'' and ''assign+''
     33      * PURPOSE: run a number of tests with ''assign'' and ''assign+''. The tests we run are the following:
     34           t1. ''assign'' with given ''ptopfile'' and ''topfile''
     35           t2. ''assign+'' with given ''ptopfile'' and ''topfile''
     36           t3. ''assign'' with given ''ptopfile'' and modified ''topfile'' to remove fixed nodes
     37           t4. ''assign+'' with given ''ptopfile'' and modified ''topfile'' to remove fixed nodes
     38           t5. ''assign'' with given ''ptopfile'' and modified ''topfile'' to remove fixed nodes, and then include fixed nodes and fixed interfaces from the output of ''assign+'' in step t4
    3439      * INPUT: a file containing lines with ''ptopfile'' and ''topfile''
    3540      * OUTPUT: file ''testresults'' that contains performance of these two allocation algorithms for each line of input
     
    3843      * INPUT: name of the results file
    3944      * OUTPUT: statistics about successes and failures of ''assign'' and ''assign+''. The code also produces files that contain inputs that lead to following potentially anomalous cases:
    40           * ''checktests'' - ''assign+'' failed and ''assign'' didn't
    41           * ''failedtests'' - both ''assign+'' and ''assign'' failed
    42           * ''weirdtests'' - ''assign+'' succeeded and ''assign'' didn't
    43           * ''impossibletests'' - ''assign+'' succeeded and ''assign'' didn't with fixed nodes from output of ''assign+''. This most often happens because ''assign+'' cannot deal properly with fixed interfaces on links.
     45          * ''checktests'' - ''assign+'' failed and ''assign'' didn't, i.e. t1 was a success and t2 was a failure
     46          * ''failedtests'' - both ''assign+'' and ''assign'' failed, i.e. both t1 and t2 were failures
     47          * ''weirdtests'' - ''assign+'' succeeded and ''assign'' didn't, i.e. t1 was a failure and t2 and t5 were a success
     48          * ''impossibletests'' - ''assign+'' succeeded and ''assign'' didn't with fixed nodes from output of ''assign+'',  i.e. t1 was a failure, t2 was a success and t5 was a failure. This most often happens because ''assign'' cannot deal properly with fixed interfaces on links.
    4449
    4550Additionally, the folder contains a version of ''assign'' I have used in testing, that will run on boss. It also contains two sets of test cases:
     
    5156== Expinfotests ==
    5257
    53 There were total of 109,326 tests
     58There were total of 109,326 tests. Historically, in real operation some of these allocations succeeded and some failed.
    5459
    5560||Category|| Count|| Percentage || Reason ||