#660: Make MHD multipatch-aware
-----------------------------------+----------------------------------------
Reporter: tbode | Owner: tbode
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
At least the Con2PrimM routines need to be multipatch-aware.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/660>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1690: The test system should treat a nonzero exit code from Cactus as a failure
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
The test system seems to ignore the fact that Cactus exits with a nonzero
exit code. It displays
Cactus exited with error code 1
Please check the logfile...
No files created in test directory
Success: 0 files identical
And in the summary at the end, it treats this as a passing test. In this
case, there were no test reference files and no files output, because the
test (by design) does not produce any data, it just aborts if the test
fails.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1690>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1523: Use Piraha to Parse all CCL files
-------------------------+--------------------------------------------------
Reporter: sbrandt | Owner:
Type: enhancement | Status: new
Priority: optional | Milestone: Cactus_4.3.0
Component: Cactus | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Piraha should be used to parse all the CCL files. This would give us a
well-defined grammar and the ability to let other tools use the CCL files
in a reliable way.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1523>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1658: ExternalLibraries/pciutils does not compile on Mac OS
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
When I try to compile ExternalLibraries/pciutils on Mac OS, I get
{{{
lspci.c:919:29: error: expected ')'
puts("lspci version " PCIUTILS_VERSION);
^
./pciutils.h:18:26: note: expanded from macro 'PCIUTILS_VERSION'
#define PCIUTILS_VERSION PCILIB_VERSION
^
lspci.c:919:11: note: to match this '('
puts("lspci version " PCIUTILS_VERSION);
}}}
This is with the osx-mountain-lion-macports-gcc.cfg optionlist, and "gcc-
mp-4.6 (MacPorts gcc46 4.6.4_3) 4.6.4".
I have to disable this thorn in my thornlist (or machine definition file)
to compile the ET. This means that the ET will not compile out of the box
on Mac OS.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1658>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1778: Scheduling WHILE Loops in CCTK_ANALYSIS Results in Hang
--------------------------------+-------------------------------------------
Reporter: zachetie@… | Owner:
Type: defect | Status: new
Priority: unset | Milestone:
Component: Other | Version: ET_2015_05
Keywords: |
--------------------------------+-------------------------------------------
When encountering a WHILE loop inside CCTK_ANALYSIS, Cactus simply hangs.
I have created a simple thorn, ScheduleTester, that reproduces this
problem 100% of the time. The thorn only takes as input the number of
iterations desired in the WHILE loop. I have attached this thorn, as well
as example .par and ThornList files to this ticket.
This problem is verified to exist within 2015_05 as well as 2014_11 ET
releases. I have not tried past releases.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1778>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#502: SimFactory user-guide should be available and updated automatically
-------------------------+--------------------------------------------------
Reporter: hinder | Owner: knarf
Type: enhancement | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
-------------------------+--------------------------------------------------
SimFactory has an incomplete user guide in the doc/userguide directory.
This is developed using Sphinx, which is a Python framework for writing
documentation. You need to install sphinx to generate this documentation.
This can be done using something similar to the following:
export PYTHONPATH=/home/ianhin/software/python
export PATH=/home/ianhin/software/python/:$PATH
hash -r
easy_install --install-dir ~/software/python sphinx
Then go into the simfactory/doc/userguide directory and type:
./autogen
make html
to generate HTML documentation (type just "make" to see the other possible
targets like PDF etc).
This should be regenerated on any commit to the SimFactory/doc/userguide
directory and copied to a web-accessible location for inclusion on
simfactory.org.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/502>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1698: The ET tickets should be tidied up
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit trac | Version: development version
Keywords: |
----------------------------------+-----------------------------------------
Many of the ET tickets have not seen much attention recently or at all.
We should have a session where we run though all the tickets and make sure
that their priorities/state etc are correct. Once we have done this, we
should come up with a strategy for keeping the tickets under control. In
the process, we should decide what is meant by the different ticket
priorities, and whether we need to add additional priorities or states to
allow us to more effectively manage the tickets.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1698>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#719: Mailing lists could have a link to the archived version of the message
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
It would be useful for the footer of a mailing list posting to contain a
URL to the archived version of the message so that it is easy to point
people to the message in an email. This would apply to both the Cactus
and the ET lists.
It appears that this is not straightforward in MailMan 2, but is expected
in version 3: http://mail.python.org/pipermail/mailman-
users/2011-October/072378.html.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/719>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit