Dear ET users,
I am trying to compile the latest release of the Einstein Toolkit,
Ørsted, on my laptop (Fedora 17, gcc-4.7.2), but I get the following
error if I try to compile with OpenMP:
/home/davide/Desert/CactusOersted/configs/charon/build/Carpet/Recompose.cc:2071:2: error: stray ‘#’ in program
the error disappears if I compile with no OpenMP support.
I can also compile without problems, using the same thornlist and with
OpenMP support, on our local cluster with the Intel compiler.
It looks like a compiler bug to me, but I am not sure about what exactly
is triggering it... Do you have any idea of what could be going wrong?
Cheers,
David
--
http://numrel.aei.mpg.de/people/radice
Hi
Please consider joining the weekly Einstein Toolkit phone call at
10 am US central time on Mondays. As usual, you can find instructions
how to join on the following web site:
http://einsteintoolkit.org/community/support/
I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and
the conference id is 118682#.
After the Ørsted release last week [1] development is again open and we
will discuss what to tackle next, e.g., what we plan to include in the
release next spring. There are still some issues to be looked at in
terms of MHD. Also, some tickets have been postponed for the next
release, mostly because it was too late to fix them for the current
one. Now would be the perfect time to look at these: [2].
As an afterthought, the release and the developers workshop again
produced a nice 'dip' in the number of open tickets and a corresponding
increase in closed tickets. The about half-yearly release cycle is quite
visible in these numbers and shows the importance of doing the releases
[3].
Having said that, currently 13 tickets are awaiting review [4]. Please
consider looking at one of them to help getting it closed.
Frank Löffler
[1]
http://einsteintoolkit.org/about/releases/ET_2012_11_announcement.php
[2]
https://trac.einsteintoolkit.org/query?status=%21closed&milestone=ET_2013_0…
[3] https://trac.einsteintoolkit.org/stats/tickets
[4]
https://trac.einsteintoolkit.org/query?status=review&col=id&col=summary&col…
We are pleased to announce release 4.1.0 of the Cactus computational
toolkit. This release includes support for new architectures, changes to
MPI configuration and comes bundled with supporting tools like
GetComponents and Simfactory. In addition, bug fixes accumulated since
the previous release in October 2011 have been included.
This release was tested and released together with the sixth release
(code name "Ørsted") of the Einstein Toolkit [1], and is used by that.
For more detailed information about the 4.1.0 release please read the
long release announcement on the Cactus Toolkit web pages:
http://cactuscode.org/download/releasenotes/Cactus_4.1.0
On behalf of the Cactus release team, Frank Löffler
[1]
http://einsteintoolkit.org/about/releases/ET_2012_11_announcement.php
We are pleased to announce the sixth release (code name "Ørsted") of the
Einstein Toolkit, an open, community developed software infrastructure
for relativistic astrophysics. This release includes various
improvements to the MHD handling within GRHydro, and improvements to the
Cactus flesh. In addition, bug fixes accumulated since the previous
release in May 2012 have been included.
The Einstein Toolkit is a collection of software components and tools
for simulating and analyzing general relativistic astrophysical systems
that builds on numerous software efforts in the numerical relativity
community including CactusEinstein, the Carpet AMR infrastructure and
the relativistic hydrodynamics code GRHydro (an updated and extended
version of the public release of the Whisky code). The Cactus Framework
is used as the underlying computational infrastructure providing
large-scale parallelization, general computational components, and a
model for collaborative, portable code development. The toolkit includes
modules to build complete codes for simulating black hole spacetimes as
well as systems governed by relativistic hydrodynamics.
The Einstein Toolkit uses a distributed software model and its different
modules are developed, distributed, and supported either by the core
team of Einstein Toolkit Maintainers, or by individual groups. Where
modules are provided by external groups, the Einstein Toolkit
Maintainers provide quality control for modules for inclusion in the
toolkit and help coordinate support. The Einstein Toolkit Maintainers
currently involve postdocs and faculty from six different institutions,
and host weekly meetings that are open for anyone to join in.
Guiding principles for the design and implementation of the toolkit
include: open, community-driven software development; well thought out
and stable interfaces; separation of physics software from computational
science infrastructure; provision of complete working production code;
training and education for a new generation of researchers.
For more information about using or contributing to the Einstein
Toolkit, or to join the Einstein Toolkit Consortium, please visit our
web pages at <http://einsteintoolkit.org>.
The Einstein Toolkit is primarily supported by NSF
1212401/1212426/1212433/1212460, 0903973/0903782/0904015 (CIGR), and
also by 0905046/0941653 (PetaCactus) and 0710874 (LONI Grid).
The Einstein Toolkit contain over 170 regression test cases. On a large
portion of the tested machines, all of these testsuites pass, using both
MPI and OpenMP parallelization.
All repositories participating in this release carry a branch ET_2012_11
marking this release. These release branches will be updated if severe
errors are found.
For more detailed information about the "Ørsted" release please read the
long release announcement on the Einstein Toolkit web pages:
http://einsteintoolkit.org/about/releases/ET_2012_11_announcement.php.
The "Ørsted" Release Team on behalf of the Einstein Toolkit Consortium
(2012-11-08)
Eloisa Bentivegna
Tanja Bode
Peter Diener
Roland Haas
Ian Hinder
Frank Löffler
Bruno Mundim
Christian D. Ott
Erik Schnetter
November 8, 2012
Hello
I would like to inquire about any left-over issues holding up the
release. So far, only one ticket is still open, has an applied patch and
only waits for test results:
https://trac.einsteintoolkit.org/ticket/434.
Is there anything else that somebody considers holding up the release?
If I don't receive anything by about noon today we will release
* today *
Frank Löffler
Present were: Frank, Roland, Bruno, Eloisa, Steve, Peter, Tanja, Ian,
Yosef, Josh
ET release:
* Fank has created svn release branches, git branches will be created today
* release notes are available at:
https://docs.einsteintoolkit.org/et-docs/Release_Details both short and
long would benefit from input
* we will release independent of MHD paper status and create tags for
the code version used in the paper once we have a version that works
* we have two outstanding ticket tickets for the release:
https://trac.einsteintoolkit.org/ticket/68https://trac.einsteintoolkit.org/ticket/434
* ticket 68 concerns GetComponent hanging on subversion errors
concerning invalid templates. A patch (actually two different ones) is
provided but would need testing, ideally on machines where the error occurs.
* ticket 434 concerns the excluded in Carpet's reduction mask
- we had a lively discussion whether this is critical or can be ignored.
Not final decision was reached.
- two options are possible:
-- leave as is and release with note about warning
-- increase warning level/make dependent on verbosity parameter
- the later requires that we understand that the error is benign
- Roland will reproduce the error with trunk code and qc0-mclachlan in
the release code. Will attach error and parfile to ticket.
MHD paper:
* will have phone call after the ET call
Yours,
Roland
Hi
Please consider joining the weekly Einstein Toolkit phone call at
10 am US central time on Mondays. As usual, you can find instructions
how to join on the following web site:
http://einsteintoolkit.org/community/support/
I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and
the conference id is 118682#.
This week we will concentrate on the release. The release branches will
be created Monday, so we will probably not release that day. However,
Tuesday or Wednesday should be possible, assuming everything works out.
Concerning remaining issues with the MHD paper I propose to let that
hold up the release.
We will use this call to discuss any remaining issues.
Please take a look at tickets concerning the release:
https://trac.einsteintoolkit.org/ticket/68https://trac.einsteintoolkit.org/ticket/434
and also more generally tickets open for review (14):
https://trac.einsteintoolkit.org/query?status=review&group=component&col=id…
Frank Löffler
Hi,
For some reason, the automated tests are taking a very long time to run; more than the one hour wall time which I have given them. They used to run in under 10 minutes. Has something changed recently that could explain this, or should I look for problems on the cluster?
--
Ian Hinder
http://numrel.aei.mpg.de/people/hinder