Commits April 2011

commits@lists.einsteintoolkit.org

12 participants
208 discussions

[svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 52)
by knarf＠cct.lsu.edu 11 Apr '11

11 Apr '11

User: knarf Date: 2011/04/11 10:18 AM Modified: / ET.tex Log: mark spinning BH for Peter File Changes: Directory: / ============ File [modified]: ET.tex Delta lines: +1 -1 =================================================================== --- ET.tex 2011-04-11 14:54:30 UTC (rev 51) +++ ET.tex 2011-04-11 15:18:56 UTC (rev 52) @@ -1467,7 +1467,7 @@ \section{Examples\pages{0.5 Frank}} -\subsection{Spinning BH\pages{2 Bruno}} +\subsection{Spinning BH\pages{2 Peter}} \subsection{BBH\pages{2 Bruno}}

1 0

[svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 51)
by bcmsma＠astro.rit.edu 11 Apr '11

11 Apr '11

User: bmundim Date: 2011/04/11 09:54 AM Modified: / ET.tex Log: An update to initial data section (by Josh/Bruno). File Changes: Directory: / ============ File [modified]: ET.tex Delta lines: +80 -34 =================================================================== --- ET.tex 2011-04-11 08:32:32 UTC (rev 50) +++ ET.tex 2011-04-11 14:54:30 UTC (rev 51) @@ -659,63 +659,109 @@ general relativistic simulations, including both vacuum and hydrodynamical configurations. These include modules used primarily for testing of various components, as -well as physically motivated configurations that e.g.\ describe single or -binary black holes and/or neutron stars. Many of the modules +well as physically motivated configurations that +describe, for example, single or binary black holes and/or neutron stars. +Many of the modules are self-contained, consisting of either all the code to generate exact initial solutions or the numerical tools required to construct solutions known semi-analytically. Others, though, require the installation of other numerical software packages that are included in the toolkit as external -libraries. One example is the {\tt TwoPunctures} +libraries. One example is the \codename{TwoPunctures} module~\cite{Ansorg:2004ds}, commonly used in numerical relativity to generate binary black hole data, which makes use of the GNU Scientific Library [GSL;~\cite{GSL:web,Galassi:2009}]. Several modules have also been implemented to read in datafiles generated by -the {\tt Lorene code}~\cite{Lorene:web,Gourgoulhon:2000nn}. +the {\tt Lorene code}~\cite{Lorene:web,Gourgoulhon:2000nn}. -Initial data setup is in most cases clearly separated by the following +Initial data setup is in most cases clearly separated from the following evolution. Typically, initial data routines provide the data in form of the quantities defined in the Base modules (see section~\ref{sec_base_modules}), -while the evolution modules may convert these quantities to quantities +and the evolution modules will convert these quantities to quantities used for the evolution later. For example, an initial data module must supply $g_{ij}$, the spatial 3-metric, and $K_{ij}$, the extrinsic curvature. -The evolution scheme however, typically makes use of the BSSN formalism. The conversion between the physical and conformal metric and extrinsic -curvature is handled solely within evolution modules. Optionally, many -initial data modules also supply values +curvature is handled solely within evolution modules, which are responsible for calculating the conformally related three metric $\tilde{\gamma}_{ij}$, the conformal factor $\psi$, the conformal traceless extrinsic curvature $\tilde{A}_{ij}$, and the trace of the extrinsic curvature $K$, as well as initializing the BSSN variable $\tilde{\Gamma}^i$ should that be the evolution formalism chosen. +Optionally, many initial data modules also supply values for the lapse and shift vector, and in some cases time derivatives as well. -The initial data routines currently implemented include the following modules. +It is important to note, though, that many dynamical calculations typically run better from initial gauge choices set by ansatz rather than those derived from stationary approximations that are incompatible with the gauge evolution equations. In particular, conformal thin-sandwich initial data for binaries include solutions for the lapse and shift that are frequently replaced by simpler analytical values that lead to more circular orbits under standard `moving puncture' gauge conditions (see, e.g., \cite{Etienne:???} and other works). +\subsubsection{Simple Vacuum initial data} + Vacuum spacetime tests can be provided by \codename{IDConstraintViolate}, which provides a vacuum spacetime explicitly violating the constraint equations, and -\codename{Exact}, a set of exact, and possibly Lorentz-boosted spacetimes in -various coordinates. +\codename{Exact}, a set of exact spacetimes in +various coordinates, including Lorentz-boosted versions of traditional solutions.. Vacuum gravitational wave configurations can be obtained by using either -\codename{IDBrillData}, providinga Brill wave spacetime~\cite{Brill:1959zz}, +\codename{IDBrillData}, providing a Brill wave spacetime~\cite{Brill:1959zz}, or \codename{IDLinearWaves}, for a spacetime containing a linear gravitational wave. -Possible black hole configurations include \codename{IDAnalyticBH}, generating -various analyticly known black hole configurations, as well as +Single black hole configurations include \codename{IDAnalyticBH}, which generates +various analytically known black hole configurations, as well as \codename{IDAxibrillBH}, \codename{IDAxiOddBrillBH}, \codename{DistortedBHIVP} -and \codename{RotatingDBHIVP}, generating single black hole systems, distorted in -various different ways. \codename{Meudon\_Bin\_BH} can read in binary black hole -initial data computed by the Lorene~\cite{TODO} code. +and \codename{RotatingDBHIVP}, which perturbed isolated black holes. + +\subsubsection{TwoPunctures: Binary Black Holes and extensions} +A substantial fraction of the published work on the components of the Einstein toolkit involves the evolution of binary black hole systems. +The most widely used routine to generate initial data for these is the \codename{TwoPunctures} code, described originally in \cite{Ansorg:}, which solves the binary puncture equations for a pair of black holes \cite{Brandt:???}. +To do so, one assumes the extrinsic curvature for each black hole corresponds to the Bowen-York form \cite{Bowen:???}, +\begin{eqnarray*} +K_{(n)}^{ij}&=&\frac{3}{2r^2}(P^in^j+P^jn^i-(\gamma^{ij}-n^in^jP^kn_k))\\ +&&+\frac{3}{r^3}(\varepsilon^{ikl}S_kn_ln^j+\varepsilon^{jkl}S_kn_ln^i) +\end{eqnarray*} +where the subscript $(n)$ refers to the contribution from black hole $n=1,2$, the 3-momentum is $P^i$, the BH spin angular momentum is $S_i$, the conformal 3-metric $\gamma^{ij}$ is assumed to be flat, i.e., $\gamma_{ij}=\eta_{ij}$, and $n^i=x^i/r$ is the Cartesian normal vector relative to the position of each BH in turn. This solution automatically satisfies the momentum constraint, and the Hamiltonian constraint may be written as an elliptical equation for the conformal factor ($g_{ij}=\psi^4\gamma_{ij}$): +\begin{eqnarray*} +\Delta \psi+\frac{1}{8}K^{ij}K_{ij}\psi^{-7}=0 +\end{eqnarray*} +Decomposing the conformal factor into a singular analytical term and a regular term $u$, such that +\begin{eqnarray*} +\psi = \frac{m_1}{2r_1}+\frac{m_2}{2r_2}_+u\equiv \frac{1}{\alpha}+u +\end{eqnarray*} +where $m_i$ and $r_i$ are the mass of and distance to each BH, respectively, the Hamiltonian constraint may be written +\begin{eqnarray*} +\Delta u +\left[\frac{1}{8}\alpha^7K^{ij}K_{ij}\right](1+\alpha u)^{-7} +\end{eqnarray*} +subject to the boundary condition $u\rightarrow 1$ as $r\rightarrow\infty$. In Cartesian coordinates, the function $u$ is infinitely differentiable everywhere except the two puncture locations. \codename{TwoPunctures} resolves this problem by performing a coordinate transformation modeled on confocal elliptical/hyperbolic coordinates, which transforms the spatial domain into a finite cube with the puncture locations mapped to two parallel edges, as can be seen in Fig.~\ref{fig:TP_BHNS_coordinates}. Since $u$ is smooth everywhere in the interior of the remapped domain, expansions into modes in these coordinates are {\em spectrally convergent}, and thus capable of extremely high accuracy. In practice, the field is expanded into Chebyshev modes in the quasi-elliptical and quasi-hyperbolic coordinates, and in Fourier modes around the axis connecting the two BHs. The elliptic solver uses a stabilized biconjugate gradient method to achieve rapid solutions. + +\begin{figure} + \label{fig:TP_BHNS_coordinates} + \centering\includegraphics[width=0.5\textwidth]{TwoPunctures_grid_BHNS}\\ + \caption{Example of a TwoPunctures coordinate system for BH-NS binary initial data} +\end{figure} + + \codename{Meudon\_Bin\_BH} can read in binary black hole +initial data computed by the Lorene~\cite{Lorene:web,Gourgoulhon:2000nn} code. Finally, the most used type of black hole initial data is provided by the module \codename{TwoPunctures}, which generates accurate binary black-hole initial data. Initial data to test different parts of hydrodynamics evolution systems can -be provided by \codename{GRHydro\_InitData}, e.g.\ for shock tests, +be provided by \codename{GRHydro\_InitData}, for example, initial data for shock tests, \codename{Hydro\_InitExcision} for tests involving hydro-excision, \codename{TOVSolver} for Tolman-Oppenheimer-Volkov type neutron star initial data, \codename{Meudon\_Bin\_NS} and \codename{Meudon\_Mag\_NS} read in binary and magnetized neutron star data computed using Lorene, respectively. Finally, the \codename{TwoPunctures} module can also be used to construct neutron star black hole binary initial data, when being coupled with \codename{TOVSolver}. -\begin{figure} - \label{fig:TP_BHNS_coordinates} - \centering\includegraphics[width=0.5\textwidth]{TwoPunctures_grid_BHNS}\\ - \caption{Example of a TwoPunctures coordinate system for BH-NS binary initial data} -\end{figure} +We turn our attention next to a brief discussion of the capabilities of each +of the modules mentioned earlier, as well as their particular implementation. + +%\subsubsection{IDConstraintViolate} +%\subsubsection{Exact} +%\subsubsection{IDBrillData} +%\subsubsection{IDLinearWaves} +%\subsubsection{IDAnalyticBH} +%\subsubsection{IDAxibrillBH} +%\subsubsection{IDAxiOddBrillBH} +%\subsubsection{DistortedBHIVP} +%\subsubsection{RotatingDBHIVP} +%\subsubsection{Meudon\_Bin\_BH} +%\subsubsection{Meudon\_Bin\_NS} +%\subsubsection{Meudon\_Mag\_NS} +%\subsubsection{GRHydro\_InitData} +%\subsubsection{Hydro\_InitExcision} +%\subsubsection{TOVSolver} +%\subsubsection{TwoPunctures} + \subsection{Equation of States}\pages{1 Christian} \subsection{Spacetime Curvature and Hydrodynamics Evolution} @@ -1468,16 +1514,16 @@ of spacetime~\ref{eq:kasner}, along with the associated error for a sequence of time resolutions. -\begin{figure} -\includegraphics[width=0.45\textwidth]{kasner.png} -\includegraphics[width=0.45\textwidth]{err.png} -\caption{Left: the evolution of a vacuum spacetime of the type~\ref{eq:gowdyT3}, -with $P=Q=\lambda=0$; the initial data are chosen as -$\gamma_{ij}=\delta_{ij}$ and $K_{ij}={\rm diag}(-2/3,-2/3,1/3)$. -Right: the numerical error for a sequence of four time resolutions $dt=[0.0125,0.025,0.05,0.1]$; -the errors are scaled according to the expectation for fourth-order convergence. -\label{fig:kasner}} -\end{figure} +%\begin{figure} +%\includegraphics[width=0.45\textwidth]{kasner.png} +%\includegraphics[width=0.45\textwidth]{err.png} +%\caption{Left: the evolution of a vacuum spacetime of the type~\ref{eq:gowdyT3}, +%with $P=Q=\lambda=0$; the initial data are chosen as +%$\gamma_{ij}=\delta_{ij}$ and $K_{ij}={\rm diag}(-2/3,-2/3,1/3)$. +%Right: the numerical error for a sequence of four time resolutions $dt=[0.0125,0.025,0.05,0.1]$; +%the errors are scaled according to the expectation for fourth-order convergence. +%\label{fig:kasner}} +%\end{figure} \section{Future Work\pages{1 Frank}}

1 0

[svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 50)
by eloisa.bentivegna＠aei.mpg.de 11 Apr '11

11 Apr '11

User: bentivegna Date: 2011/04/11 03:32 AM Modified: / ET.tex Log: Added text and two figures for the Kasner example. Also included reference to local_bibtex/references.bib. File Changes: Directory: / ============ File [modified]: ET.tex Delta lines: +49 -3 =================================================================== --- ET.tex 2011-04-11 05:05:01 UTC (rev 49) +++ ET.tex 2011-04-11 08:32:32 UTC (rev 50) @@ -1431,9 +1431,55 @@ \subsection{Collapse\pages{2 Christian}} Show TOV collapse and BH formation -\subsection{Cosmology\pages{2 Eloisa}} -Convergence +\subsection{Cosmology} +The Einstein Toolkit is not only designed to evolve compact-object +spacetimes, but it is also capable of solving the initial-value +problem for spacetimes with radically different topology and global +properties. In the following we illustrate the evolution of an +initial-data set representing a constant-$t$ section of a +spacetime from the Gowdy $T^3$ class~\cite{Gowdy71,New98}; models in +this class have the line element: +\begin{equation} +\label{eq:gowdyT3} +ds^2=\tau^{-1/2}e^{\lambda/2}(-d\tau^2+dz^2)+\tau[e^P(dx+Qdy)^2+e^{-P}dy^2] +\end{equation} +defined on a 3-torus $-x_0 \leq x \leq x_0$, $-y_0 \leq y \leq y_0$, +$-z_0 \leq z \leq z_0$, with the functions $P$, $Q$ and $\lambda$ to be +determined by the Einstein equations. For $P=Q=\lambda=0$, a coordinate +transformation $t=4/3 \tau^{3/4}$ (plus a rescaling of the spatial +coordinates) casts the line element into the form: +\begin{equation} +\label{eq:kasner} +ds^2=-dt^2+t^{4/3}(dx^2+dy^2)+t^{-2/3}dz^2 +\end{equation} +which represents the familiar Kasner spacetime for a homogeneous but +anisotropically expanding universe. In the 3+1 decomposition described +above, this reads: +\begin{widetext} +\begin{eqnarray} +\alpha(t) &=& 1 \\ +\beta^i(t) &=& 0 \\ +\gamma_{ij}(t) &=& {\rm diag}(t^{4/3},t^{4/3},t^{-2/3}) \\ +K_{ij}(t) &=& - {\rm diag}(\frac{2}{3} t^{4/3},\frac{2}{3}t^{4/3},\frac{1}{3}t^{-2/3}) +\end{eqnarray} +\end{widetext} +In Figure\ref{fig:kasner}, we show the full evolution of the $t=1$ slice +of spacetime~\ref{eq:kasner}, along with the associated error for a sequence of +time resolutions. + +\begin{figure} +\includegraphics[width=0.45\textwidth]{kasner.png} +\includegraphics[width=0.45\textwidth]{err.png} +\caption{Left: the evolution of a vacuum spacetime of the type~\ref{eq:gowdyT3}, +with $P=Q=\lambda=0$; the initial data are chosen as +$\gamma_{ij}=\delta_{ij}$ and $K_{ij}={\rm diag}(-2/3,-2/3,1/3)$. +Right: the numerical error for a sequence of four time resolutions $dt=[0.0125,0.025,0.05,0.1]$; +the errors are scaled according to the expectation for fourth-order convergence. +\label{fig:kasner}} +\end{figure} + + \section{Future Work\pages{1 Frank}} This paper illustrated the current state of the ``Einstein Toolkit'', a collection of freely available and easy to use computational codes @@ -1473,6 +1519,6 @@ \bibliographystyle{amsplain-url} -\bibliography{manifest/einsteintoolkit,local_bibtex/ott_references} +\bibliography{manifest/einsteintoolkit,local_bibtex/ott_references,local_bibtex/references} \end{document}

1 0

[svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 49)
by knarf＠cct.lsu.edu 10 Apr '11

10 Apr '11

User: knarf Date: 2011/04/11 12:05 AM Added: /figures/ TwoPunctures_grid_BHNS.pdf Modified: / ET.tex Log: work on several sections, especially 2-4 Directory Changes: Directory: /svn:mime-type/ ========================== + application/pdf File Changes: Directory: / ============ File [modified]: ET.tex Delta lines: +108 -62 =================================================================== --- ET.tex 2011-04-09 21:11:24 UTC (rev 48) +++ ET.tex 2011-04-11 05:05:01 UTC (rev 49) @@ -118,7 +118,7 @@ \cite{Baker:2006vn,Campanelli:2007ew,HolleyBockelmann:2007eh, Pollney:2007ss,Lousto:2007db,Lousto:2008dn} and references therein), post-Newtonian (PN) and numerical waveform comparisons and waveform -template generation~(e.g., \cite{Baker:2006ha, +template generation~(e.g.,~\cite{Baker:2006ha, Husa:2007rh,Baumgarte:2006en,Buonanno:2006ui, Hannam:2007wf,Gopakumar:2007vh, Campanelli:2008nk, Buonanno:2007pf, Ajith:2007kx} and references @@ -133,8 +133,8 @@ It is remarkable that many of the successful techniques used to evolve binary BHs have proven to be equally applicable to merging BH-NS and -NS-NS binaries, allowing for the first full GR simulations of these systems (e.g., -\cite{Shibata:2006bs,Shibata:2006ks,Loeffler06a,Shibata:2007zm, +NS-NS binaries, allowing for the first full GR simulations of these systems +(e.g.,~\cite{Shibata:2006bs,Shibata:2006ks,Loeffler06a,Shibata:2007zm, Etienne:2007jg,Baiotti:2008ra,Duez:2008rb}), and spured a lot of activity also in this field~\todo{cite}. @@ -142,7 +142,7 @@ spacetimes has been carried out in multi-dimensional settings, focusing on BH accretion processes and relativistic jet production and evolution, and has yielded results since the mid 1990s -(e.g., \cite{font:08}\todo{cite more}). On the other hand, GRMHD coupled with +(e.g.,~\cite{font:08}\todo{cite more}). On the other hand, GRMHD coupled with curvature evolution, crucial for modeling large-scale bulk dynamics in compact binary or single-star collapse scenarios, has started to produce astrophysically interesting results only in the @@ -152,10 +152,9 @@ The first full GR simulations of merging NS-NS and/or BH-NS binaries have recently been carried out by groups at Tokyo University -(Shibata~et~al., GRHD and GRMHD e.g., -\cite{Shibata:2006bs,Shibata:2007zm,Shibata:2003ga,Shibata:2005ss,Shibata:2006nm,Yamamoto:2008js}), at UIUC (Shapiro and -collaborators, including co-PI Faber, e.g., -\cite{Etienne:2007jg,Liu:2008xy}), LSU (Lehner et al., +(Shibata~et~al., GRHD and GRMHD +e.g.,~\cite{Shibata:2006bs,Shibata:2007zm,Shibata:2003ga,Shibata:2005ss,Shibata:2006nm,Yamamoto:2008js}), at UIUC (Shapiro and +collaborators, including co-PI Faber, e.g.,~\cite{Etienne:2007jg,Liu:2008xy}), LSU (Lehner et al., \cite{Anderson:2007kz,Anderson:2008zp}), Caltech-Cornell (Duez et al.~\cite{Duez:2008rb}), and at the AEI and Sissa~(Rezzolla and collaborators, \cite{Baiotti:2008ra,Loeffler06a}). The first simulations in 3D GRHD @@ -163,10 +162,9 @@ by co-PI Ott and collaborators \cite{ott:07prl,ott:07cqg} and by Shibata~et~al.~\cite{shibata:053D}. The collapse of rotating, hypermassive NSs to \bh{s} has been studied in 2D and 3D GR by -Shibata~et~al.~(GRHD/GRMHD, Tokyo, e.g., -\cite{shibata:06,shibata:00}), Shapiro, Duez, and collaborators (GRMHD, -UIUC, e.g., \cite{Duez:2005sf,duez:06}), and by Baiotti, Rezzolla~et~al. -(GRHD, AEI/LSU, e.g., \cite{Baiotti04,baiotti:05, +Shibata~et~al.~(GRHD/GRMHD, Tokyo, e.g.,~\cite{shibata:06,shibata:00}), Shapiro, Duez, and collaborators (GRMHD, +UIUC, e.g.,~\cite{Duez:2005sf,duez:06}), and by Baiotti, Rezzolla~et~al. +(GRHD, AEI/LSU, e.g.,~\cite{Baiotti04,baiotti:05, baiotti:07}). Simulations of nonaxisymmetric instabilities in rapidly rotating polytropic \ns{} models have been carried out in full GR by Shibata~et~al.~\cite{shibata:00}, @@ -196,31 +194,36 @@ \subsection{Scientific} -While the above list of studies represents an ensemble of breakthrough +While the list of studies mentioned in the introduction represent +an ensemble of breakthrough simulations that have significantly advanced the modeling of relativistic astrophysical systems, all simulations are presently missing one or multiple physical ingredients or are lacking the numerical precision to accurately and realistically model the large-scale and small-scale dynamics of their target systems. +One of the aims of the Einstein Toolkit is to provide or extend +some of these missing ingredients in the course of its development. +The three most important of all possible additions, as deemed by +the Einstein Toolkit members, are listed below. -{\bf MHD} Many studies, in particular those concerned with +\begin{itemize} + \item{\bf MHD}. Many studies, in particular those concerned with massive star collapse, binary NS-NS or BH-NS, and rotational - nonaxisymmetric instabilities are still performed in pure GRHD\@. + nonaxisymmetric instabilities, are still performed in pure GRHD\@. Without doubt, these systems must be simulated with GRMHD to capture the effects of magnetic fields that in many cases will alter the simulation outcome on a qualitative level and may be the driving mechanisms behind much of the observable EM signature - from GRBs (e.g., \cite{wb:06}) - and magneto-rotationally exploding core-collapse supernovae (e.g., - \cite{Burrows:2007yx}). In addition, all simulations that have + from GRBs (e.g.,~\cite{wb:06}) + and magneto-rotationally exploding core-collapse supernovae + (e.g.,~\cite{Burrows:2007yx}). In addition, all simulations that have taken into account magnetic fields are still limited to the ideal MHD approximation (perfect conductivity). Non-ideal GRMHD schemes are just becoming - available~(e.g., \cite{Palenzuela:2008sf,DelZanna:2007pk}). + available~(e.g.,~\cite{Palenzuela:2008sf,DelZanna:2007pk}). - - {\bf Equation of state (EOS), microphysics, and radiation + \item {\bf Equation of state (EOS), microphysics, and radiation transport}. All presently published 3D GR(M)HD simulations, with the sole exception of the work by co-PI Ott on massive star collapse, relied on a simple zero-temperature polytropic description of @@ -230,8 +233,8 @@ relativistic astrophysical systems. The inclusion of finite-temperature EOS, derived from the microphysical descriptions of high-density matter, will lead to qualitatively different and much - more astrophysically reliable results (see, e.g., - \cite{ott:07prl}). In addition, most GR(M)HD studies are + more astrophysically reliable results (see, e.g.,~\cite{ott:07prl}). + In addition, most GR(M)HD studies are neglecting transport of neutrinos and photons and their interactions with matter. Neutrinos in particular play a crucial role in core-collapse supernovae and in @@ -240,43 +243,66 @@ incorporating neutrino and/or photon transport and interactions in approximate ways \cite{ott:07prl,Farris:2008fe}. - {\bf High-order schemes and AMR\@}. Numerical accuracy is a + \item {\bf High-order schemes and AMR\@}. Numerical accuracy is a central issue in long-term GR(M)HD simulations and must be addressed by a combination of (1) adaptive mesh refinement (AMR), focusing grid points to regions where most resolution is needed, and (2), - high-order numerical techniques. Presently, a large number of GRMHD - calculations are still performed without AMR and, due to physically - limited computational resources, may be underresolving the dynamics - in the systems under investigation. In addition, most GRMHD - schemes, while implementing high-resolution shock-capturing methods, + high-order numerical techniques. + + AMR codes, e.g., the Carpet driver, + are available and coupling of existing and future GRMHD codes + with AMR must be facilitated in order to avoid underresolving the + dynamics in the systems under investigation. AMR methods are, + on the other hand, much more complicated than uniformly distributed + mesh methods, and require sophisticated algorithms to make use of + massively parallel systems efficiently. + + While AMR can increase resolution near regions of interest within + the computational domain, it does not increase the convergence + order of the underlying numerical methods. Simulations of black holes + can easily make use of high-order numerical methods, with 8th order + of convergence being not uncommon presently. However, + most GRMHD schemes, while implementing high-resolution shock-capturing methods, are still limited to 2nd-order numerical accuracy while performing curvature evolution typically with 4th-order accuracy. Higher order - GRMHD schemes are in use in fixed-background simulations (e.g., - \cite{Tchekhovskoy:2007zn}), but still await implementation in - fully dynamical simulations. AMR codes, e.g., the Carpet driver, - are available and coupling of existing and future GRMHD codes - with AMR must be facilitated. + GRMHD schemes are in use in fixed-background simulations + (e.g.,~\cite{Tchekhovskoy:2007zn}), but still await implementation in + fully dynamical simulations. +\end{itemize} \subsection{Academic and Social} + A primary concern for research groups is securing reliable funding to maintain graduate students and postdoctoral researchers. This goal is easier to achieve if it can be shown that science goals can be attacked directly with less potential of infrastructure problems, one of the goals of the Einstein Toolkit. -In addition, the toolkit provides computer scientists an ideal platform -to perform state-of-the-art research, directly benefiting research in -other areas of science and hereby providing an immediate application -of their research. +While the Einstein Toolkit does have a large group of users, many of them +are not directly collaborating on science problems, and some can even be +seen as competitors. However, all groups agree that sharing the development +of the underlying infrastructure is benefitial for every group and the +progress in science in general. This is achieved by lifting much of the +otherwise necessary burden of creating such an infrastructure off the +research groups' shoulders, while at the same time increasing the amount +of code-review, and by this, code quality. +In addition, the Einstein Toolkit provides computer scientists an +ideal platform to perform state-of-the-art research, which is directly +benefiting research in other areas of science and hereby providing an +immediate application of their research. One of the most prominent +examples within the Einstein Toolkit is the Cactus Computational Toolkit, +a framework developed by computer scientists and now used by researchers +is many other fields. + \section{Design and Strategy\pages{0.5 Frank}} The mechanisms for the development and support of the Einstein Toolkit are -designed to be open, transparent and community driven. All the source code, +designed to be open, transparent and community-driven. The complete source code, documentation and tools included in the Einstein Toolkit are distributed -under open source licenses. The Einstein Toolkit maintains an SVN repository -({\tt svn.einsteintoolkit.org}) with open access which contains software +under open-source licenses. The Einstein Toolkit maintains an version +control system ({\tt svn.einsteintoolkit.org}) with open access which contains software supported by the Einstein Toolkit, the toolkit web pages and documentation. An open wiki for documentation ({\tt docs.einsteintoollkit.org}) has been established where the community @@ -284,45 +310,55 @@ discussion about the toolkit takes place on an open mail list ({\tt users(a)einsteintoolkit.org}). The regular weekly meetings for the Einstein Toolkit are open and the community is invited to -participate, and minutes are recorded and publicly available. The Einstein Toolkit +participate. Meeting minutes are recorded and publicly available as well. +The Einstein Toolkit blog requires users to first request a login, but then can be freely posted to. Any user can post comments to entries already on the blog. The community heavily uses an issue tracking system -({\tt trac.einsteintoolkit.org}), with submissions open to everyone. +({\tt trac.einsteintoolkit.org}), with submissions also open to everyone. -Despite the open design, some actions have to be restricted to a small -group of maintainers. This is true for e.g. administrative tasks like the +Despite this open design, some actions have to be restricted to a small +group of maintainers. This is true for e.g.\ administrative tasks like the setup and maintenance of the services itself, or to avoid large amounts of spam. However, one of the most important tasks of an Einstein Toolkit -Maintainer is also to review and apply patches sent by users, to ensure +Maintainer is to review and apply patches sent by users in order to ensure a high software quality level. Every substancial change or addition to the toolkit has to be reviewed by another Einstein Toolkit Maintainer, -and is generally open for discussion on the users mailing list. Despite this -not being enforced by technically it seems to work pretty well while at the -same time promoting development. +and is generally open for discussion on the users mailing list. This convention, +despite not being technically enforced, works well in practice, and is at the +same time promoting active development. \section{Core Technologies\pages{0.5 Frank}} -\subsection{Cactus Framework\pages{1 Gab}} +\subsection{Cactus Framework\pages{1 Gab/Frank}} The \textbf{Cactus Framework}~\cite{CS_cactus_web,CS_Goodale02a,CS_cactususersguide} is an open source, modular, portable programming environment for collaborative HPC computing, primarily developed at LSU\@. Cactus has a generic parallel computational toolkit with modules providing -parallel drivers, coordinates, boundary conditions, interpolators, +e.g.\ parallel drivers, coordinates, boundary conditions, interpolators, reduction operators, and efficient I/O in different data formats. Generic interfaces are used, making it possible to use external packages and improved modules which are immediately available to its users. Cactus is involved in the NSF Blue Waters consortium for petascale computing, has funding from NSF SDCI to -develop new application level tools for performance and correctness, -as well as the current NSF XiRel award for scalable AMR\@. -\S\ref{broader} describes the growing impact of Cactus in other -application domains. +develop new application level tools for performance and correctness. -\todo{ES: Say something about component structure and component - interfaces; I refer to this in the Carpet subsection below.} +The structure of the Cactus framework is completely modular, with +only a very small core proving the interfaces between modules, +both at compile- and run-time. The Cactus modules, called ``thorns'', +may, and typically do, specify inter-module dependencies, e.g., to share or +extend configuration information, common variables or runtime parameters. +Modules compiled into an executable can remain dormant at run-time. +This usage of modules and a common interface between them, enables researchers +to 1) easily use modules written by others without the need to understand +all details of their implementation, and 2) to write their own modules +without the need to change the source code of other parts of a simulation, +in the (supported) programming language of their choice. +The number of active modules within a typical Cactus simulation ranges +from a few ten to hundereds, often with an extensive set of inter-module +dependencies. The Cactus Framework was developed by the numerical relativity community, and although it is a general component @@ -488,7 +524,7 @@ of complex software systems, and require the use of well defined interfaces. Low-level interoperability within the Einstein Toolkit is provided by the Cactus infrastructure. One example of this is using one module -from within another, e.g. by calling a function within another thorn +from within another, e.g., by calling a function within another thorn independent of programming language used for both the calling and the called function. @@ -595,6 +631,11 @@ $n^\mu$. \end{itemize} +Note that, while this includes definitions for variables used to store information +about magnetic fields, the implementation of an evolution system for magnetic fields +within the Einstein Toolkit is at the time of this publication still in development, and +not yet officially released. + HydroBase also sets up scheduling blocks that organize the main functions which modules of a hydrodynamics code may need. All of those scheduling blocks are optional, however if used, they might simplify existing codes and make them more interoperable. HydroBase itself does @@ -618,8 +659,8 @@ general relativistic simulations, including both vacuum and hydrodynamical configurations. These include modules used primarily for testing of various components, as -well as physically motivated configurations that e.g. -describe single or binary black holes and/or neutron stars. Many of the modules +well as physically motivated configurations that e.g.\ describe single or +binary black holes and/or neutron stars. Many of the modules are self-contained, consisting of either all the code to generate exact initial solutions or the numerical tools required to construct solutions known semi-analytically. Others, though, require the installation of other @@ -662,13 +703,18 @@ \codename{TwoPunctures}, which generates accurate binary black-hole initial data. Initial data to test different parts of hydrodynamics evolution systems can -be provided by \codename{GRHydro\_InitData}, e.g. for shock tests, +be provided by \codename{GRHydro\_InitData}, e.g.\ for shock tests, \codename{Hydro\_InitExcision} for tests involving hydro-excision, \codename{TOVSolver} for Tolman-Oppenheimer-Volkov type neutron star initial data, \codename{Meudon\_Bin\_NS} and \codename{Meudon\_Mag\_NS} read in binary and magnetized neutron star data computed using Lorene, respectively. Finally, the \codename{TwoPunctures} module can also be used to construct neutron star black hole binary initial data, when being coupled with \codename{TOVSolver}. +\begin{figure} + \label{fig:TP_BHNS_coordinates} + \centering\includegraphics[width=0.5\textwidth]{TwoPunctures_grid_BHNS}\\ + \caption{Example of a TwoPunctures coordinate system for BH-NS binary initial data} +\end{figure} \subsection{Equation of States}\pages{1 Christian} @@ -989,7 +1035,7 @@ % Event horizon The event horizon module \codename{EHFinder}~\cite{Diener:2003jc} -evolves a null surface backwards in time given an initial guess (e.g. +evolves a null surface backwards in time given an initial guess (e.g., the last apparent horizon) which will, in the vicinity of an event horizon, converge exponentially to that event horizon. This has to be done after a simulation has already evolved the initial data forward Directory: /figures/ ==================== File [added]: TwoPunctures_grid_BHNS.pdf Delta lines: +0 -0 =================================================================== (Binary files differ) Property changes on: figures/TwoPunctures_grid_BHNS.pdf ___________________________________________________________________

1 0

[svn:einsteintoolkit] Exact/trunk/test/ (Rev. 267)
by roland.haas＠physics.gatech.edu 10 Apr '11

10 Apr '11

User: rhaas Date: 2011/04/10 05:56 AM Modified: /trunk/test/ Schwarzschild_EF.par /trunk/test/Schwarzschild_EF/ alp_3D_diagonal.xg, alp_x_[15][15].xg, alp_xy_[15].asc, alp_xz_[15].asc, alp_y_[15][15].xg, alp_yz_[15].asc, alp_z_[15][15].xg, betax_3D_diagonal.xg, betax_x_[15][15].xg, betax_xy_[15].asc, betax_xz_[15].asc, betax_y_[15][15].xg, betax_yz_[15].asc, betax_z_[15][15].xg, betay_3D_diagonal.xg, betay_x_[15][15].xg, betay_xy_[15].asc, betay_xz_[15].asc, betay_y_[15][15].xg, betay_yz_[15].asc, betay_z_[15][15].xg, betaz_3D_diagonal.xg, betaz_x_[15][15].xg, betaz_xy_[15].asc, betaz_xz_[15].asc, betaz_y_[15][15].xg, betaz_yz_[15].asc, betaz_z_[15][15].xg, gxx_3D_diagonal.xg, gxx_x_[15][15].xg, gxx_xy_[15].asc, gxx_xz_[15].asc, gxx_y_[15][15].xg, gxx_yz_[15].asc, gxx_z_[15][15].xg, gxy_3D_diagonal.xg, gxy_x_[15][15].xg, gxy_xy_[15].asc, gxy_xz_[15].asc, gxy_y_[15][15].xg, gxy_yz_[15].asc, gxy_z_[15][15].xg, gxz_3D_diagonal.xg, gxz_x_[15][15].xg, gxz_xy_[15].asc, gxz_xz_[15].asc, gxz_y_[15][15].xg, gxz_yz_[15].asc, gxz_z_[15][15].xg, gyy_3D_diagonal.xg, gyy_x_[15][15].xg, gyy_xy_[15].asc, gyy_xz_[15].asc, gyy_y_[15][15].xg, gyy_yz_[15].asc, gyy_z_[15][15].xg, gyz_3D_diagonal.xg, gyz_x_[15][15].xg, gyz_xy_[15].asc, gyz_xz_[15].asc, gyz_y_[15][15].xg, gyz_yz_[15].asc, gyz_z_[15][15].xg, gzz_3D_diagonal.xg, gzz_x_[15][15].xg, gzz_xy_[15].asc, gzz_xz_[15].asc, gzz_y_[15][15].xg, gzz_yz_[15].asc, gzz_z_[15][15].xg, kxx_3D_diagonal.xg, kxx_x_[15][15].xg, kxx_xy_[15].asc, kxx_xz_[15].asc, kxx_y_[15][15].xg, kxx_yz_[15].asc, kxx_z_[15][15].xg, kxy_3D_diagonal.xg, kxy_x_[15][15].xg, kxy_xy_[15].asc, kxy_xz_[15].asc, kxy_y_[15][15].xg, kxy_yz_[15].asc, kxy_z_[15][15].xg, kxz_3D_diagonal.xg, kxz_x_[15][15].xg, kxz_xy_[15].asc, kxz_xz_[15].asc, kxz_y_[15][15].xg, kxz_yz_[15].asc, kxz_z_[15][15].xg, kyy_3D_diagonal.xg, kyy_x_[15][15].xg, kyy_xy_[15].asc, kyy_xz_[15].asc, kyy_y_[15][15].xg, kyy_yz_[15].asc, kyy_z_[15][15].xg, kyz_3D_diagonal.xg, kyz_x_[15][15].xg, kyz_xy_[15].asc, kyz_xz_[15].asc, kyz_y_[15][15].xg, kyz_yz_[15].asc, kyz_z_[15][15].xg, kzz_3D_diagonal.xg, kzz_x_[15][15].xg, kzz_xy_[15].asc, kzz_xz_[15].asc, kzz_y_[15][15].xg, kzz_yz_[15].asc, kzz_z_[15][15].xg Log: Exact: move grid points in Schwarzschild_EF away from origin for this we need an even number of points (ie. an odd number of cells) File Changes: Directory: /trunk/test/Schwarzschild_EF/ ======================================== File [modified]: alp_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: alp_x_[15][15].xg Delta lines: <Unavailable> File [modified]: alp_xy_[15].asc Delta lines: <Unavailable> File [modified]: alp_xz_[15].asc Delta lines: <Unavailable> File [modified]: alp_y_[15][15].xg Delta lines: <Unavailable> File [modified]: alp_yz_[15].asc Delta lines: <Unavailable> File [modified]: alp_z_[15][15].xg Delta lines: <Unavailable> File [modified]: betax_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: betax_x_[15][15].xg Delta lines: <Unavailable> File [modified]: betax_xy_[15].asc Delta lines: <Unavailable> File [modified]: betax_xz_[15].asc Delta lines: <Unavailable> File [modified]: betax_y_[15][15].xg Delta lines: <Unavailable> File [modified]: betax_yz_[15].asc Delta lines: <Unavailable> File [modified]: betax_z_[15][15].xg Delta lines: <Unavailable> File [modified]: betay_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: betay_x_[15][15].xg Delta lines: <Unavailable> File [modified]: betay_xy_[15].asc Delta lines: <Unavailable> File [modified]: betay_xz_[15].asc Delta lines: <Unavailable> File [modified]: betay_y_[15][15].xg Delta lines: <Unavailable> File [modified]: betay_yz_[15].asc Delta lines: <Unavailable> File [modified]: betay_z_[15][15].xg Delta lines: <Unavailable> File [modified]: betaz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: betaz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: betaz_xy_[15].asc Delta lines: <Unavailable> File [modified]: betaz_xz_[15].asc Delta lines: <Unavailable> File [modified]: betaz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: betaz_yz_[15].asc Delta lines: <Unavailable> File [modified]: betaz_z_[15][15].xg Delta lines: <Unavailable> File [modified]: gxx_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: gxx_x_[15][15].xg Delta lines: <Unavailable> File [modified]: gxx_xy_[15].asc Delta lines: <Unavailable> File [modified]: gxx_xz_[15].asc Delta lines: <Unavailable> File [modified]: gxx_y_[15][15].xg Delta lines: <Unavailable> File [modified]: gxx_yz_[15].asc Delta lines: <Unavailable> File [modified]: gxx_z_[15][15].xg Delta lines: <Unavailable> File [modified]: gxy_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: gxy_x_[15][15].xg Delta lines: <Unavailable> File [modified]: gxy_xy_[15].asc Delta lines: <Unavailable> File [modified]: gxy_xz_[15].asc Delta lines: <Unavailable> File [modified]: gxy_y_[15][15].xg Delta lines: <Unavailable> File [modified]: gxy_yz_[15].asc Delta lines: <Unavailable> File [modified]: gxy_z_[15][15].xg Delta lines: <Unavailable> File [modified]: gxz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: gxz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: gxz_xy_[15].asc Delta lines: <Unavailable> File [modified]: gxz_xz_[15].asc Delta lines: <Unavailable> File [modified]: gxz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: gxz_yz_[15].asc Delta lines: <Unavailable> File [modified]: gxz_z_[15][15].xg Delta lines: <Unavailable> File [modified]: gyy_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: gyy_x_[15][15].xg Delta lines: <Unavailable> File [modified]: gyy_xy_[15].asc Delta lines: <Unavailable> File [modified]: gyy_xz_[15].asc Delta lines: <Unavailable> File [modified]: gyy_y_[15][15].xg Delta lines: <Unavailable> File [modified]: gyy_yz_[15].asc Delta lines: <Unavailable> File [modified]: gyy_z_[15][15].xg Delta lines: <Unavailable> File [modified]: gyz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: gyz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: gyz_xy_[15].asc Delta lines: <Unavailable> File [modified]: gyz_xz_[15].asc Delta lines: <Unavailable> File [modified]: gyz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: gyz_yz_[15].asc Delta lines: <Unavailable> File [modified]: gyz_z_[15][15].xg Delta lines: <Unavailable> File [modified]: gzz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: gzz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: gzz_xy_[15].asc Delta lines: <Unavailable> File [modified]: gzz_xz_[15].asc Delta lines: <Unavailable> File [modified]: gzz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: gzz_yz_[15].asc Delta lines: <Unavailable> File [modified]: gzz_z_[15][15].xg Delta lines: <Unavailable> File [modified]: kxx_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: kxx_x_[15][15].xg Delta lines: <Unavailable> File [modified]: kxx_xy_[15].asc Delta lines: <Unavailable> File [modified]: kxx_xz_[15].asc Delta lines: <Unavailable> File [modified]: kxx_y_[15][15].xg Delta lines: <Unavailable> File [modified]: kxx_yz_[15].asc Delta lines: <Unavailable> File [modified]: kxx_z_[15][15].xg Delta lines: <Unavailable> File [modified]: kxy_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: kxy_x_[15][15].xg Delta lines: <Unavailable> File [modified]: kxy_xy_[15].asc Delta lines: <Unavailable> File [modified]: kxy_xz_[15].asc Delta lines: <Unavailable> File [modified]: kxy_y_[15][15].xg Delta lines: <Unavailable> File [modified]: kxy_yz_[15].asc Delta lines: <Unavailable> File [modified]: kxy_z_[15][15].xg Delta lines: <Unavailable> File [modified]: kxz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: kxz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: kxz_xy_[15].asc Delta lines: <Unavailable> File [modified]: kxz_xz_[15].asc Delta lines: <Unavailable> File [modified]: kxz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: kxz_yz_[15].asc Delta lines: <Unavailable> File [modified]: kxz_z_[15][15].xg Delta lines: <Unavailable> File [modified]: kyy_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: kyy_x_[15][15].xg Delta lines: <Unavailable> File [modified]: kyy_xy_[15].asc Delta lines: <Unavailable> File [modified]: kyy_xz_[15].asc Delta lines: <Unavailable> File [modified]: kyy_y_[15][15].xg Delta lines: <Unavailable> File [modified]: kyy_yz_[15].asc Delta lines: <Unavailable> File [modified]: kyy_z_[15][15].xg Delta lines: <Unavailable> File [modified]: kyz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: kyz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: kyz_xy_[15].asc Delta lines: <Unavailable> File [modified]: kyz_xz_[15].asc Delta lines: <Unavailable> File [modified]: kyz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: kyz_yz_[15].asc Delta lines: <Unavailable> File [modified]: kyz_z_[15][15].xg Delta lines: <Unavailable> File [modified]: kzz_3D_diagonal.xg Delta lines: <Unavailable> File [modified]: kzz_x_[15][15].xg Delta lines: <Unavailable> File [modified]: kzz_xy_[15].asc Delta lines: <Unavailable> File [modified]: kzz_xz_[15].asc Delta lines: <Unavailable> File [modified]: kzz_y_[15][15].xg Delta lines: <Unavailable> File [modified]: kzz_yz_[15].asc Delta lines: <Unavailable> File [modified]: kzz_z_[15][15].xg Delta lines: <Unavailable> Directory: /trunk/test/ ======================= File [modified]: Schwarzschild_EF.par Delta lines: <Unavailable>

1 0

[svn:einsteintoolkit] www/release-info/ (Rev. 517)
by ian.hinder＠aei.mpg.de 10 Apr '11

10 Apr '11

User: hinder Date: 2011/04/10 05:39 AM Modified: /release-info/ kraken__1_1.log, kraken__2_1.log, kraken__2_2.log Log: Update Kraken results File Changes: Directory: /release-info/ ========================= File [modified]: kraken__1_1.log Delta lines: +10 -13 =================================================================== --- release-info/kraken__1_1.log 2011-04-10 03:46:54 UTC (rev 516) +++ release-info/kraken__1_1.log 2011-04-10 10:39:41 UTC (rev 517) @@ -823,11 +823,11 @@ GRHydro: GRHydro_test_shock_ppm Success: 48 files compared, 17 differ in the last digits GRHydro: GRHydro_test_tov_ppm_ML - Failure: 180 files compared, 83 differ, 7 differ significantly + Success: 180 files compared, 83 differ in the last digits GRHydro: GRHydro_test_tov_ppm_ML_disable_internal_excision - Failure: 180 files compared, 83 differ, 7 differ significantly + Success: 180 files compared, 83 differ in the last digits GRHydro: GRHydro_test_tov_ppm_no_trp_ML - Failure: 180 files compared, 94 differ, 8 differ significantly + Success: 180 files compared, 94 differ in the last digits Hydro_InitExcision: diag_flip_pugh_eno Success: 72 files compared, 59 differ in the last digits Hydro_InitExcision: diag_flip_pugh_ppm @@ -915,9 +915,9 @@ RotatingDBHIVP: test_rdbh Success: 120 files compared, 82 differ in the last digits RotatingSymmetry180: KerrSchild-rotating-180 - Failure: 128 files compared, 108 differ, 38 differ significantly + Failure: 120 files compared, 100 differ, 32 differ significantly RotatingSymmetry90: KerrSchild-rotating-90 - Failure: 128 files compared, 106 differ, 38 differ significantly + Failure: 120 files compared, 98 differ, 32 differ significantly SlabTest: slabtest Success: 1 files identical TOVSolver: test_one_boost_max @@ -1018,8 +1018,8 @@ Summary for configuration sim - Time -> Tue Apr 5 16:42:29 EDT 2011 - Host -> aprun5 + Time -> Sat Apr 9 02:52:43 EDT 2011 + Host -> aprun15 User -> hinder Total available tests -> 171 @@ -1027,19 +1027,16 @@ Runnable tests -> 130 Total number of thorns -> 159 Number of tested thorns -> 40 - Number of tests passed -> 119 + Number of tests passed -> 122 Number passed only to - set tolerance -> 80 - Number failed -> 11 + set tolerance -> 83 + Number failed -> 8 Tests failed: nonstaggered (from CarpetReduce) staggered (from CarpetReduce) Schwarzschild_EF (from Exact) - GRHydro_test_tov_ppm_ML (from GRHydro) - GRHydro_test_tov_ppm_ML_disable_internal_excision (from GRHydro) - GRHydro_test_tov_ppm_no_trp_ML (from GRHydro) halfsphere_pugh_ppm (from Hydro_InitExcision) x_flip_pugh_ppm (from Hydro_InitExcision) x_pugh_ppm (from Hydro_InitExcision) File [modified]: kraken__2_1.log Delta lines: +10 -15 =================================================================== --- release-info/kraken__2_1.log 2011-04-10 03:46:54 UTC (rev 516) +++ release-info/kraken__2_1.log 2011-04-10 10:39:41 UTC (rev 517) @@ -818,11 +818,11 @@ GRHydro: GRHydro_test_shock_ppm Success: 48 files compared, 17 differ in the last digits GRHydro: GRHydro_test_tov_ppm_ML - Failure: 180 files compared, 84 differ, 7 differ significantly + Success: 180 files compared, 84 differ in the last digits GRHydro: GRHydro_test_tov_ppm_ML_disable_internal_excision - Failure: 180 files compared, 84 differ, 7 differ significantly + Success: 180 files compared, 84 differ in the last digits GRHydro: GRHydro_test_tov_ppm_no_trp_ML - Failure: 180 files compared, 95 differ, 8 differ significantly + Success: 180 files compared, 95 differ in the last digits Hydro_InitExcision: diag_flip_pugh_eno Success: 72 files compared, 59 differ in the last digits Hydro_InitExcision: diag_flip_pugh_ppm @@ -916,9 +916,9 @@ RotatingDBHIVP: test_rdbh Success: 120 files compared, 82 differ in the last digits RotatingSymmetry180: KerrSchild-rotating-180 - Failure: 128 files compared, 109 differ, 5 differ significantly + Success: 120 files compared, 102 differ in the last digits RotatingSymmetry90: KerrSchild-rotating-90 - Failure: 128 files compared, 106 differ, 6 differ significantly + Success: 120 files compared, 98 differ in the last digits SlabTest: slabtest Success: 1 files identical TOVSolver: test_one_boost_max @@ -1009,8 +1009,8 @@ Summary for configuration sim - Time -> Tue Apr 5 17:23:59 EDT 2011 - Host -> aprun5 + Time -> Sat Apr 9 03:59:58 EDT 2011 + Host -> aprun15 User -> hinder Total available tests -> 171 @@ -1018,10 +1018,10 @@ Runnable tests -> 124 Total number of thorns -> 159 Number of tested thorns -> 37 - Number of tests passed -> 101 + Number of tests passed -> 106 Number passed only to - set tolerance -> 65 - Number failed -> 23 + set tolerance -> 70 + Number failed -> 18 Tests failed: @@ -1039,15 +1039,10 @@ misner1.2-025 (from AHFinderDirect) recoverML (from AHFinderDirect) Schwarzschild_EF (from Exact) - GRHydro_test_tov_ppm_ML (from GRHydro) - GRHydro_test_tov_ppm_ML_disable_internal_excision (from GRHydro) - GRHydro_test_tov_ppm_no_trp_ML (from GRHydro) halfsphere_pugh_ppm (from Hydro_InitExcision) x_flip_pugh_ppm (from Hydro_InitExcision) x_pugh_ppm (from Hydro_InitExcision) gw3d_McLachlan_ord4_30 (from ML_BSSN_Test) - KerrSchild-rotating-180 (from RotatingSymmetry180) - KerrSchild-rotating-90 (from RotatingSymmetry90) ======================================================================== File [modified]: kraken__2_2.log Delta lines: +10 -15 =================================================================== --- release-info/kraken__2_2.log 2011-04-10 03:46:54 UTC (rev 516) +++ release-info/kraken__2_2.log 2011-04-10 10:39:41 UTC (rev 517) @@ -818,11 +818,11 @@ GRHydro: GRHydro_test_shock_ppm Success: 48 files compared, 17 differ in the last digits GRHydro: GRHydro_test_tov_ppm_ML - Failure: 180 files compared, 84 differ, 7 differ significantly + Success: 180 files compared, 84 differ in the last digits GRHydro: GRHydro_test_tov_ppm_ML_disable_internal_excision - Failure: 180 files compared, 84 differ, 7 differ significantly + Success: 180 files compared, 84 differ in the last digits GRHydro: GRHydro_test_tov_ppm_no_trp_ML - Failure: 180 files compared, 95 differ, 8 differ significantly + Success: 180 files compared, 95 differ in the last digits Hydro_InitExcision: diag_flip_pugh_eno Success: 72 files compared, 59 differ in the last digits Hydro_InitExcision: diag_flip_pugh_ppm @@ -916,9 +916,9 @@ RotatingDBHIVP: test_rdbh Success: 120 files compared, 82 differ in the last digits RotatingSymmetry180: KerrSchild-rotating-180 - Failure: 128 files compared, 109 differ, 5 differ significantly + Success: 120 files compared, 102 differ in the last digits RotatingSymmetry90: KerrSchild-rotating-90 - Failure: 128 files compared, 100 differ, 6 differ significantly + Success: 120 files compared, 92 differ in the last digits SlabTest: slabtest Success: 1 files identical TOVSolver: test_one_boost_max @@ -1009,8 +1009,8 @@ Summary for configuration sim - Time -> Tue Apr 5 19:31:07 EDT 2011 - Host -> aprun5 + Time -> Sat Apr 9 06:13:24 EDT 2011 + Host -> aprun15 User -> hinder Total available tests -> 171 @@ -1018,10 +1018,10 @@ Runnable tests -> 124 Total number of thorns -> 159 Number of tested thorns -> 37 - Number of tests passed -> 101 + Number of tests passed -> 106 Number passed only to - set tolerance -> 65 - Number failed -> 23 + set tolerance -> 70 + Number failed -> 18 Tests failed: @@ -1039,15 +1039,10 @@ misner1.2-025 (from AHFinderDirect) recoverML (from AHFinderDirect) Schwarzschild_EF (from Exact) - GRHydro_test_tov_ppm_ML (from GRHydro) - GRHydro_test_tov_ppm_ML_disable_internal_excision (from GRHydro) - GRHydro_test_tov_ppm_no_trp_ML (from GRHydro) halfsphere_pugh_ppm (from Hydro_InitExcision) x_flip_pugh_ppm (from Hydro_InitExcision) x_pugh_ppm (from Hydro_InitExcision) gw3d_McLachlan_ord4_30 (from ML_BSSN_Test) - KerrSchild-rotating-180 (from RotatingSymmetry180) - KerrSchild-rotating-90 (from RotatingSymmetry90) ========================================================================

1 0

[svn:einsteintoolkit] www/release-info/ (Rev. 516)
by knarf＠cct.lsu.edu 09 Apr '11

09 Apr '11

User: knarf Date: 2011/04/09 10:46 PM Modified: /release-info/ philip__1_1.log, philip__2_1.log, philip__2_2.log Log: update philip testsuite results File Changes: Directory: /release-info/ ========================= File [modified]: philip__1_1.log Delta lines: +16 -24 =================================================================== --- release-info/philip__1_1.log 2011-04-09 19:38:56 UTC (rev 515) +++ release-info/philip__1_1.log 2011-04-10 03:46:54 UTC (rev 516) @@ -170,7 +170,15 @@ (McLachlan/ML_BSSN_Test/test/gw3d_McLachlan_ord4_30.par) Requires 2 processors + KerrSchild-rotating-180 in RotatingSymmetry180 + (CactusNumerical/RotatingSymmetry180/test/KerrSchild-rotating-180.par) + Requires 2 processors + KerrSchild-rotating-90 in RotatingSymmetry90 + (CactusNumerical/RotatingSymmetry90/test/KerrSchild-rotating-90.par) + Requires 2 processors + + Tests with different number of test files: Multipole (test_22) @@ -234,10 +242,6 @@ RotatingDBHIVP [2] - RotatingSymmetry180 [1] - - RotatingSymmetry90 [1] - SlabTest [1] TOVSolver [5] @@ -481,14 +485,6 @@ test_rdbh - RotatingSymmetry180: - - KerrSchild-rotating-180 - - RotatingSymmetry90: - - KerrSchild-rotating-90 - SlabTest: slabtest @@ -716,6 +712,8 @@ Periodic PunctureTracker ReflectionSymmetry + RotatingSymmetry180 + RotatingSymmetry90 SetMask_SphericalSurface Slab Socket @@ -915,10 +913,6 @@ Success: 96 files compared, 92 differ in the last digits RotatingDBHIVP: test_rdbh Success: 120 files compared, 77 differ in the last digits - RotatingSymmetry180: KerrSchild-rotating-180 - Failure: 120 files compared, 100 differ, 32 differ significantly - RotatingSymmetry90: KerrSchild-rotating-90 - Failure: 120 files compared, 95 differ, 32 differ significantly SlabTest: slabtest Success: 1 files identical TOVSolver: test_one_boost_max @@ -1021,25 +1015,23 @@ Summary for configuration sim - Time -> Fri Apr 8 15:45:43 CDT 2011 - Host -> philip036 + Time -> Sat Apr 9 16:03:23 CDT 2011 + Host -> philip035 User -> knarf Total available tests -> 171 - Unrunnable tests -> 40 - Runnable tests -> 131 + Unrunnable tests -> 42 + Runnable tests -> 129 Total number of thorns -> 162 - Number of tested thorns -> 40 + Number of tested thorns -> 38 Number of tests passed -> 128 Number passed only to set tolerance -> 80 - Number failed -> 3 + Number failed -> 1 Tests failed: Schwarzschild_EF (from Exact) - KerrSchild-rotating-180 (from RotatingSymmetry180) - KerrSchild-rotating-90 (from RotatingSymmetry90) ======================================================================== File [modified]: philip__2_1.log Delta lines: +2 -2 =================================================================== --- release-info/philip__2_1.log 2011-04-09 19:38:56 UTC (rev 515) +++ release-info/philip__2_1.log 2011-04-10 03:46:54 UTC (rev 516) @@ -1012,8 +1012,8 @@ Summary for configuration sim - Time -> Fri Apr 8 16:01:48 CDT 2011 - Host -> philip036 + Time -> Sat Apr 9 16:23:28 CDT 2011 + Host -> philip035 User -> knarf Total available tests -> 171 File [modified]: philip__2_2.log Delta lines: +2 -2 =================================================================== --- release-info/philip__2_2.log 2011-04-09 19:38:56 UTC (rev 515) +++ release-info/philip__2_2.log 2011-04-10 03:46:54 UTC (rev 516) @@ -1012,8 +1012,8 @@ Summary for configuration sim - Time -> Fri Apr 8 16:16:11 CDT 2011 - Host -> philip036 + Time -> Sat Apr 9 16:39:24 CDT 2011 + Host -> philip035 User -> knarf Total available tests -> 171

1 0

[svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 48)
by knarf＠cct.lsu.edu 09 Apr '11

09 Apr '11

User: knarf Date: 2011/04/09 04:11 PM Modified: / ET.tex Log: expand introduction File Changes: Directory: / ============ File [modified]: ET.tex Delta lines: +35 -11 =================================================================== --- ET.tex 2011-04-04 14:54:56 UTC (rev 47) +++ ET.tex 2011-04-09 21:11:24 UTC (rev 48) @@ -109,7 +109,7 @@ Now is a particularly exciting time for numerical relativity and relativistic astrophysics. Recent computational breakthroughs~\cite{Pretorius:2005gq, Campanelli:2005dd, Baker:2005vv} -have transformed the field with our ability to +have transformed the field with the ability to effectively evolve the Einstein field equations for coalescing black hole binaries and other systems containing moving black holes. Following, and in part parallel to, these breakthroughs there have @@ -132,23 +132,23 @@ Pfeiffer:2007yz}. It is remarkable that many of the successful techniques used to -evolve binary BHs have proven equally applicable to merging BH-NS and -NS-NS binaries, allowing for the first full GR simulations of -these systems (e.g., +evolve binary BHs have proven to be equally applicable to merging BH-NS and +NS-NS binaries, allowing for the first full GR simulations of these systems (e.g., \cite{Shibata:2006bs,Shibata:2006ks,Loeffler06a,Shibata:2007zm, -Etienne:2007jg,Baiotti:2008ra,Duez:2008rb}). +Etienne:2007jg,Baiotti:2008ra,Duez:2008rb}), and spured a lot of activity +also in this field~\todo{cite}. - -GRMHD on fixed background spacetimes has been carried out in multi-dimensional +General relativistic magneto-hydrodynamics (GRMHD) on fixed background +spacetimes has been carried out in multi-dimensional settings, focusing on BH accretion processes and relativistic jet production and evolution, and has yielded results since the mid 1990s -(e.g., \cite{font:08}). On the other hand, GRMHD coupled with +(e.g., \cite{font:08}\todo{cite more}). On the other hand, GRMHD coupled with curvature evolution, crucial for modeling large-scale bulk dynamics in compact binary or single-star collapse scenarios, has started to produce astrophysically interesting results only in the past $\sim 3-5$ years, enabled primarily by the availability of long-term stable curvature evolution systems as well as improved GRMHD -algorithms \cite{font:08}. +algorithms~\cite{font:08}\todo{cite more}. The first full GR simulations of merging NS-NS and/or BH-NS binaries have recently been carried out by groups at Tokyo University @@ -171,9 +171,27 @@ rapidly rotating polytropic \ns{} models have been carried out in full GR by Shibata~et~al.~\cite{shibata:00}, Baiotti~et~al.~\cite{baiotti:07,manca:07}. - +In parallel to the advances in physical understanding and numerical techniques, +a set of computational tools and libraries was developed, with the +aim to provide a computational core that can enable the new science, +broaden the community, facilitate interdisciplinary research and take +advantage of emerging petascale computers and advanced cyberinfrastructure: +the Cactus computational toolkit. While being developed to a large part by +computer scientists, its development was driven by the direct input from other +fields, especially numerical relativity, succeeding in applying expertise in +computer science directly to problems in numerical relativity. +This success spawned usage of the Cactus computational toolkit in other +areas, such as hurricane forecast models. At the same time, the growing +number of results in numerical relativity increased the need for commonly +available utilities such as comparison and analysis tools, typically +problem-specific to astrophysical problems. Including them within the +Cactus computational toolkit didn't fit it's grown scope. This triggered +the creation of the Einstein Toolkit. While large parts of the Einstein toolkit +presently do make use of the Cactus toolkit, this is not an requirement at all, +and other contributions are welcome and have been accepted. + \section{Requirements\pages{2 Frank}} \subsection{Scientific} @@ -652,6 +670,8 @@ the \codename{TwoPunctures} module can also be used to construct neutron star black hole binary initial data, when being coupled with \codename{TOVSolver}. +\subsection{Equation of States}\pages{1 Christian} + \subsection{Spacetime Curvature and Hydrodynamics Evolution} \todo{Christian in charge} @@ -1355,14 +1375,18 @@ \section{Examples\pages{0.5 Frank}} -\subsection{Vacuum\pages{2 Bruno}} +\subsection{Spinning BH\pages{2 Bruno}} +\subsection{BBH\pages{2 Bruno}} + \subsection{TOV\pages{2 Frank}} Show stable TOV evolution \subsection{Collapse\pages{2 Christian}} Show TOV collapse and BH formation +\subsection{Cosmology\pages{2 Eloisa}} +Convergence \section{Future Work\pages{1 Frank}} This paper illustrated the current state of the ``Einstein Toolkit'',

1 0

[svn:einsteintoolkit] www/release-info/ (Rev. 515)
by knarf＠cct.lsu.edu 09 Apr '11

09 Apr '11

User: knarf Date: 2011/04/09 02:38 PM Modified: /release-info/ numrel-gcc__1_1.log, numrel-gcc__2_1.log, numrel-gcc__2_2.log, numrel__1_1.log, numrel__2_1.log, numrel__2_2.log Log: update numrel File Changes: Directory: /release-info/ ========================= File [modified]: numrel-gcc__1_1.log Delta lines: +15 -23 =================================================================== --- release-info/numrel-gcc__1_1.log 2011-04-09 15:00:47 UTC (rev 514) +++ release-info/numrel-gcc__1_1.log 2011-04-09 19:38:56 UTC (rev 515) @@ -170,7 +170,15 @@ (McLachlan/ML_BSSN_Test/test/gw3d_McLachlan_ord4_30.par) Requires 2 processors + KerrSchild-rotating-180 in RotatingSymmetry180 + (CactusNumerical/RotatingSymmetry180/test/KerrSchild-rotating-180.par) + Requires 2 processors + KerrSchild-rotating-90 in RotatingSymmetry90 + (CactusNumerical/RotatingSymmetry90/test/KerrSchild-rotating-90.par) + Requires 2 processors + + Tests with different number of test files: Multipole (test_22) @@ -236,10 +244,6 @@ RotatingDBHIVP [2] - RotatingSymmetry180 [1] - - RotatingSymmetry90 [1] - SlabTest [1] TOVSolver [5] @@ -489,14 +493,6 @@ test_rdbh - RotatingSymmetry180: - - KerrSchild-rotating-180 - - RotatingSymmetry90: - - KerrSchild-rotating-90 - SlabTest: slabtest @@ -724,6 +720,8 @@ Periodic PunctureTracker ReflectionSymmetry + RotatingSymmetry180 + RotatingSymmetry90 SetMask_SphericalSurface Slab Socket @@ -927,10 +925,6 @@ Success: 96 files compared, 92 differ in the last digits RotatingDBHIVP: test_rdbh Success: 120 files compared, 82 differ in the last digits - RotatingSymmetry180: KerrSchild-rotating-180 - Failure: 120 files compared, 102 differ, 32 differ significantly - RotatingSymmetry90: KerrSchild-rotating-90 - Failure: 120 files compared, 96 differ, 32 differ significantly SlabTest: slabtest Success: 1 files identical TOVSolver: test_one_boost_max @@ -1033,19 +1027,19 @@ Summary for configuration gcc - Time -> Thu Apr 7 14:05:58 CDT 2011 + Time -> Sat Apr 9 02:27:30 CDT 2011 Host -> numrel07.cct.lsu.edu User -> knarf Total available tests -> 173 - Unrunnable tests -> 40 - Runnable tests -> 133 + Unrunnable tests -> 42 + Runnable tests -> 131 Total number of thorns -> 163 - Number of tested thorns -> 41 + Number of tested thorns -> 39 Number of tests passed -> 127 Number passed only to set tolerance -> 76 - Number failed -> 6 + Number failed -> 4 Tests failed: @@ -1053,8 +1047,6 @@ halfsphere_pugh_ppm (from Hydro_InitExcision) x_flip_pugh_ppm (from Hydro_InitExcision) x_pugh_ppm (from Hydro_InitExcision) - KerrSchild-rotating-180 (from RotatingSymmetry180) - KerrSchild-rotating-90 (from RotatingSymmetry90) ======================================================================== File [modified]: numrel-gcc__2_1.log Delta lines: +1 -1 =================================================================== --- release-info/numrel-gcc__2_1.log 2011-04-09 15:00:47 UTC (rev 514) +++ release-info/numrel-gcc__2_1.log 2011-04-09 19:38:56 UTC (rev 515) @@ -1024,7 +1024,7 @@ Summary for configuration gcc - Time -> Thu Apr 7 14:27:05 CDT 2011 + Time -> Sat Apr 9 02:47:59 CDT 2011 Host -> numrel07.cct.lsu.edu User -> knarf File [modified]: numrel-gcc__2_2.log Delta lines: +1 -1 =================================================================== --- release-info/numrel-gcc__2_2.log 2011-04-09 15:00:47 UTC (rev 514) +++ release-info/numrel-gcc__2_2.log 2011-04-09 19:38:56 UTC (rev 515) @@ -1024,7 +1024,7 @@ Summary for configuration gcc - Time -> Thu Apr 7 15:02:27 CDT 2011 + Time -> Sat Apr 9 03:04:09 CDT 2011 Host -> numrel07.cct.lsu.edu User -> knarf File [modified]: numrel__1_1.log Delta lines: +15 -23 =================================================================== --- release-info/numrel__1_1.log 2011-04-09 15:00:47 UTC (rev 514) +++ release-info/numrel__1_1.log 2011-04-09 19:38:56 UTC (rev 515) @@ -170,7 +170,15 @@ (McLachlan/ML_BSSN_Test/test/gw3d_McLachlan_ord4_30.par) Requires 2 processors + KerrSchild-rotating-180 in RotatingSymmetry180 + (CactusNumerical/RotatingSymmetry180/test/KerrSchild-rotating-180.par) + Requires 2 processors + KerrSchild-rotating-90 in RotatingSymmetry90 + (CactusNumerical/RotatingSymmetry90/test/KerrSchild-rotating-90.par) + Requires 2 processors + + Tests with different number of test files: Multipole (test_22) @@ -236,10 +244,6 @@ RotatingDBHIVP [2] - RotatingSymmetry180 [1] - - RotatingSymmetry90 [1] - SlabTest [1] TOVSolver [5] @@ -489,14 +493,6 @@ test_rdbh - RotatingSymmetry180: - - KerrSchild-rotating-180 - - RotatingSymmetry90: - - KerrSchild-rotating-90 - SlabTest: slabtest @@ -724,6 +720,8 @@ Periodic PunctureTracker ReflectionSymmetry + RotatingSymmetry180 + RotatingSymmetry90 SetMask_SphericalSurface Slab Socket @@ -927,10 +925,6 @@ Success: 96 files compared, 92 differ in the last digits RotatingDBHIVP: test_rdbh Success: 120 files compared, 82 differ in the last digits - RotatingSymmetry180: KerrSchild-rotating-180 - Failure: 120 files compared, 100 differ, 32 differ significantly - RotatingSymmetry90: KerrSchild-rotating-90 - Failure: 120 files compared, 95 differ, 32 differ significantly SlabTest: slabtest Success: 1 files identical TOVSolver: test_one_boost_max @@ -1033,25 +1027,23 @@ Summary for configuration sim - Time -> Thu Apr 7 14:04:33 CDT 2011 + Time -> Sat Apr 9 01:18:20 CDT 2011 Host -> numrel07.cct.lsu.edu User -> knarf Total available tests -> 173 - Unrunnable tests -> 40 - Runnable tests -> 133 + Unrunnable tests -> 42 + Runnable tests -> 131 Total number of thorns -> 163 - Number of tested thorns -> 41 + Number of tested thorns -> 39 Number of tests passed -> 130 Number passed only to set tolerance -> 78 - Number failed -> 3 + Number failed -> 1 Tests failed: Schwarzschild_EF (from Exact) - KerrSchild-rotating-180 (from RotatingSymmetry180) - KerrSchild-rotating-90 (from RotatingSymmetry90) ======================================================================== File [modified]: numrel__2_1.log Delta lines: +3 -3 =================================================================== --- release-info/numrel__2_1.log 2011-04-09 15:00:47 UTC (rev 514) +++ release-info/numrel__2_1.log 2011-04-09 19:38:56 UTC (rev 515) @@ -879,9 +879,9 @@ IDAxiBrillBH: test_axibrill_nostagger Success: 96 files compared, 69 differ in the last digits IDAxiOddBrillBH: E2xeon_test_axioddbh - Success: 88 files compared, 85 differ in the last digits + Success: 88 files compared, 87 differ in the last digits IDAxiOddBrillBH: test_axioddbh - Success: 120 files compared, 72 differ in the last digits + Success: 120 files compared, 74 differ in the last digits IDConstraintViolate: ConstraintViolate Success: 24 files identical IDLinearWaves: test_pw_ADM_leap @@ -1024,7 +1024,7 @@ Summary for configuration sim - Time -> Thu Apr 7 14:25:46 CDT 2011 + Time -> Sat Apr 9 01:39:08 CDT 2011 Host -> numrel07.cct.lsu.edu User -> knarf File [modified]: numrel__2_2.log Delta lines: +2 -2 =================================================================== --- release-info/numrel__2_2.log 2011-04-09 15:00:47 UTC (rev 514) +++ release-info/numrel__2_2.log 2011-04-09 19:38:56 UTC (rev 515) @@ -881,7 +881,7 @@ IDAxiOddBrillBH: E2xeon_test_axioddbh Success: 88 files compared, 87 differ in the last digits IDAxiOddBrillBH: test_axioddbh - Success: 120 files compared, 72 differ in the last digits + Success: 120 files compared, 74 differ in the last digits IDConstraintViolate: ConstraintViolate Success: 24 files identical IDLinearWaves: test_pw_ADM_leap @@ -1024,7 +1024,7 @@ Summary for configuration sim - Time -> Thu Apr 7 14:56:03 CDT 2011 + Time -> Sat Apr 9 01:55:23 CDT 2011 Host -> numrel07.cct.lsu.edu User -> knarf

1 0

[svn:einsteintoolkit] www/release-info/ (Rev. 514)
by schnetter＠cct.lsu.edu 09 Apr '11

09 Apr '11

User: eschnett Date: 2011/04/09 10:00 AM Removed: /release-info/ hopper__2_1.log Modified: /release-info/ hopper__1_1.log, hopper__2_2.log Log: Update Hopper results File Changes: Directory: /release-info/ ========================= File [modified]: hopper__1_1.log Delta lines: <Unavailable> File [removed]: hopper__2_1.log Delta lines: <Unavailable> File [modified]: hopper__2_2.log Delta lines: <Unavailable>

1 0

← Newer
1
...
13
14
15
16
17
18
19
20
21
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Commits April 2011