#608: Improve colour scheme on http://einsteintoolkit.org/release-
info/parse_testsuite_results.php
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
The green checkmarks on the grey background are difficult to see, and are
difficult to distinguish from a missing checkmark. Either missing
checkmarks should be emphasized (e.g. by a large blue dot?), or the colour
scheme of the green needs to be improved, e.g by using a white background
for the green.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/608>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#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
#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
#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
#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