Difference between revisions of "Repository transition"

From Einstein Toolkit Documentation
Jump to: navigation, search
(comment on NewRad)
 
(5 intermediate revisions by 2 users not shown)
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
 
* EinsteinEOS
 
* EinsteinEOS
−
* EinsteinEvolve RH: do we want to keep NewRad in here? It does not really provide evolution from a user's point of few rather it provides a boundary condition (which is implemented by modifying the RHS). It would seem to be more suitable for CactusNumerial (but has the wrong license)
+
* EinsteinEvolve: LegoExcision: out, NewRad -> EinsteinNumerical/NewRad, GRHydro -> GRHydro arrangement
 +
* EinsteinInitialData/GRHydro_InitData -> GRHydro arrangement
 
* EinsteinInitialData
 
* EinsteinInitialData
 
* EinsteinUtils
 
* EinsteinUtils
 +
 +
Cactus:
 +
* CactusBase - done
 +
* CactusConnect - done
 +
* CactusElliptic - done
 +
* CactusExamples - done
 +
* CactusIO - done
 +
* CactusNumerical - done
 +
* CactusPUGH - done
 +
* CactusUtils - done
 +
* CactusTest - done
 +
* CactusWave - done
 +
 +
PITTNullCode:
 +
* PITTNullCode - done
 +
 +
TAT:
 +
* TAT
 +
 +
Other:
 
* incoming
 
* incoming
 
* manifest
 
* manifest
Line 14: Line 36:
 
* VizTools/CarpetN5
 
* VizTools/CarpetN5
 
* VizTools/DataVaultXVSutils
 
* VizTools/DataVaultXVSutils
−
* CactusBase
 
−
* CactusElliptic
 
−
* CactusIO
 
−
* CactusNumerical
 
−
* CactusUtils
 
−
* TAT
 
 
* flesh
 
* flesh
−
* PITTNullCode
 
−
* CactusConnect
 
−
* EinsteinInitialData/GRHydro_InitData
 
−
* CactusExamples:
 
−
* CactusTest (GRHydro_InitData goes here, as Test_GRHydro, RH: this is a license conflict. GRHydro_InitData is GPL)
 
−
* CactusWave
 
−
* CactusPUGH
 
−
 
−
== possible conflicting locations ==
 
−
* it would make sense to keep thorn X and its TestX thorn in the same repository. They should then not be split up into X in EinsteinEvolve and TestX in Cactus Test. This affects:
 
−
** GRHydro and GRHydro_Init_Data
 
−
** MoL and TestMoL
 
−
** Carpet and its Test thorns (currently Carpet / CarpetExtra arrangements)
 
−
In particular for the case of GRHydro, GRHydro itself has had many more frequent changes requiring updates to test data than GRHydro_Init_Data so it makes sense to keep the test parfiles and test data with GRhydro rather than with GRHydro_Init_Data (the future Test_GRHydro).
 

Latest revision as of 17:23, 4 August 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 - done
  • CactusIO - done
  • CactusNumerical - done
  • CactusPUGH - done
  • CactusUtils - done
  • CactusTest - done
  • CactusWave - done

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=3737"