Einstein Toolkit Documentation - User contributions [en]

User:Twright

2018-08-08T15:52:32Z

Twright: Test editing without CAPTCHA.

Test edits for logged-in users

https://www.cct.lsu.edu/

Yt

2018-08-06T16:52:24Z

Twright: yt moved to Yt: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

This Webpage is the wiki for developing the yt http://yt-project.org frontend for the Einstein Toolkit.

== Status ==

We have an almost working frontend.

== Challenges ==

* yt supports cell-centred data only.
** To correct this we first implement a fake subgrid, filled by restriction
** Later Matt will add better support for true vertex-centred data
* Multiblock is not yet supported, but yt's coordinate handler will be able to make it work.
* Discontinuous Galerkin methods are not supported. Support will come with hexahedral mesh support
** High-order finite element support is coming and then discontinuous Galerkin methods will work beautifully.

== Tasks in Order of Priority ==

Check off when done:

* handle unigrid data
* handle vertex-centred AMR data
* improve handling of boundaries (outer boundaries vs. symmetry boundaries)
* handle multi-block data
* handle cell-centred data
* remove buffer zones from output
* handle DGFE data
* measure performance, complain about performance problems

Also:

* collect (here on this wiki?) a list of additional information necessary, e.g. additional attributes that would be helpful
* suggest improvements to output format, from experience with other output formats

== Shopping List ==

* information (best would be starting index and size) about what we call ''Active Region'', i.e. part of the grid that's unique and not overlapping with its siblings (grids on the same level)
* full information about type of external boundaries, best would be 6 element integer array, or 3x2

== Simulation List ==

We have the following simulations available to test against

* static_tov, a static neutron star with fixed mesh refinement
* ml_wavetoy, a series of simulations of a Gaussian pulse with refinement at the centre and periodic boundary conditions
* excited_tov_Lev0-i0000, a perturbed neutron star with adaptive mesh refinement and a sevenpatch multiblock infrastructure.
* bssn_dg4_sixpatches_kerrschild, a black hole with excision using discontinuous Galerkin methods

== TODO ==

* After it is working, Jonah will add comments to the frontend to ensure future generations have the knowledge of Carpet required to design it gleaned during the workshop at the NCSA.
* Other TODOS?

yt

2018-08-06T16:52:24Z

Twright: yt moved to Yt: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Yt]]

test site

2018-08-06T16:52:02Z

Twright: test site moved to Test site: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Test site]]

test3

2018-08-06T16:51:25Z

Twright: test3 moved to Test3: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Test3]]

test

2018-08-06T16:51:12Z

Twright: test moved to Test: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Test]]

Seminar-2013 02 04-participants

2018-08-06T16:50:55Z

Twright: seminar-2013 02 04-participants moved to Seminar-2013 02 04-participants: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

==List of participants for Christian Reisswig's presentation on 2012-02-04==

(see http://einsteintoolkit.org/seminars/2013_02_04/ for details)

We will use WebEx for Christian's presentation. You need to register to receive an invitation email for WebEx about one hour before the presentation. You register by '''adding your name and email address''' to the list below. Please register at least two hours before the talk begins. If you cannot / do not want to register in public, then send email to Erik Schnetter <eschnetter@perimeterinstitute.ca> instead.

(Yes, we know that it is inconvenient and somewhat counter-productive to have to register. We are working on this. Apologies.)

NOTE: I have removed the email addresses to help conserve privacy. If you still want to participate, please contact me directly.

* Erik Schnetter
* Barry Wardell
* Scott Noble
* Roland Haas
* Tanja Bode
* David Radice
* Daniela Alic
* Bruno Giacomazzo
* Ian Hawke
* Tim Lemon
* John Muddle
* Vassilios Mewes
* Bruno Mundim

seminar-2013 02 04-participants

2018-08-06T16:50:55Z

Twright: seminar-2013 02 04-participants moved to Seminar-2013 02 04-participants: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Seminar-2013 02 04-participants]]

adding initial data

2018-08-06T16:50:31Z

Twright: adding initial data moved to Adding initial data: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Adding initial data]]

Adding initial data

2018-08-06T16:50:31Z

Twright: adding initial data moved to Adding initial data: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

=Writing an Initial Data thorn for the Einstein Toolkit=

This page explains how to write a new initial data thorn for the Einstein Toolkit. These initial data will set up ADMBase or HydroBase variables, so that they are usable for all other thorns that are based Einstein Toolkit.

==Introduction==

You need:
* a prescription or routine that actually generates the initial data,
* to decide whether this are initial data for the spacetime, for hydrodynamics, or both,
* these instructions.

==Example==

Let us assume, for the sake of simplicity, that we are going to set up initial data for the spacetime only. Let us pick a concrete example: the Kruskal coordinates. The Kruskal coordinates describe a single, static black hole (the Schwarzschild spacetime), and their advantage over many other coordinate systems is that they cover the whole, extended Schwarzschild spacetime (i.e. including both asymptotically flat ends, the worm hole, the black and white hole horizons), and that they do not introduce coordinate singularities. Of course there are curvature singularities inside the white and black holes, but there are no "artificial" singularities, e.g. at the horizons. The Kruskal coordinates are beautifully described in Sean M. Carroll's "A No-Nonsense Introduction to General Relativity", 2001, at http://pancake.uchicago.edu/~carroll/notes/grtinypdf.pdf .

To make things a bit more interesting, we are also going to apply a coordinate transformation to the Kruskal coordinates, so that we can evaluate them on arbitrary slices. Of course that means that the actual coordinates are not the Kruskal coordinates. This means that the slicing can in principle be chosen arbitrarily within the extended Schwarzschild spacetime. Other coordinates (e.g. ingoing Eddington-Finkelstein coordinates) are regular only a in part of the spacetime. This will allow us to examine arbitrary slicings of Schwarzschild -- even slicings that are not spherically symmetric -- which is very interesting when one studies trapped surfaces or apparent horizons.

In particular, we want to implement the following slicings:
* Kruskal
* Schwarzschild
* the Wald-Iyer slicing introduced in Phys. Rev. D '''44''', R3719 (1991), "Trapped surfaces in the Schwarzschild geometry and cosmic censorship"

As described in this paper, this slicing has the property that it comes arbitrarily close to the (future) curvature singularity in the Schwarzschild spacetime, but does not contain any apparent horizons. We want to examine this numerically.

==Kruskal Solution==

As mentioned above, we begin by implementing a Fortran module that evaluates the Kruskal solution at a particular event (t,x,y,z). How to do this is outside the scope of this tutorial; one example implementation is here: [[Media:kruskal.F90]].

This module contains a routine that has as its input arguments 4 real numbers t, x, y, and z, describing the spacetime event where the four-metric needs to be evaluated. Its output arguments are alpha, beta^i, and g_ij, which this routine has to fill in. For convenience, this routine also sets the two arguments u and v to the Kruskal coordinates of this event, and two other arguments st and sr to its Schwarzschild coordinates. (Since the metric is spherically symmetric, angular coordinates can be omitted.)

Internally, the routine transforms the tuple (t,x,y,z) to (u,v) and (st,sr) according to the chosen slicing. In particular, the different slicings lead to:
* Kruskal: v = t
* Schwarzschild: v = u tanh (t / 4M)
* Wald-Iyer: v = t z/r
where M is the ADM mass and r is the Pythagorean of (x,y,z). Details do not matter for the tutorial here can be found in the source code. It should be mentioned that this coordinate transformation requires a non-linear root finding which is implemented with the help of the GSL (GNU Scientific Library).

This module is the heart of this initial data thorn, and most of the physical and numerical work has been invested here. What remains it to wrap this routine, so that the Einstein Toolkit understands it.

In many other cases, the initial data will be calculated not pointwise, but by an external solver on an auxiliary grid, and there will be an interpolation routine that evaluates the solution at arbitrary coordinates (t,x,y,z). It is sufficient if the solution is only known at t=0.

==Loop over all grid points==

The next step is to populate the ADMBase (and/or HydroBase) grid functions. This requires a routine which is scheduled in Cactus's INITIAL bin, and which iterates over all grid points, evaluating the solution there. The solution is evaluated by calling the Kruskal module described above.

===Basic Structure===

The boilerplate form of such a routine is as follows:

#include "cctk.h"
#include "cctk_Arguments.h"
#include "cctk_Functions.h"
#include "cctk_Parameters.h"

subroutine Kruskal_InitialData (CCTK_ARGUMENTS)
implicit none
DECLARE_CCTK_ARGUMENTS
DECLARE_CCTK_FUNCTIONS
DECLARE_CCTK_PARAMETERS
integer :: i, j, k
do k = 1, cctk_lsh(3)
do j = 1, cctk_lsh(2)
do i = 1, cctk_lsh(1)
! DO THE ACTUAL WORK
end do
end do
end do
end subroutine Kruskal_InitialData

This routine has to fill in all ADMBase variables, which are:
* lapse alpha
* shift beta^i
* metric g_ij
* extrinsic curvature K_ij
* potentially: time derivative of lapse
* potentially: time derivative of shift
Whether the latter two are necessary depends on whether the evolution system uses them; for example, the BSSN does use the time derivative of the shift. If they are not set, many thorns will assume that they are zero, which may or may not be what is intended.

===Excursion: Extrinsic Curvature===

Reviewing what we have so far, we notice that the Kruskal module does not calculate the extrinsic curvature K_ij. The reason is that calculating K_ij requires calculating the time derivative of g_ij, and the coordinate transformation implemented in the Kruskal module is already quite complicated. We are therefore going to calculate K_ij via finite differencing. Note that many initial data prescriptions have explicit expressions for K_ij, so that this step may not be necessary.

This finite differencing is implemented, at each grid point, by evaluating the initial data several times with small offsets in the time and space directions. Straight-forward second order finite differencing then yields all the derivatives of lapse, shift, and three-metric, and the extrinsic curvature is then calculated in a straightforward manner via the ADM relation
d/dt g_ij = -2 alpha K_ij + g_kj beta^k,i + g_ik beta^k,j + beta^k g_ij,k

The time derivatives of lapse and shift could be calculated in a similar manner. This is not implemented in this thorn, because its solution is not intended for a time evolution; instead, horizons can be located directly on the initial data.

===Setting only the desired quantities===

The Einstein Toolkit allows mix-and-matching between different three-metrics, lapse, and shift conditions. (This is only rarely used these days.) Therefore, this routine must set metric, lapse, and shift only when these are actually selected by the user in the parameter file; otherwise, it would overwrite data set by other thorns.

The user chooses initial conditions via the ADMBase parameters
* ADMBase::initial_data (metric and extrinsic curvature)
* ADMBase::initial_lapse
* ADMBase::initial_shift

Each thorn providing initial data needs to extend the range of these parameters (see below). It may only set up its initial data if the user chose so. In our case, we examine these parameters in the beginning
logical :: want_lapse, want_shift, want_data
want_lapse = CCTK_EQUALS (initial_lapse, "Kruskal")
want_shift = CCTK_EQUALS (initial_shift, "Kruskal")
want_data = CCTK_EQUALS (initial_data, "Kruskal")
and set the grid functions in the loop only if these conditions hold:
! Store initial data

if (want_data) then
gxx(i,j,k) = gama(1,1)
gxy(i,j,k) = gama(1,2)
gxz(i,j,k) = gama(1,3)
gyy(i,j,k) = gama(2,2)
gyz(i,j,k) = gama(2,3)
gzz(i,j,k) = gama(3,3)

kxx(i,j,k) = kk(1,1)
kxy(i,j,k) = kk(1,2)
kxz(i,j,k) = kk(1,3)
kyy(i,j,k) = kk(2,2)
kyz(i,j,k) = kk(2,3)
kzz(i,j,k) = kk(3,3)
end if

if (want_lapse) then
alp(i,j,k) = alfa
end if

if (want_shift) then
betax(i,j,k) = beta(1)
betay(i,j,k) = beta(2)
betaz(i,j,k) = beta(3)
end if

For reference, the complete initial data routine is here: [[Media:InitialData.F90]]

==CCL Files: Cactus Declarations==

In the last step (now that all the hard work is done), we describe to Cactus how this torn is called, what its variables are, what parameters it takes, and when its routines need to be called.

===interface.ccl===

This thorn is called "Kruskal", and it implements an interface that we also call "Kruskal" (for the lack of a better idea).
IMPLEMENTS: Kruskal

This thorn requires access to a few other variables, in particular the grid points' coordinates, and the ADMBase variables which it calculates:
INHERITS: ADMBase StaticConformal grid

It also calculates and stores the Kruskal and Schwarzschild coordinates of every grid point for convenience, so we define grid functions for these:
CCTK_REAL Schwarzschild_radius TYPE=gf
{
schw_radius
schw_time
kruskal_u
kruskal_v
} "Schwarzschild radius"

The complete file is here: [[Media:interface.ccl.txt]]

===param.ccl===

There are two kinds of parameters that we have to deal with:
* Parameters that choose which kind of initial data should be set up (which we extend to include "Kruskal")
* Parameters for ourselves, where e.g. the ADM mass of the Schwarzschild spacetime is set, and the slicing is chosen

Let's begin with the initial data choice parameters, which are defined in ADMBase. We obtain access to them, and extend their range (the set of allowed values) to include "Kruskal"). We can do this because ADMBase allows us to do so -- private parameters could not be extended.

SHARES: ADMBase

EXTENDS KEYWORD initial_lapse
{
"Kruskal" :: "Kruskal lapse"
}

EXTENDS KEYWORD initial_shift
{
"Kruskal" :: "Kruskal shift"
}

EXTENDS KEYWORD initial_data
{
"Kruskal" :: "Kruskal metric"
}

USES KEYWORD metric_type

We also set a few parameters of our own:

PRIVATE:

BOOLEAN calculate_Schwarzschild_radius "Calculate the Schwarzschild radius?"
{
} no

CCTK_REAL mass "Black hole mass"
{
0:* :: ""
} 1.0

KEYWORD slicing "Choice of slicing"
{
"Kruskal" :: "v = t"
"Schwarzschild" :: "v = u tanh (t / 4M)"
"Wald-Iyer" :: "v = t cos theta"
} "Kruskal"

CCTK_REAL delta "Finite differencing distance"
{
(0:* :: ""
} 1.0e-6

The complete file is here: [[Media:param.ccl.txt]]

===schedule.ccl===

Finally we declare which variables need to have storage, and which routines need to be called when.

We allow users to store the Schwarzschild and Kruskal coordinates of each grid point if the parameter calculate_Schwarzschild_radius is set, so we need to allocate storage for this group:

if (calculate_Schwarzschild_radius)
{
STORAGE: Schwarzschild_radius
}

We also describe under which circumstances our initial data routine should be called, and when it should be called:

if (CCTK_EQUALS (initial_lapse, "Kruskal")
|| CCTK_EQUALS (initial_shift, "Kruskal")
|| CCTK_EQUALS (initial_data, "Kruskal"))
{
SCHEDULE Kruskal_InitialData IN ADMBase_InitialData
{
LANG: Fortran
} "Set up Kruskal initial data"
}

ADMBase provides the schedule group "ADMBase_InitialData" for, well, setting up initial data. This ensures that e.g. coordinates are set up beforehand, and boundary conditions or AMR prolongation or restriction occur afterwards. There is a similar HydroBase schedule group for hydrodynamics variables.

Scheduling the initial data routine takes no options, leaving all schedule options at their default values. This means e.g. that this routine is called once for each refinement level (corresponding to "OPTIONS=local"). Also, no grid functions need to be synchronised since all grid points are set, including boundary and ghost points.

The complete file is here: [[Media:schedule.ccl.txt]]

==Setting up and Running an Example==

You can obtain a tarball of the complete thorn here: [[Media:Kruskal.tar.gz]].

This section is missing. There are example parameter files in the par subdirectory. It is particularly interesting to run "kruskal-wald-iyer.par", which shows that "numerical apparent horizons" are found after all, although true apparent horizons do not exist. Speak about http://prd.aps.org/abstract/PRD/v73/i2/e021502 .

Adding a test case

2018-08-06T16:49:50Z

Twright: adding a test case moved to Adding a test case: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

=Adding a Test Case to a Thorn=

This page describes how to add a test case to a Cactus thorn. It will
guide you step-by-step through the ideas behind test cases to some of
the finer details that make a test case easy to use.

==A test case is...==

Cactus test cases are primarily ''regression tests'', i.e. they are
supposed to catch unintended changes in the behaviour of thorns. Test
cases should be small, so that one can quickly run many test cases,
and see whether anything changed unexpectedly. Test cases are not
supposed to perform a convergence test, or test any other kind of
physics correctness. It is important to test these as well, but a
regression test case is not really a good way to do so.

In Cactus, test cases are parameter files that are run by Cactus, and
which are then compared to the expected output. To set up a test
case, you have to (a) write a parameter file, and (b) run it to create
this "expected output". These are stored in the "test" directory of a
thorn. The output directory must have the same name as the parameter
file (without the ".par" suffix).

Cactus compares the new and the expected output by comparing real
numbers in ASCII files, allowing a certain "fuzz", i.e. a difference
of about 1.0e-12.

==How to design a test case==

Test cases should be
* simple
* small
* quick
* use as few thorns as possible (simple!)
* output only a few variables (small!)
* output only norms and 1D ASCII quantities (small!)
* finish in under two minutes (quick!)

Preferably, each major feature in a thorn should be covered by a test
case. If necessary, one has to introduce helper thorns that use the
tested features.

By default, test cases are run on two processes. Obviously, the test
case should not output anything that would change between different
runs, such as e.g. the current date. It does also not make sense to
output the parameter file itself.

They should also not output quantities that are significantly
influenced by floating-point round-off error. For example, the "sum"
reduction operator on N grid points has an absolute error that is N
times the floating-point round-off, which is unsuitably large. The
"average" reduction operator divides this by N and thus has a smaller
absolute error.

In general, norms are quite insensitive to changes that occur at a
single grid point, and can thus miss changes in behaviour. Similarly,
1D ASCII output will miss changes that occur off-axis. In general, a
combination of norms and 1D output is best.

Checkpoint files, binary I/O, reading initial data from files, web
servers etc. cannot easily be tested, and should be avoided in test
cases if possible. They are certainly an advanced topic that we will
skip here.

It is a common mistake (read: a mistake that I made) to output too
many variables in test cases. This makes test cases too large, and
then inconvenient to handle. If there are more than a dozen test
cases per thorn, the size of the expected output can significantly
increase download speed and disk space required for this thorn. These
additional files will probably not help in detecting whether the
thorn's behaviour has changed -- they only may make it easier to track
down the reason, and this is not what a test case is for.

==How to create a test case==

It is probably best to start from a working parameter file that uses a
particular feature. Then one removes all those features and thorns
that are not necessary. To reduce the size further, one reduces the
number of time steps, chooses a much smaller domain and a much coarse
grid. It may make sense to introduce symmetries or periodic
boundaries.

Note that a test case does not need to provide physically interesting
output; it is only supposed to check whether the code still provides
the same output. Thus, as long as a coarser grid still executes the
same routines, it is fine. Of course, the grid must not be so coarse
that it generates nans.

At this stage, it may also make sense to avoid mesh refinement or
multi-block systems, or to reduce the order of accuracy.

In the end, the parameter file should run on a single core, should not
need more than a few hundred MByte of memory, and should finish in
under two minutes. Typically, it suffices to run for a few time steps
on a 10^3 domain.

At this stage, the physics output of the parameter file has probably
changed a lot. This is fine; all it needs to do is to check that the
feature that is to be tested will return the same result in the future
as it does now.

==How to finish a test case==

After these steps, you should make a few more modifiations to the
parameter file.

Output directory: Choose the I/O options
IO::out_dir = $parfile
IO::out_fileinfo = "none"
IO::parfile_write = "no"
to ensure that the output directory has the right name, and that no
additional information is written into the output files.

TODO: add compact Carpet output format and omission of ghost zones here. See ML_BSSN_Test for how to do this so that the tests can then run on all numbers of processes.

Output quantities: Certain reduction operations (such as "sum") should
be avoided, since they change too much due to floating-point
round-off. The following reductions (and similar ones) are good;
others should be avoided:
* count minimum maximum average norm1 norm2 norm_inf
Do not use
* product sum sum_abs sum_squared sum_abs_squared

Screen output (info output) is ignored in test cases. You should
leave a bit of info output enabled, since this helps debugging, but it
won't be checked when the test case is run.

You will also want to beautify the parameter file at this point,
adding comments, and maybe adding your own name for vanity at the top.
You should also explain what the test case is testing.

Then you run the parameter file on two processes. After a short while
(under two minutes!), you should see an output directory. Have a look
into the output directory and check:
* Is there a ".par" file? (There should not.)
* Are there binary files? (There should not.)
* Are there large files? (There should not.)
* Are there many files? (There should not.)

Then move the parameter file as well as this output directory into the
"test" directory of the thorn you are testing.

Next, run this test case, following the Cactus instructions for doing
so. The test case should pass.

TODO: advise that the test should also be tested on 1 process, and higher numbers, and should still pass.

Don't forget to commit the test case, or to attach it to a patch you
are proposing.

==How to track down why a test case fails==

(INCOMPLETE)

* Check out old code versions, find version that succeeds
* Output additional quantities, since the test case probably doesn't output enough data for this
* When doing so, keep several versions of the code/executable around, since you will be re-running the test cases many times

==Making the test output independent of the number of processes==

You may find that output data depends on the number of processes being run on. Setting the following parameters may make the output the same on 1 and 2 processes, which are the numbers of processes used in the automated tests.

CarpetIOASCII::compact_format = yes
CarpetIOASCII::output_ghost_points = no

Talk:Adding a test case

2018-08-06T16:49:50Z

Twright: Talk:adding a test case moved to Talk:Adding a test case: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

adding a test case

2018-08-06T16:49:50Z

Twright: adding a test case moved to Adding a test case: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Adding a test case]]

Talk:adding a test case

2018-08-06T16:49:50Z

Twright: Talk:adding a test case moved to Talk:Adding a test case: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Talk:Adding a test case]]

Meeting agenda

2018-08-06T16:48:25Z

Twright: meeting agenda moved to Meeting agenda: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

<div class="toclimit-1">__TOC__</div>

= Connection Details =

We are using Blue Jeans to host the Einstein Toolkit meetings. The meeting is sponsored by the [https://www.perimeterinstitute.ca/ Perimeter Institute for theoretical physics].

* Meeting Title: Einstein Toolkit
* Meeting Time: Every Monday at 10:00 Eastern Time / 2 hrs
* Connect via a web browser (recommended): https://bluejeans.com/194244555
* Dial in via phone (if you cannot use a web browser):
*# +1 866 826 8602 (Canada/USA) +1 647 427 3061 (Global Numbers)
*# Enter Meeting ID: 256 841 6361
*# Press #
* Want to test your video connection? https://bluejeans.com/111

Google's Chrome browser is a good choice to connect since it will allow you to screenshare individual windows. Both of Chrome and Firefox have been successfully used for just audio connection and video reception (Safari on OSX only allows to download the OSX app, but not to connect directly in the browser).
<onlyinclude><includeonly><ul><li>The link for the call is: https://bluejeans.com/194244555.
</li><li>Today's [[meeting_agenda#Meeting_Agenda|meeting agenda]] is on this wiki too.</li></ul></includeonly></onlyinclude>

= Meeting Agenda =

When adding a topic, please add your '''name''' next to the item you are proposing.
Meetings are every Monday at 10:00 AM US Eastern time. Old meeting minutes can be found on the [[Phone_Call_Minutes|phone call minutes]] page.

== 2018-08-06 ==
* upcoming ET release in September [RH]
** status of gallery examples [RH]
*** BBH: Sam
*** Poisson equation: Shawn
*** Scalar field using Multipatch code: Roland
*** TOV: Roland
*** BNS: Peter
** reviews [RH]
*** [https://bitbucket.org/zach_etienne/giraffe/src GiRaFFE]
*** [https://bitbucket.org/zach_etienne/wvuthorns_diagnostics/src WVUThorns_Diagnostics]
*** Lean
*** Proca
** milestones: [https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&milestone=ET_2018_08&or&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&priority=critical&component=!Mojave&or&priority=blocker&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&component=!Mojave&col=id&col=summary&col=status&col=priority&col=milestone&col=component&col=owner&col=type&col=reporter&order=priority from trac] [RH]
* education working group ([[Media:EinsteinToolkit_EducationAndOutreach.pdf]]) [RH]
* unanswered question on mailing list / open tickets without responses
** http://lists.einsteintoolkit.org/pipermail/users/2018-July/006421.html
** http://lists.einsteintoolkit.org/pipermail/users/2018-July/006392.html
** http://lists.einsteintoolkit.org/pipermail/users/2018-July/006419.html

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-August/006437.html here]

== 2018-07-30 ==
* wiki editing without accounts [RH]
* memory consumption in BBH simulations [RH]
* upcoming ET release in September [RH]
** status of gallery examples [RH]
*** BBH
*** Poisson equation
*** Scalar field using Multipatch code
*** TOV
*** BNS
** reviews
*** [https://bitbucket.org/zach_etienne/giraffe/src GiRaFFE]
*** [https://bitbucket.org/zach_etienne/wvuthorns_diagnostics/src WVUThorns_Diagnostics]
*** Lean
*** Proca
** milestones: [https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&milestone=ET_2018_08&or&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&priority=critical&component=!Mojave&or&priority=blocker&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&component=!Mojave&col=id&col=summary&col=status&col=priority&col=milestone&col=component&col=owner&col=type&col=reporter&order=priority from trac] [RH]
* unanswered question on mailing list / open tickets without responses

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-July/006416.html here].

== 2018-07-23 ==
* Working group updates

** [[Media:wgopt-update-20180723.pdf|Optimization]]: [RH]
** Scheduling: [SB]
** [https://docs.google.com/presentation/d/1ojZuRIbr28-sS5uKg7201D2rHcyZNnIAu6O_P-6XQ94/edit?usp=sharing IllinoisGRMHD]: [ZE]
** Cosmoparticles: [HW]
** DataVault: [QZ]
* wiki editing without accounts [RH]
* SSL certificate for wiki server expiring August 18th [RH]
* tutorial server still down [RH]
* upcoming ET release in September [RH]
** status of gallery examples [RH]
*** BBH
*** Poisson equation
*** Scalar field using Multipatch code
*** TOV
*** BNS
** reviews
*** [https://bitbucket.org/zach_etienne/giraffe/src GiRaFFE]
*** [https://bitbucket.org/zach_etienne/wvuthorns_diagnostics/src WVUThorns_Diagnostics]
*** Lean
*** Proca
** milestones: [https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&milestone=ET_2018_08&or&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&priority=critical&component=!Mojave&or&priority=blocker&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&component=!Mojave&col=id&col=summary&col=status&col=priority&col=milestone&col=component&col=owner&col=type&col=reporter&order=priority from trac] [RH]
* unanswered question on mailing list / open tickets without responses

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-July/006411.html here]

== 2018-07-16 ==
* upcoming ET release in September [RH]
** status of gallery examples [RH]
*** BBH
*** Poisson equation
*** Scalar field using Multipatch code
*** TOV
*** BNS
** milestones: [https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&milestone=ET_2018_08&or&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&priority=critical&component=!Mojave&or&priority=blocker&status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&component=!Mojave&col=id&col=summary&col=status&col=priority&col=milestone&col=component&col=owner&col=type&col=reporter&order=priority from trac] [RH]
* unanswered question on mailing list / open tickets without responses

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-July/006383.html here]

== 2018-07-09 ==
* upcoming ET release in September [RH]
** status of gallery examples [RH]
** thorns to include [RH]
* unanswered question on mailing list / open tickets without responses

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-July/006373.html]

== 2018-07-02 ==
* upcoming ET release in August [RH]
** thorns to include
** announcement of major improvements / bugfixes
** support for common OS
** milestones: [https://trac.einsteintoolkit.org/query?status=accepted&status=assigned&status=confirmed&status=new&status=reopened&status=review&status=reviewed_ok&milestone=ET_2018_08&col=id&col=summary&col=status&col=priority&col=milestone&col=component&col=owner&col=type&col=reporter&order=priority 2018-08]
* new user tutorial issues: [https://trac.einsteintoolkit.org/ticket/2149 2149] [https://trac.einsteintoolkit.org/ticket/2150 2150] [[https://trac.einsteintoolkit.org/ticket/2004 2004] [https://trac.einsteintoolkit.org/ticket/2147 2147] [RH]
* possible issue with QLM: [https://trac.einsteintoolkit.org/ticket/2160 2160] [RH]
* Backward compatibility in PreSync [SC]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-July/006364.html here]

== 2018-06-25 ==
* ET meeting summery [RH]
* SSL certificates expiring: https://trac.einsteintoolkit.org/ticket/2145 [RH]
* compiling ET on MacBooks apparently fails [RH]
* report that QLM does not compute spin correctly: https://trac.einsteintoolkit.org/ticket/2160 [RH]
* any open question on mailing list of chat(s) [RH]
** QLM question above
** apparently on OSX we can generate a command line too long for the OS to handle

Minutes are here: [http://lists.einsteintoolkit.org/pipermail/users/2018-June/006350.html here]

== 2018-06-18 ==

No meeting on 2018-06-18 due to ET meeting at GT. ET meeting [[Media:ETWorkshop_Updates_GT2018.pdf|summary slides]].

== 2018-06-11 ==

Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-June/006327.html here]

== 2018-06-04 ==
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-June/006309.html here]

== 2018-05-28 ==

* [ZE] Working group updates
** [ZE] [https://docs.google.com/presentation/d/1NPv2I6MZqgrhMIfLbxYenMmW-ReqYBKd5OudLam69i8/edit?usp=sharing IllinoisGRMHD]
** [RH] [[Media:PF-WG-20180527.pdf|Performance Optimization]]

Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-May/006295.html here]

== 2018-05-21 ==

* [RH] working group updates next week
* [RH] incorporating WK's con2prim in GRhydro
* [RH] server status
** captchas on wiki sites
* standing item: unanswered / ongoing questions on mailing list

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-May/006279.html here]

== 2018-05-14 ==

* [RH] planning for next ET release (due in June or August)
** [RH] status of NSNS gallery example: http://einsteintoolkit.org/mp.html
** [RH] status of download page for ET MHD paper: http://einsteintoolkit.org/mp.html
* [RH] server status
** ssl on trac and wiki sites
** captchas on trac and wiki sites
* standing item: unanswered / ongoing questions on mailing list

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-May/006257.html here]

== 2018-05-07 ==

* [RH] planning for next ET release (due in June or August)
** [RH] status of NSNS gallery example: http://einsteintoolkit.org/mp.html
** [RH] status of download page for ET MHD paper: http://einsteintoolkit.org/mp.html
** [RH] status of review for codes that should be included in next release:
*** Giraffe [https://bitbucket.org/zach_etienne/wvuthorns/pull-requests/1/giraffe-review/diff pull request]
*** other codes and pull requests?
* [RH] server status
** ssl on trac and wiki sites
** captchas on trac and wiki sites
* standing item: unanswered / ongoing questions on mailing list

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-May/006244.html here]

== 2018-04-30 ==

* [SB] Working Group updates
** [https://docs.einsteintoolkit.org/et-docs/images/8/8d/WorkingGroupScheduler.pdf Working Group on Data Dependent Task Scheduler]
** [ZE] [https://docs.google.com/presentation/d/1imIZ5Yf6Hw4FZPH9RklrKExlxkP3JQ-21o-8QNxeuUE/edit?usp=sharing IllinoisGRMHD Working Group]
* [RH] server status
** ssl on trac and wiki sites
** captchas on trac and wiki sites
* standing item: unanswered / ongoing questions on mailing list

== 2018-04-23 ==
* [ZE] New ETK gitter chat rooms: [https://gitter.im/EinsteinToolkit/EinsteinToolkit Users/Developers Chat] ; [https://gitter.im/EinsteinToolkit/WG-PerformanceOptimization Performance Optimization Working Group]
* [RH] working group updates
** [RH] [https://docs.einsteintoolkit.org/et-docs/images/b/b0/PF-WG-20180423.pdf Working Group on Performance optimization]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-April/006210.html here]

== 2018-04-16 ==
(Cancelled due to [https://www.aps.org/meetings/april/about.cfm APS April Meeting?])

== 2018-04-09 ==
* wiki page requiring login [RH]
* updates on ET meetings in EU and US [RH]
* missing material on ET website on http://einsteintoolkit.org/mp.html [RH]
* issues ([https://trac.einsteintoolkit.org/ticket/2144 ticket]) signing up a member fails due to page not found for http://einsteintoolkit.org/send-registration

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-April/006186.html here].

== 2018-04-02 ==

* Update on websites [SB]
* Update on thorns waiting to be added [SB]
* Working group document for performanceoptimization-wg [[Working Group on Performance Optimization]] [RH]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-April/006174.html here]

== 2018-03-26 ==

* ssl status of https://einsteintoolkit.org and https://www.cactuscode.org [https://www.cct.lsu.edu/~knarf/cgi-bin/monitor.cgi status page] [RH]
* Working group document for performanceoptimization-wg [[Working Group on Performance Optimization]] [RH]
* ReCAPTCHA will cease service on https://docs.einsteintoolkit.org on 2018-03-31. See ticket [https://trac.einsteintoolkit.org/ticket/2135 2135] [RH]
* move https://www.einsteintoolkit.org to be hosted by bitbucket (test is: https://einsteintoolkit.bitbucket.io/). Can we point the DNS entry to it? [RH]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-March/006162.html here]

== 2018-03-19 ==

* Status on updating Trac [SB]
* Update on the working groups? [SB]
* reviews of code to be included [RH]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-March/006133.html here]

== 2018-03-12 ==

* Status on updating Trac

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-March/006122.html here]

== 2018-03-05 ==

* upcoming workshops [RH]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-March/006116.html here]

== 2018-02-26 ==

* upcoming workshops [RH]
* tickets for the next release [SB]
* discussions on the mailing list [SB]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-February/006110.html here]/

== 2018-02-19 ==

* Erik will give a summary of a Perimeter Institute workshop [ES]
* Talk about tickets that didn't make it into the release [SB]
* upcoming workshops [BK,SB]
* update on openmp scaling on stampede2 [JH]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-February/006095.html here]

== 2018-02-12 ==
* no agenda

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-February/006073.html here].

== 2018-02-05 ==

* [RH] ET release updates.
* [RH] US ET meeting date poll: [https://www.when2meet.com/?6644007-rVgmz https://www.when2meet.com/?6644007-rVgmz]
* [RH} offline tutorial: [https://nbviewer.jupyter.org/github/nds-org/jupyter-et/blob/master/CactusTutorial.ipynb https://nbviewer.jupyter.org/github/nds-org/jupyter-et/blob/master/CactusTutorial.ipynb]
* standing item: unanswered emails on the list

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-February/006054.html here].

== 2018-01-29 ==

* [EB] [HW] Announce cosmoparticle mailing list and invite subscriptions.
* [RH] [YZ] Failing tests in PITTNullCode when using --fast-math
* [RH] status of ET testsuites for release
* [RH} Hydro_RNSID review results
* [JH] OpenMP Scalability

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-January/006039.html here].

== 2018-01-22 ==

* [ES] OpenMP scalability
* [MZ & HW] Adding [https://bitbucket.org/canuda/lean_public Lean public] and [https://bitbucket.org/canuda/proca Proca] thorns to the Toolkit
* Tickets to be looked at for the upcoming ET_2018_02 release: [https://trac.einsteintoolkit.org/query?status=%21closed&milestone=ET_2018_02&or&status=%21closed&priority=critical&component=%21Mojave&or&status=%21closed&priority=blocker&component=%21Mojave&col=id&col=summary&col=milestone&col=priority&col=status&col=owner&col=type&col=component&col=reporter&order=priority ET_2018_02 tickets]

Minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-January/006013.html here]

== 2018-01-15 ==

* [RH] ET release planning
** date for release
** thorns to include
** items past inclusion deadline
** status of review requests
*** RNSID [https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests/3/new-initial-data-thorn-for-grhydro/diff pull request]
*** Giraffe [https://bitbucket.org/zach_etienne/wvuthorns/pull-requests/1/giraffe-review/diff pull request]

* [RH] ET US workshop at GT
** dates
** program
** committees
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-January/005998.html here]

== 2018-01-08 ==

* standing item: unanswered emails on list
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2018-January/005990.html here]

== 2017-12-04 ==
* [EB] [HV] Discussion on Cosmo/Particle WG [https://docs.google.com/document/d/1tN5m74VPJ18V9KKCXcGjD4yECsraoqQLy34B-EX0azc]
* [RH] ET tutorial machine moved to JetStream at TACC but still through NDS
* standing item: unanswered emails on list
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-December/005951.html here]

== 2017-11-27 ==
* [EB] [HV] Review of Cosmo/Particle WG [https://docs.google.com/document/d/1tN5m74VPJ18V9KKCXcGjD4yECsraoqQLy34B-EX0azc]
* [BG] Review of "Matter Codes" WG [https://docs.google.com/document/d/1i9a5pCqHLVGumLOqy5VEsBMaU42p9AtW_is3Inz7FlA/edit]
* [MZ] [BG] European ET workshop 2018
* [SB] Tutorial for new users https://www.einsteintoolkit.nationaldataservice.org
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-November/005927.html here]

== 2017-11-20 ==
* [RH] [SB] ET tutorial using jupyter: https://www.einsteintoolkit.nationaldataservice.org
* [RH] update mailing list to mailman 3.1
* [RH] RNSID review
* [GDA] Next ET Workshop
* [GDA] Review of ET Facebook page, who else should post?
* [GDA/ZE] First review of new WG: https://docs.google.com/document/d/1qiNeVgPlleg6Mjq9WI3iS--IA5o1FbpywAcq1Do_9xI/edit
* [GDA] Review of working groups
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-November/005905.html here]

== 2017-11-06 ==
* [RH] status update on the ET tutorial machine [http://lists.einsteintoolkit.org/pipermail/users/2017-November/005861.html]
* [RH] status update on the ET Jenkins server and failing tests
* [RH] working groups [https://docs.einsteintoolkit.org/et-docs/Working_List_of_ET_Groups]
* [RH] rework tutorials using methods of software carpentry [https://software-carpentry.org/]
* standing item: unanswered emails on list
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-November/005869.html here].

== 2017-10-30 ==
* [GA] Discussion of the EU ET Workshop -- what worked? what could be improved? where do we archive the google doc and photos etc? planning for next meeting?
* [GA] Working groups: proposed template and groups discussed at the workshop: look at first two pages of https://docs.google.com/document/d/1j12IEY8kH6R33qfXpD5BaDDXLEYdNceEqf9crLupsPs/edit
* [IH] Volunteers to answer unanswered questions on the ET list:
** [http://lists.einsteintoolkit.org/pipermail/users/2017-October/005829.html Is there any document of TwoPuncture's code?]
** [http://lists.einsteintoolkit.org/pipermail/users/2017-October/005792.html About the thorn Einstein exact]
* [HW] code optimization using pop-coe services (https://pop-coe.eu/services)
* [GA] Potential NSF funding opportunity: https://www.nsf.gov/pubs/2018/nsf18505/nsf18505.htm?WT.mc_id=USNSF_25&WT.mc_ev=click
* [MZ] [http://lists.einsteintoolkit.org/pipermail/users/2017-October/005835.html Change the behaviour of "copy" in CarpetLib/src/operators.hh?]
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-October/005842.html here].

== 2017-10-23 ==
* [ES] Introduce Nix https://nixos.org package manager for building Cactus dependencies
* [EB] Discuss the new ET video channel and how to incorporate it in einsteintoolkit.org
* [GA] Help with code optimization from Prace (email from Helvi)
* [HW] ET "starting body" for new users
* [GA] Discussion of the EU ET Workshop -- what worked? what could be improved? where do we archive the google doc and photos etc?
* [GA] Working groups: proposed template and groups discussed at the workshop: look at first two pages of https://docs.google.com/document/d/1j12IEY8kH6R33qfXpD5BaDDXLEYdNceEqf9crLupsPs/edit
* [GA] Trailer from EdFest: https://www.dropbox.com/s/qiyebml11nqr3r0/EdFest%20Trailer%202017.mp4?dl=0
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-October/005830.html here].

== 2017-10-16 ==

[This will likely overlap with a LIGO/Virgo announcement]

== 2017-10-09 ==

no meeting

== 02-Oct 2017 ==
* [RH] update on Euro ET workshop in Mallorca, Oct 11-14, http://grg.uib.es/EinsteinToolkit2017/
* [RH] thorns for inclusion: GiRaFFE, RNSID. Review status?
* [RH] Jenkins status update
* [RH] Comet lustre data corruption update
* [RH] Next ET release date
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-October/005787.html here].

== 25-Sep 2017 ==

* The cactusmaint@cactuscode.org email address is the one all users are directed to on cactuscode.org, and it seems to not work. Do we want to fix it, or just steer users to users@einsteintoolkit.org?
* Please send to Gabrielle Allen any pictures or movies that can be used for Edfest. A first version of the movie is here: https://www.dropbox.com/s/mpmcwmw6ewdklkf/EdFest.mp4?dl=0
* First working group added to wiki, along with policies, procedures -- suggest that the first meeting of each month includes a review of milestones. I didn't get to work on the others from the SI2 proposal this week :(.
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-September/005780.html here].

== 18-Sep 2017 ==
* Progress on new tutorial machine setup
Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-September/005772.html here].

== 11-Sep-2017 ==
* Demo of the RunView tool by Anna Neshyba and David Koppelman. This tool uses PAPI and CactusTimers to generate a graphical output (html) of Cactus performance.
* Is it time for a new release of Cactus? The lack of new releases led at least one online user to conclude that Cactus was a dead project. Perhaps we should have a new Cactus release with each release of the ET?
* Creation of a popular book about the science done by the Einstein Toolkit (Steven) -- I was thinking about ways to improve the visibility of the platform and attract new users and/or funding. Coincidentally, I've recently had some experience figuring out how to publish books on various platforms. These days it's fairly straightforward to publish books with no cost as paperback and ebook, or even hardcover. I was thinking that many of the people working on the ET could write a chapter, and I could handle the publishing. One can configure any level of profit for such endeavors, and I would like to suggest zero, since there are probably legal issues with the toolkit actually making money from such a thing. Does this sound like something people would be interested in?
* switch ExternalLibraries over to github: svn checkout https://github.com/rhaas80/GSL

Meeting minutes are [http://lists.einsteintoolkit.org/pipermail/users/2017-September/005769.html here].

== 28-Aug-2017 ==
* Status update on KNL
* update on Euro ET workshop in Mallorca, Oct 11-14, http://grg.uib.es/EinsteinToolkit2017/
* status of servers at LSU
** continued use of svn
** switch ExternalLibraries over to github: svn checkout https://github.com/rhaas80/GSL
Minutes: http://lists.einsteintoolkit.org/pipermail/users/2017-August/005739.html

== 21-Aug-2017 ==
* Progress on tutorial machine at NCSA
* Comments/discussion on updates to the Working Group Document (including procedures) (Gabrielle) https://docs.google.com/document/d/1j12IEY8kH6R33qfXpD5BaDDXLEYdNceEqf9crLupsPs
Minutes: http://lists.einsteintoolkit.org/pipermail/users/2017-August/005739.html

== 14-Aug-2017 ==
* Report on ET workshop survey (Nasir Eisty)
* NSF SI2 Project posted (Gabrielle Allen) https://figshare.com/articles/Einstein_Toolkit_Community_Integration_and_Data_Exploration/5306587
* Template for working groups: https://docs.google.com/document/d/1j12IEY8kH6R33qfXpD5BaDDXLEYdNceEqf9crLupsPs/edit?usp=sharing
* Discuss new code contributions
** RNSID

== 07-Aug-2017 ==

* Report from summer school and workshop:
** Summer school recordings etc. are here: https://docs.einsteintoolkit.org/et-docs/NCSAETK2017/setup
* Introduce working groups
* Discuss new code contributions
** GiRAFFE
** RNSID
* DataVault updates
Minutes: http://lists.einsteintoolkit.org/pipermail/users/2017-August/005706.html

meeting agenda

2018-08-06T16:48:25Z

Twright: meeting agenda moved to Meeting agenda: Capitalize titles; Newer MediaWiki will orphan pages with lowercase title names

#REDIRECT [[Meeting agenda]]