1. 01 May, 2009 7 commits
  2. 30 Apr, 2009 1 commit
  3. 29 Apr, 2009 6 commits
  4. 28 Apr, 2009 1 commit
  5. 27 Apr, 2009 2 commits
  6. 24 Apr, 2009 2 commits
  7. 23 Apr, 2009 3 commits
  8. 22 Apr, 2009 8 commits
  9. 21 Apr, 2009 4 commits
  10. 20 Apr, 2009 3 commits
  11. 17 Apr, 2009 3 commits
    • Leigh B. Stoller's avatar
      Add a "regression" mode to both the old assign_wrapper and the new · ecb66ab5
      Leigh B. Stoller authored
      mapper wrapper. In regression mode, the wrapper/mapper proceeds
      normally, creating a .vtop file, and then running assign with a fixed
      seed. If the wrapper and the mapper agree on the .vtop file, then the
      solution from assign should be identical.
      
      The wrapper/mapper then proceeds normally, reserving resources and
      making all the DB changes. Needless to say, this has to be on a
      private copy of the database, with all nodes free. Creating that DB
      was a tale in its own right.
      
      At completion, call the existing BackupPhysicalState() function that
      we use in swapmod, and write all the physical tables we have changed
      (just the rows corresponding to the experiment of course). The delete
      all that state, and free the nodes.
      
      If everything is working correctly, those physical tables should be
      identical when created by the mapper or the wrapper.
      
      Of course, its not quite there yet. I have a few things to fix up
      before diff -r produces no results.
      ecb66ab5
    • Leigh B. Stoller's avatar
      Move the initialization of some network agents of assign_wrapper and · 5f5452e1
      Leigh B. Stoller authored
      into a function here, which is now called from tbprerun.
      5f5452e1
    • Leigh B. Stoller's avatar
      A whole bunch of changes for debugging the new assign_wrapper code. · 877aa352
      Leigh B. Stoller authored
      In order to run to completion in impotent mode, create new virtual
      node objects, but just don't put them into the DB. This lets the
      mapper keep going all the way to the end without making any actual DB
      changes.
      877aa352