Services

2018-01-25T20:42:08Z

Hinder: /* Build and test */

The Einstein Toolkit depends on a number of services managed by the ET maintainers. Here we list each of these, and give any relevant information. Ideally, this page should be sufficient for a maintainer to deal with urgent issues relating to these services in case the primary administrator is unavailable.

== Website ==

* https://einsteintoolkit.org
* Location: A VM at CCT
* Administrator: Frank Loeffler (in future Steve Brandt)

== Wiki ==

* https://docs.einsteintoolkit.org/et-docs/
* Location: ??
* Administrator: Frank Loeffler (in future Steve Brandt)

== Subversion ==

* https://svn.einsteintoolkit.org
* Location: A VM at CCT
* Administrator: Frank Loeffler (in future Steve Brandt)

== TRAC ==

* https://trac.einsteintoolkit.org
* Location: A VM at CCT
* Administrator: Steve Brandt
* The trac machine is the same as svn.cactuscode.org. It is installed in /svn/trac. If one has root access, and the need arises, one can administer it with the trac-admin command line tool.

== Mailing lists ==

* http://lists.einsteintoolkit.org/mailman/listinfo
* Location: ?

== Cactus services? ==

== Domain ==

* einsteintoolkit.org
* Owned by LSU
* Notes: Cannot point subdomains to any machines not controlled directly by LSU

== Build and test ==

* https://build-test.barrywardell.net
* Location: A VM in NCSA Nebula
* Administrator: Ian Hinder
* Detailed documentation at [[BuildAndTest]]
* Notes:
** Jenkins runs on the build master, and can connect to a variety of build nodes. One such node is also hosted on Nebula, and is currently (10-May-2017) the only working build node.
** Depends on the git super-repository https://bitbucket.org/einsteintoolkit/einsteintoolkit
** A login node for people to test failures on a system very similar to the build node is available at login.barrywardell.net. Contact Ian Hinder for access.

== Git updater ==

* et.barrywardell.net
* Location: A VM in NCSA Nebula
* Administrator: Ian Hinder
* Notes:
** This server periodically updates its local copies of the ET repositories and updates the git super-repository at https://bitbucket.org/einsteintoolkit/einsteintoolkit/. It also hosts and updates git-svn mirrors of the subversion repositories needed for the ET, so that the super-repository can use them.

Services

2018-01-25T20:41:40Z

Hinder: /* Build and test */

The Einstein Toolkit depends on a number of services managed by the ET maintainers. Here we list each of these, and give any relevant information. Ideally, this page should be sufficient for a maintainer to deal with urgent issues relating to these services in case the primary administrator is unavailable.

== Website ==

* https://einsteintoolkit.org
* Location: A VM at CCT
* Administrator: Frank Loeffler (in future Steve Brandt)

== Wiki ==

* https://docs.einsteintoolkit.org/et-docs/
* Location: ??
* Administrator: Frank Loeffler (in future Steve Brandt)

== Subversion ==

* https://svn.einsteintoolkit.org
* Location: A VM at CCT
* Administrator: Frank Loeffler (in future Steve Brandt)

== TRAC ==

* https://trac.einsteintoolkit.org
* Location: A VM at CCT
* Administrator: Steve Brandt
* The trac machine is the same as svn.cactuscode.org. It is installed in /svn/trac. If one has root access, and the need arises, one can administer it with the trac-admin command line tool.

== Mailing lists ==

* http://lists.einsteintoolkit.org/mailman/listinfo
* Location: ?

== Cactus services? ==

== Domain ==

* einsteintoolkit.org
* Owned by LSU
* Notes: Cannot point subdomains to any machines not controlled directly by LSU

== Build and test ==

* https://build-test.barrywardell.net
* Location: A VM in NCSA Nebula
* Administrator: Ian Hinder
* Notes:
** Jenkins runs on the build master, and can connect to a variety of build nodes. One such node is also hosted on Nebula, and is currently (10-May-2017) the only working build node.
** Depends on the git super-repository https://bitbucket.org/einsteintoolkit/einsteintoolkit
** A login node for people to test failures on a system very similar to the build node is available at login.barrywardell.net. Contact Ian Hinder for access.
** Many more details are available at [[BuildAndTest]]

== Git updater ==

* et.barrywardell.net
* Location: A VM in NCSA Nebula
* Administrator: Ian Hinder
* Notes:
** This server periodically updates its local copies of the ET repositories and updates the git super-repository at https://bitbucket.org/einsteintoolkit/einsteintoolkit/. It also hosts and updates git-svn mirrors of the subversion repositories needed for the ET, so that the super-repository can use them.

BuildAndTest

2018-01-25T20:40:30Z

Hinder:

Adding a test case

2018-01-22T16:00:51Z

Hinder:

=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

Meeting agenda

2018-01-22T15:06:26Z

Hinder:

<onlyinclude><includeonly><ul><li></includeonly>The link for the call is: https://hangouts.google.com/hangouts/_/stevenrbrandt.com/etcall. '''After connecting, you will need to wait for the moderator to add you to the call'''.
<includeonly></li></includeonly><includeonly><li>Today's [[meeting_agenda|meeting agenda]] is on this wiki too.</li></ul></includeonly></onlyinclude>
When adding a topic, please add your '''name''' next to the item you are proposing.
Meetings are every Monday at 9:00 AM US Central time.

== 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]

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

== 2018-01-08 ==

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

== 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]

== 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]

== 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]

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

Editing the Einstein Toolkit website

2017-11-20T15:49:34Z

Hinder: /* Overview */

==== Overview ====

The Einstein Toolkit website is at https://einsteintoolkit.org. The source is hosted in a BitBucket Git repository at https://bitbucket.org/einsteintoolkit/www.

To contribute, you can either fork the repository on BitBucket and open a pull request, or ask maintainers@einsteintoolkit.org for write access via your BitBucket account.

Changes pushed to the master branch appear after a few seconds on the website.

For example, if you have write access,

git clone https://bitbucket.org/einsteintoolkit/www.git

Edit and test the website cloned into www, then commit and push.

git commit -a
git push

Meeting agenda

2017-10-27T08:39:06Z

Hinder: /* 2017-10-30 */

<onlyinclude>

The link for the call is: https://hangouts.google.com/hangouts/_/stevenrbrandt.com/etcall. '''After connecting, you will need to wait for the moderator to add you to the call'''.
<includeonly>Today's [[meeting_agenda|meeting agenda]] is on this wiki too.</includeonly>
</onlyinclude>
When adding a topic, please add your '''name''' next to the item you are proposing.

== 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?
* [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
* [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]

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

2017-08-09T16:52:30Z

Hinder:

=2017-08-08: Algorithm notes=

Have three sets of equations:

1. RK4
2. ys in ks
3. ks in ys

Algorithm for unigrid evolution of existing data at t_n:

* Use RK4 to set y_{n+1}
* Repeat

Algorithm for 2-level evolution of existing data at t_n:

* Evolve coarse grid using RK4. Keeps the ks in gridfunctions and y_n and y_{n+1}.
* Spatially prolongate the coarse ks to the fine ks in the RB
* Save y_{n+1} on the RB using "ys in ks" and the prolongated coarse grid ks
* Compute fine ks from coarse ks on the RB using "ys in ks" at th=0 then "ks in ys"
* Compute f(Y1) using the RHS function on the interior
* Set k1 using RK4 on the interior
* k1 is now set everywhere
* Set Y2 using RK4
* Set k2 using RK4 on the interior
* Already have fine k2 on RB
* Set Y3 using RK4
* Set k3 using RK4 on the interior
* Already have fine k3 on RB
* Set Y4 from RK4
* Set k4 from RK4 on the interior
* Do not have k4 on the RB
* Set y_{n+1} using RK4 on the interior
* Restore the saved y_{n+1} on the RB
* Now have y_{n+1} everywhere
* Spatially prolongate the coarse ks to the fine ks in the RB (either do this again, or don't overwrite the ks. if we are using efficient RK4, we might not be setting the same k variables directly * anyway, so this isn't an issue?)
* Compute the fine grid ks from the coarse ks in the RB using "ys in ks" at th=1 then "ks in ys"
* Repeat RK4 steps to advance fine grid to t_{n+2}

Current Carpet/MoL algorithm:

* t_n, t_{n-1} and t_{n-2} initialised by ID
* Compute f in interior
* MoL_Add to compute Y2
* Prolongate Y2 from coarse grid
* Compute f in interior
* MoL_Add to compute Y3
* Prolongate Y2 from coarse grid
* Compute f in interior
* MoL_Add to compute Y4
* Prolongate Y2 from coarse grid
* Compute f in interior
* Accumulate vars into y_{n+1}
* Prolongate Y2 from coarse grid

How can we implement the new algorithm?

Suppose we only prolongate the ks once, at t_n. RHSs computed as normal on the interior. Schedule a new function before MoL_Add to set the rhs variables to 1/dt k_i where these k_i are computed using the prolongated k variables using ks in ys and ys in ks.

=2017-08-09: Schedule=

{| {{PrettyTable}}
|+Schedule
|-
|CCTK_INITIAL
|State vector set at t=0
|-
|CCTK_EVOL
|Time and iteration variables advanced. Time and iteration variables advanced
|-
|MoL_InitialCopy
|Copy tl1 into tl0 (reverting Cactus tl rotation)
|}