Trac January 2015

trac@lists.einsteintoolkit.org

1 participants
123 discussions

[Einstein Toolkit] #1523: Use Piraha to Parse all CCL files
by Einstein Toolkit 02 Aug '18

02 Aug '18

#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

1 11

[Einstein Toolkit] #1658: ExternalLibraries/pciutils does not compile on Mac OS
by Einstein Toolkit 05 Jul '18

05 Jul '18

#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

1 3

[Einstein Toolkit] #502: SimFactory user-guide should be available and updated automatically
by Einstein Toolkit 22 May '18

22 May '18

#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

1 6

[Einstein Toolkit] #1698: The ET tickets should be tidied up
by Einstein Toolkit 22 May '18

22 May '18

#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

1 6

[Einstein Toolkit] #719: Mailing lists could have a link to the archived version of the message
by Einstein Toolkit 21 May '18

21 May '18

#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

1 18

[Einstein Toolkit] #1368: add env option for commands in .mojave.xml
by Einstein Toolkit 07 May '18

07 May '18

#1368: add env option for commands in .mojave.xml -------------------------+-------------------------------------------------- Reporter: sbrandt | Owner: sbrandt Type: enhancement | Status: new Priority: major | Milestone: Cactus_4.3.0 Component: Mojave | Version: Keywords: | -------------------------+-------------------------------------------------- add env option for commands in .mojave.xml -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1368> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1471: Cactus should auto-detect newer versions of GCC from MacPorts
by Einstein Toolkit 30 Apr '18

30 Apr '18

#1471: Cactus should auto-detect newer versions of GCC from MacPorts -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Currently, during Cactus configuration without an optionlist on Mac OS, I get {{{ checking for gcc-mp-4.4... no checking for gcc-mp-4.3... no checking for gcc-mp-4.2... no checking for gcc... gcc checking whether the C compiler (gcc ) works... yes }}} I have gcc-mp-4.6, and 4.7 and 4.8 are also available in macports. The configure script should be updated to detect these versions. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1471> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

2 11

[Einstein Toolkit] #1170: ExtrenalLibraries handle XXX_DIR XXX_INC_DIRS and XXX_LIB_DIRS incosistently
by Einstein Toolkit 20 Mar '18

20 Mar '18

#1170: ExtrenalLibraries handle XXX_DIR XXX_INC_DIRS and XXX_LIB_DIRS incosistently -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: ExternalLibraries | -----------------------------------+---------------------------------------- This is a companion ticket to #1006. Different thorns (eg. MPI and HDF5 and LAPACK) handle XXX_DIR and XXX_INC_DIRS etc differently. MPI for example sets the include path to $MPI_DIR/include if MPI_INC_DIRS is not explicitly set and to MPI_INC_DIRS if it is set. HDF5 has no HDF5_INC_DIRS option and always sets the include path to HDF5_DIR/include. LAPACK has not INC_DIRS option and sets the linker path to LAPACK_DIR while the other two thorns set it to XXX_DIR/lib (unless overridden by MPI_LIB_DIRS in the case of MPI). I would be good to present a uniform set of option for all these thorns. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1170> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1474: compile ExternalLibraries with other thorns rather than when CST runs
by Einstein Toolkit 20 Mar '18

20 Mar '18

#1474: compile ExternalLibraries with other thorns rather than when CST runs -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Compiling external libraries takes a long time by now. Currently this happens very early in the compilation phase, before the other thorns are compiled. It would be better if the compilation happened at the same time as that of other thorns. This will entail splitting the configuration ie. detecting whether to build the included source or use a system wide copy from the compilation, most likely either using Cactus makefile variables or temporary files to transfer the decisions from the configuration stage to the build stage. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1474> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #1725: Disable Fortran 77 support in Cactus
by Einstein Toolkit 24 Jan '18

24 Jan '18

#1725: Disable Fortran 77 support in Cactus -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | -------------------------+-------------------------------------------------- There are no "Fortran 77" compilers any more. Cactus currently distinguishes between FCODE and F90CODE (pure Fortran 77, and Fortran 90). The pure Fortran 77 code has less argument checking etc. and is less safe, and is not needed any more. It should be removed, both from the makefile system as well as from the CST that auto-generates code. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1725> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2015