== 06-28-2011 == 

 * we are re-merging the minidvodbs of ThreePi into ThreePi.V3 on ipp004

 * we have started LAP dvodbs on ipp005:
 
{{{
add.minidvodb LAP.ThreePi.20110621 LAP.THREEPI.20110621.MINI LAP.THREEPI.20110621 1 GPC1
add.label LAP.ThreePi.20110621
survey.add.addstar LAP.ThreePi.test LAP.THREEPI.20110621 LAP.ThreePi.20110621 cam
}}}
This queues up stripe 82 LAP.   Once this is done, I will rotate to a new minidvodb_id, and then add in the LAP.ThreePi.20110621 label. 

minidvodb_id = 764 will contain just stripe 82

 == 07-28-2011 ==

  * heather's not very good about updating this.  We have several dvodbs that we are building:
  * on ipp004
    * ThreePi.V3
      * contains the original minidvodbs (ThreePi), as well as has queued up all the new destreaked ones
      * ThreePi.V1.Mini - these are the original minidvodbs merged into threePi.V3 - we may consider moving them to ipp005 to free up space
      * ThreePi.V2 is deleted - it got corrupted, there was no backup
      * ThreePi.V2.Mini is being moved over to ipp005 in case we need it and also to free space on ipp004.
    * SAS.201107  (deprecated)
    * SAS.FootPrint
    * SAS2.12
    * SAS2.123  
  * on ipp005
    * LAP (what was available on cam/staticsky for LAP.20110621
    * ThreePi.V3.20110707.bak - contains all the merged minidvodb from ThreePi.124 through ThreePi.340 (excluding ThreePi.331, it refuses to merge, it is corrupted somehow)
    * ThreePi.V2.Mini