Repository transition
Revision as of 08:40, 30 July 2014 by 132.236.6.166 (talk)
Arrangements should go into one git repository each, except where noted:
- EinsteinAnalysis
- EinsteinBase
- EinsteinEOS
- EinsteinEvolve: LegoExcision: out, NewRad -> EinsteinNumerical/NewRad, GRHydro -> GRHydro arrangement
- EinsteinInitialData
- EinsteinUtils
- incoming
- manifest
- pyGWAnalysis
- tools
- VizTools/CarpetHDF5
- VizTools/CarpetN5
- VizTools/DataVaultXVSutils
- CactusBase - done
- CactusElliptic - done
- CactusIO - done
- CactusNumerical (TestLocalReduce moved in here) - done (except TestLocalReduce)
- CactusUtils
- TAT
- flesh
- PITTNullCode - done
- CactusConnect - done
- EinsteinInitialData/GRHydro_InitData -> GRHydro arrangement
- CactusExamples
- CactusTest, everything stays there, except TestLocalReduce, which moves to CactusNumerical (next to LocalReduce) - done (except TestLocalReduce)
- CactusWave
- CactusPUGH - done
