Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #606: Support Peter's new load balancing scheme in Carpet
by Einstein Toolkit 07 Oct '11

07 Oct '11

#606: Support Peter's new load balancing scheme in Carpet -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- I just realise that Peter's new load balancing scheme is not yet available in Carpet; apparently, the respective enabling patch has not yet been committed. Also, there is a parameter "alpha" in this algorithm that is currently not initialised. This should become a Carpet parameter. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/606> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #603: Misleading error message regarding EOS_Omni
by Einstein Toolkit 06 Oct '11

06 Oct '11

#603: Misleading error message regarding EOS_Omni ------------------------+--------------------------------------------------- Reporter: azebrowski | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | ------------------------+--------------------------------------------------- Hello, I was getting this error: INFO (GRHydro): Trying to get EOS handles WARNING level 0 in thorn Bindings processor 0 host login2.uc.futuregrid.org (line 5193 of /gpfs/home/azebro1/Cactus/configs/sim/bindings/Functions/AliasedFunctions.c): -> The function EOS_Omni_GetHandle has not been provided by any thorn in your thornlist WARNING level 0 in thorn Bindings processor 0 host login2.uc.futuregrid.org (line 5193 of /gpfs/home/azebro1/Cactus/configs/sim/bindings/Functions/AliasedFunctions.c): -> The function EOS_Omni_GetHandle has not been provided by any thorn in your thornlist cactus_sim: /gpfs/home/azebro1/Cactus/arrangements/Carpet/Carpet/src/helpers.cc:237: int Carpet::Abort(const cGH*, int): Assertion `0' failed. But, in my thornlist, I had: EinsteinEOS/EOS_Omni # EOS_Omni ( ) [ ] { } The actual error here is that the thorn wasn't being activated (Thanks, Dr. Schnetter!) Hopefully this won't be too hard to fix :) -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/603> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #602: Problem with thorn EOS_Omni
by Einstein Toolkit 05 Oct '11

05 Oct '11

#602: Problem with thorn EOS_Omni --------------------------+------------------------------------------------- Reporter: Maxim Barkov | Type: defect Status: new | Priority: major Milestone: | Component: EinsteinToolkit thorn Version: ET_2011_05 | Keywords: --------------------------+------------------------------------------------- Hello, I have tried to compile the ET on my local PC. Ubuntu 11.04 2xXenon using the next procedure: make test1-config make test1 my ~/.cactus/config is follow ###################################### CC = gcc CXX = g++ F90 = gfortran F77 = gfortran MPI = OpenMPI MPI_LIBS = -lmpi MPI_LIB_DIRS = /usr/lib/ MPI_INC_DIRS = /usr/include/openmpi/ ############################################ After many outputs I get: ________________________________________________________________________ Checking status of thorn EOS_Omni ________________________________________________________________________ Preprocessing /home/bmv/utils/soft/develop/ET/Cactus/arrangements/EinsteinEOS/EOS_Omni/src/nuc_eos/readtable.F90 Compiling /home/bmv/utils/soft/develop/ET/Cactus/arrangements/EinsteinEOS/EOS_Omni/src/nuc_eos/readtable.F90 /home/bmv/utils/soft/develop/ET/Cactus/configs/test1/build/EOS_Omni/nuc_eos/readtable.f90:5.10: use hdf5 1 Fatal Error: Can't open module file 'hdf5.mod' for reading at (1): No such file or directory make[3]: *** [readtable.F90.o] Error 1 make[2]: *** [nuc_eos/make.checked] Error 2 make[1]: *** [/home/bmv/utils/soft/develop/ET/Cactus/configs/test1/lib/libthorn_EOS_Omni.a] Error 2 make: *** [test1] Error 2 Could you help me to solve this problem? Best wishes, Maxim -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/602> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #379: Python simfactory branch has a confusing name
by Einstein Toolkit 04 Oct '11

04 Oct '11

#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

1 8

[Einstein Toolkit] #586: Syntax errors in make/make.config.rules.in
by Einstein Toolkit 04 Oct '11

04 Oct '11

#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

1 18

[Einstein Toolkit] #595: unused function in simfactory
by Einstein Toolkit 01 Oct '11

01 Oct '11

#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

1 1

[Einstein Toolkit] #587: updates for zwicky files in simfactory/python
by Einstein Toolkit 01 Oct '11

01 Oct '11

#587: updates for zwicky files in simfactory/python -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: enhancement | Status: new Priority: optional | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- attached please find updates for zwicky in simfactory -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/587> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #599: Avoid the need to escape wiki-words in ticket descriptions and messages
by Einstein Toolkit 01 Oct '11

01 Oct '11

#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

1 1

[Einstein Toolkit] #598: Point to other, similar codes
by Einstein Toolkit 30 Sep '11

30 Sep '11

#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

1 0

[Einstein Toolkit] #594: Order of restriction and calls to POSTRESTRICTINITIAL in Initial timebin
by Einstein Toolkit 30 Sep '11

30 Sep '11

#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

1 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac