#369: Add command to update thorn list
---------------------------+------------------------------------------------
Reporter: eschnett | Owner: eric9
Type: defect | Status: new
Priority: minor | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
When the thorn list changes, then I have to run GetComponents --update
twice: first to update the thorn list, and then to actually check out
these thorns. Currently, I have to update all thorns twice, which is a
waste of time.
Ideally, GetComponents would first update the thorn list, then update
itself, then update everything else, and thus perform three passes over
the thorn list, but not perform the work three times. Can we achieve this
somehow? For example, we could mark the CRL script and the thorn lists
with special tags, and GetComponents would then perform the work in three
stages, restarting in between.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/369>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#575: McLachlan should use the kranc script instead of calling Mathematica
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: McLachlan |
-----------------------------------+----------------------------------------
Kranc provides a command-line interface and some useful code for catching
and displaying errors and improving on the default output. This is
accessed by running your script using the "kranc" command rather than
directly in Mathematica.
The attached patch modifies all the McLachlan scripts to work in this way.
Update to the latest Kranc to get proper error behaviour.
OK to apply?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/575>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#379: Python simfactory branch has a confusing name
------------------------+---------------------------------------------------
Reporter: hinder | Owner: mthomas
Type: defect | Status: new
Priority: minor | Milestone: ET_2011_11
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
The python version of simfactory is currently on the branch PYSIM_2010.
This should be just PYSIM.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/379>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#586: Syntax errors in make/make.config.rules.in
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: critical | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
The file make.config.rules.in contains shell syntax errors, e.g. in this
construct:
define NOTIFY_PREPROCESSING
{ if test "$(VERBOSE)" == "yes"; then echo Preprocessing $<; fi }
1. "test" doesn't know the "==" operator, it's "=" instead
2. Commands within { } need to be terminated by a semicolon
Also:
3. In other places, we allow both upper and lower case settings
And:
4. The { } seem superfluous here; the if ... fi already brackets the
statement
5. The VERBOSE variable could be checked by make, not by the shell
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/586>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#595: unused function in simfactory
-------------------------+--------------------------------------------------
Reporter: knarf | Owner: eschnett
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
The function ParseEnvCommands is not used in simfactory, and as far as I
can tell it is not doing what I think it should do. It should either be
fully implemented (but that may already be provided elsewhere), or be
removed.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/595>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#599: Avoid the need to escape wiki-words in ticket descriptions and messages
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit trac | Version:
Keywords: |
----------------------------------+-----------------------------------------
When writing a ticket description or adding a comment to a ticket, TRAC
currently converts any CamelCase words into links. We often have such
words when talking about the ET, as thorn names are of this form. Since
there are no pages with these names, such links are broken and render in
grey with a question-mark following them. I have not seen anyone use a
CamelCase link deliberately in a ticket (until this one!). To make these
words render properly, it is necessary to escape them by prepending a "!"
character. This is tedious, and is distracting when reading the email
version of the ticket.
I propose that the setting [https://trac.einsteintoolkit.org/wiki/TracIni
#wiki-section ignore_missing_pages] be used in the TracIni configuration
file. This will cause CamelCase words which do not correspond to existing
pages to render as plain text. This means an extra step when creating new
pages, but that is rare in comparison to writing tickets and comments.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/599>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#598: Point to other, similar codes
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
We should have a page on the ET web site that points to other, similar
open-source codes and infrastructures, be they 1D or 3D.
GR1D (stellarcollapse.org)
http://www.physik.unibas.ch/~liebend/download/index.html
Gadget?
Zeus?
Enzo?
Echo?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/598>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#594: Order of restriction and calls to POSTRESTRICTINITIAL in Initial timebin
--------------------+-------------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
in b4429f4006e5 CallRestrict in Evolve.cc was changed such that (as was
always the case in the git version), all restriction happens before the
first POSTRESTRICT routine is scheduled.
This patch does so in CallRestrict in Initialise.cc as well. Is currently
only triggered by WeylScal4 it seems (but would affect anything that does
a SYNC in MoL_PseudeoEvolution(Boundaries)).
The git version of Carpet always did this it seems.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/594>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#579: WeylScal4 needs to be scheduled after ADMBase_SetADMVars
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: critical | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
The ADM variables may be calculated in MoL_PseudoEvolution, the same bin
in which WeylScal4 is scheduled. If so, this order must be enforced.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/579>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit