Repository transition

From Einstein Toolkit Documentation
Revision as of 09:00, 30 July 2014 by 132.236.6.166 (talk)
Jump to: navigation, search

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
Retrieved from "https://docs.einsteintoolkit.org/et-docs/index.php?title=Repository_transition&oldid=3736"