Difference between revisions of "Repository transition"

From Einstein Toolkit Documentation
Jump to: navigation, search
Line 1: Line 1:
 
Arrangements should go into one git repository each, except where noted:
 
Arrangements should go into one git repository each, except where noted:
  
 +
EinsteinToolkit:
 
* EinsteinAnalysis
 
* EinsteinAnalysis
 
* EinsteinBase
 
* EinsteinBase
Line 9: Line 10:
 
* EinsteinUtils
 
* EinsteinUtils
  
 +
Cactus:
 
* CactusBase - done
 
* CactusBase - done
 
* CactusConnect - done
 
* CactusConnect - done
Line 20: Line 22:
 
* CactusWave
 
* CactusWave
  
 +
PITTNullCode:
 
* PITTNullCode - done
 
* PITTNullCode - done
  
 +
TAT:
 
* TAT
 
* TAT
  
 +
Other:
 
* incoming
 
* incoming
 
* manifest
 
* manifest

Revision as of 09:00, 30 July 2014

Arrangements should go into one git repository each, except where noted:

EinsteinToolkit:

  • EinsteinAnalysis
  • EinsteinBase
  • EinsteinEOS
  • EinsteinEvolve: LegoExcision: out, NewRad -> EinsteinNumerical/NewRad, GRHydro -> GRHydro arrangement
  • EinsteinInitialData/GRHydro_InitData -> GRHydro arrangement
  • EinsteinInitialData
  • EinsteinUtils

Cactus:

  • CactusBase - done
  • CactusConnect - done
  • CactusElliptic - done
  • CactusExamples
  • CactusIO - done
  • CactusNumerical (TestLocalReduce moved in here) - done (except TestLocalReduce)
  • CactusPUGH - done
  • CactusUtils
  • CactusTest, everything stays there, except TestLocalReduce, which moves to CactusNumerical (next to LocalReduce) - done (except TestLocalReduce)
  • CactusWave

PITTNullCode:

  • PITTNullCode - done

TAT:

  • TAT

Other:

  • incoming
  • manifest
  • pyGWAnalysis
  • tools
  • VizTools/CarpetHDF5
  • VizTools/CarpetN5
  • VizTools/DataVaultXVSutils
  • flesh