Search Mailing List and Tickets

Users Mailing List

The Einstein Toolkit Consortium is aiming to cultivate a self-supporting and open community and we encourage you to write to the mail list with your questions about the use of the toolkit or browse its archive.

Commits Mailing List

Commits to most version control repositories within the Einstein Toolkit are announced to the mailing list

Cactus mailing lists

Traditionally the Einstein Toolkit has focused on Cactus based codes and subscribing to the various Cactus mailing lists may be useful.

Bug Tracker

Issues (bugs, wish-list items, tasks) are recorded in a database. There they can be discussed, flagged, and assigned to developers. Don't hesitate to report problem you might have found: reporting problems is the first step in helping to solve them using our bug tracker. Update notifications for issues in all Einstein Toolkit related repositories are centrally available on the bug tracking mailing list is another way to get support maybe even faster and more interactively. We are currently exploring using the channel EinsteinToolkit/EinsteinToolkit on as a modern replacement for IRC. No client is needed though any native Matrix client can be used. You will need a GitHub, GitLab, or Twitter account to use it.

Weekly Calls

The Einstein Toolkit holds a weekly, public call to discuss various items coming up while developing, using and releasing the toolkit. Everyone is invited to join, may it only be to listen in. Please see the weekly agenda for call in instructions and topics to be discussed.


Minutes of the meetings are posted to as well as to the agenda wiki page.

General guideline for questions

When asking for help in the mail list, try to describe your problem according to the following suggestions. This will make it easier for others to help you and potentially aid users with similar problems in the future.

  • What operating system, OS version, processor, and package manager are you using? If you are using a cluster, please include its name and URL of a website describing it, if possible.
  • Try to share information and files relevant to the case. If you have compilation problems using SimFactory, send the make.log file after running the command
     VERBOSE=yes simfactory/bin/sim build -j1 2>&1 | tee make.log 
    as well as the configuration file in configs/sim/OptionList. If you have trouble with a simulation run foo, send the foo.out and foo.err logs and the used parameter file if possible.
  • If a lot of text is copy-pasted into the email's body and makes it difficult to read, add the relevant files as attachments to the mail. They will be accessible from the archive page of the mailing list and all the subscribing users will be able to access them on their own email clients.
  • If the attachments are too large, you will be notified by the mailing list that your message awaits moderator's approval and given the choice to cancel the sending.