January 2018 - Trac - lists.einsteintoolkit.org

[Einstein Toolkit] #2105: Gallery examples should be tested
by Einstein Toolkit 30 Jul '18

30 Jul '18

#2105: Gallery examples should be tested ----------------------------+----------------------------------------------- Reporter: hinder | Owner: Type: task | Status: new Priority: major | Milestone: ET_2018_02 Component: Other | Version: development version Keywords: ReleaseProcess | ----------------------------+----------------------------------------------- The gallery examples at https://einsteintoolkit.org/gallery.html should be tested to make sure they work with the upcoming release. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2105> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1949: provide floating branch to "current release" and links to it
by Einstein Toolkit 17 Jul '18

17 Jul '18

#1949: provide floating branch to "current release" and links to it -----------------------------+---------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Other | Version: development version Keywords: EinsteinToolkit | -----------------------------+---------------------------------------------- In order to not always have to update all websites with the correct ULRs to the then current release it would be good if we were to provide a "current release" branch of the ET which always points to the head of the current release branch/tag. Ie right now it would be identical to 2016_05. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1949> 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] #1934: pciutils was broken
by Einstein Toolkit 05 Jul '18

05 Jul '18

#1934: pciutils was broken ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | ----------------------+----------------------------------------------------- ExternalLibraries/pciutils was broken; the configure.sh script references two patch files that were not there. I reverted the commit. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1934> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1906: CarpetRegrid2: possible off-by-one error when using regrid_every parameter
by Einstein Toolkit 28 Jun '18

28 Jun '18

#1906: CarpetRegrid2: possible off-by-one error when using regrid_every parameter ---------------------------+------------------------------------------------ Reporter: bmundim | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: development version Keywords: CarpetRegrid2 | ---------------------------+------------------------------------------------ I was working on a par file for a quick regridding test and found out an unexpected behaviour regarding regridding. Basically I want a par file with a few iterations such that it adds a refinement level every 4 iterations for example. I set the following parameters then: {{{ CarpetRegrid2::add_levels_automatically = "yes" CarpetRegrid2::regrid_every = 4 }}} for a grid structure as such: {{{ Cactus::cctk_itlast = 10 CoordBase::xmin = -0.5 CoordBase::ymin = -0.5 CoordBase::zmin = -0.5 CoordBase::xmax = 0.5 CoordBase::ymax = 0.5 CoordBase::zmax = 0.5 CoordBase::ncells_x = 16 CoordBase::ncells_y = 16 CoordBase::ncells_z = 16 Carpet::max_refinement_levels = 3 CarpetRegrid2::num_centres = 1 CarpetRegrid2::active_1 = "yes" CarpetRegrid2::num_levels_1 = 1 CarpetRegrid2::radius_1[1] = 0.12 CarpetRegrid2::radius_1[2] = 0.04 }}} I was expecting then regridding to happen at iterations 4 and 8, however if you run the attached par file, a modification of balsara shocktube test, you see that the level additions actually happen at iterations 5 and 9 instead: {{{ ... INFO (CarpetRegrid2): Increasing number of levels of centre 1 to 2 (it=5) ... INFO (CarpetRegrid2): Increasing number of levels of centre 1 to 3 (it=9) }}} which is apparently an off-by-one kind of error. I tracked down the code producing these messages and it comes from function CarpetRegrid2_RegridMaps at CarpetRegrid2/src/regrid.cc, lines 745 to 747. In order for that piece of code to execute we do have to have do_recompose set to true. Strangely the condition to set it, compares the previous iteration to the regrid_every parameter on line 707 of the same file: {{{ (cctk_iteration - 1) % regrid_every == 0 }}} Investigating if this actually makes sense I was led to what I think it might be the source of the problem on line 58 of Carpet/src/Evolve.cc. Time and iteration is advanced before calling CallRegrid. Skimming over the AdvanceTime routine it is not clear to me that it really needs to be called before CallRegrid. If it is really needed then why the condition to regrid or not is not taken on the current updated iteration as in: {{{ cctk_iteration % regrid_every == 0 }}} Thanks, Bruno -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1906> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1778: Scheduling WHILE Loops in CCTK_ANALYSIS Results in Hang
by Einstein Toolkit 28 Jun '18

28 Jun '18

#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

1 2

[Einstein Toolkit] #1992: provide bibtext snippets for requested cittations on ET website
by Einstein Toolkit 26 Jun '18

26 Jun '18

#1992: provide bibtext snippets for requested cittations on ET website ----------------------------+----------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus website | Version: development version Keywords: | ----------------------------+----------------------------------------------- Our citing page http://einsteintoolkit.org/documentation/licenses/ right now lists the bibtex key and the doi for the requested citations. It would be useful to make the bibtex keys hyperlinks to a bibtex fragment for the paper in question that could be copied and pasted into a user's bibtext file. If we don't want to use the fragment from our own einsteintoolkit.bib we could use INSPIRE's doe search facility using "bibtex" as the output format, eg: http://inspirehep.net/search?ln=en&ln=en&p=doi%3A10.1088%2F0264-9381%2F21%2… for the Carpet reference. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1992> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2025: ssl warning for wiki.einsteintoolkit.org
by Einstein Toolkit 11 Jun '18

11 Jun '18

#2025: ssl warning for wiki.einsteintoolkit.org -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: | -------------------------------------+-------------------------------------- My browser (Firefox 45.8.0 ESR) reports {{{ wiki.einsteintoolkit.org uses an invalid security certificate. The certificate is only valid for wiki.cct.lsu.edu Error code: SSL_ERROR_BAD_CERT_DOMAIN }}} for https://wiki.einsteintoolkit.org/ -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2025> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 11

[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] #1769: External libraries: moving towards multiarch library directory structure
by Einstein Toolkit 20 Mar '18

20 Mar '18

#1769: External libraries: moving towards multiarch library directory structure ----------------------------------------------+----------------------------- Reporter: bmundim | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2015_05 Component: EinsteinToolkit thorn | Version: development version Keywords: ExternalLibraries HDF5 Multiarch | ----------------------------------------------+----------------------------- Several Linux distributions have already started to move their libraries to a new directory structure that reflects the target architecture and allows the installation of packages from multiple architectures in the same system. The following links provide more details of this change: {{{ https://wiki.debian.org/Multiarch/TheCaseForMultiarch https://wiki.ubuntu.com/MultiarchSpec }}} This change potentially affects several of external library scripts shipped with ET. For example the HDF5/src/detect.sh script is not able to detect the hdf5 libraries installed in the directory /usr/lib/x86_64 -linux-gnu for Ubuntu 14.04.2 LTS. I have attached a simple patch to remedy this issue and open a discussion on the best way to proceed here. This patch does depend on the availability of gcc on the system. It currently works fine for me, but we might need a better solution for systems without gcc. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1769> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 40

[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] #1946: sim setup should create a section for the current machine
by Einstein Toolkit 26 Feb '18

26 Feb '18

#1946: sim setup should create a section for the current machine -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: development version Keywords: | -------------------------+-------------------------------------------------- When calling sim setup on a machine in the machine data base (eg bluewaters in my case) it it still creates only a {{{[default]}}} section in defs.local.ini which means that the account information and possibly non-default sourcebasedir are not used for bluewaters leading to hard to understand error messages later on. I would thus like to suggest to change sim setup such that instead (or in addition to) a "[default]" section it creates a section for the detected machine if it already knows this machine. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1946> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #2109: Write the release announcement
by Einstein Toolkit 26 Feb '18

26 Feb '18

#2109: Write the release announcement ----------------------------+----------------------------------------------- Reporter: hinder | Owner: sbrandt Type: task | Status: new Priority: major | Milestone: ET_2018_02 Component: Other | Version: development version Keywords: ReleaseProcess | ----------------------------+----------------------------------------------- The release announcement for the upcoming release needs to be written. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2109> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #2093: Show if this machine matches the mdb
by Einstein Toolkit 26 Feb '18

26 Feb '18

#2093: Show if this machine matches the mdb -------------------------+-------------------------------------------------- Reporter: sbrandt | Owner: Type: enhancement | Status: new Priority: unset | Milestone: Component: SimFactory | Version: development version Keywords: | -------------------------+-------------------------------------------------- It would be useful if Simfactory could tell you whether your machine matches something in the mdb. This pull request makes that work. See pull request: https://bitbucket.org/simfactory/simfactory2/pull-requests/23/show-this- machine/diff -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2093> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #2050: cctk_startupxxx is a valid group
by Einstein Toolkit 23 Feb '18

23 Feb '18

#2050: cctk_startupxxx is a valid group ---------------------+------------------------------------------------------ Reporter: sbrandt | Owner: sbrandt Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | ---------------------+------------------------------------------------------ Currently, the "at" keyword in the schedule.ccl file is supposed to report an error if one is scheduling in a group that is not present at startup. It detects this with a regexp, but the regexp does not include boundaries. As such cctk_startupxxx is considered valid. In addition, the new parser is failing to report a CST error for this violation regardless of group name. The attached patch to the schedule parser fixes both defects. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2050> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 24

[Einstein Toolkit] #2108: Tutorial should be tested
by Einstein Toolkit 19 Feb '18

19 Feb '18

#2108: Tutorial should be tested ----------------------------+----------------------------------------------- Reporter: hinder | Owner: Type: task | Status: new Priority: major | Milestone: ET_2018_08 Component: Other | Version: development version Keywords: ReleaseProcess | ----------------------------+----------------------------------------------- The Einstein Toolkit tutorials should be tested for the upcoming release. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2108> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 17

[Einstein Toolkit] #2084: error in thorn Vectors
by Einstein Toolkit 14 Feb '18

14 Feb '18

#2084: error in thorn Vectors ---------------------------------+------------------------------------------ Reporter: babiuc@… | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | ---------------------------------+------------------------------------------ Checking status of thorn Vectors COMPILING arrangements/CactusUtils/Vectors/src/vectors.cc In file included from /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors.h:18:0, from /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors.cc:1: /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors-4-SSE.h: In function 'CCTK_REAL4 k4sum(CCTK_REAL4_VEC)': /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors-4-SSE.h:709:29: error: '_mm_hadd_ps' was not declared in this scope CCTK_REAL4_VEC const x2 = _mm_hadd_ps(x1, x1); ^~~~~~~~~~~ /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors-4-SSE.h:709:29: note: suggested alternative: '_mm_add_ps' CCTK_REAL4_VEC const x2 = _mm_hadd_ps(x1, x1); ^~~~~~~~~~~ _mm_add_ps In file included from /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors.h:30:0, from /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors.cc:1: /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors-8-SSE2.h: In function 'CCTK_REAL8 k8sum(CCTK_REAL8_VEC)': /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors-8-SSE2.h:753:29: error: '_mm_hadd_pd' was not declared in this scope CCTK_REAL8_VEC const x2 = _mm_hadd_pd(x1, x1); ^~~~~~~~~~~ /Users/babiuc/Cactus/arrangements/CactusUtils/Vectors/src/vectors-8-SSE2.h:753:29: note: suggested alternative: '_mm_add_pd' CCTK_REAL8_VEC const x2 = _mm_hadd_pd(x1, x1); ^~~~~~~~~~~ _mm_add_pd make[4]: *** [vectors.cc.o] Error 1 make[3]: *** [make.checked] Error 2 make[2]: *** [/Users/babiuc/Cactus/configs/ET/lib/libthorn_Vectors.a] Error 2 make[1]: *** [ET] Error 2 make: *** [ET-rebuild] Error 2 -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2084> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2103: Documentation web pages should be regenerated
by Einstein Toolkit 07 Feb '18

07 Feb '18

#2103: Documentation web pages should be regenerated ----------------------------+----------------------------------------------- Reporter: hinder | Owner: Type: task | Status: new Priority: major | Milestone: ET_2018_02 Component: Other | Version: development version Keywords: ReleaseProcess | ----------------------------+----------------------------------------------- The documentation web pages need to be regenerated: * https://einsteintoolkit.org/usersguide/UsersGuide.html * https://einsteintoolkit.org/documentation/ThornGuide.php * https://einsteintoolkit.org/referencemanual/ReferenceManual.html -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2103> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #2097: Jenkins test system should use generic.cfg where possible
by Einstein Toolkit 05 Feb '18

05 Feb '18

#2097: Jenkins test system should use generic.cfg where possible -------------------------+-------------------------------------------------- Reporter: hinder | Owner: hinder Type: enhancement | Status: new Priority: minor | Milestone: ET_2018_02 Component: Jenkins | Version: development version Keywords: | -------------------------+-------------------------------------------------- We now recommend using generic.cfg instead of OS-specific optionlists, so the Jenkins test system should do the same. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2097> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #2077: include RNSID in ET
by Einstein Toolkit 02 Feb '18

02 Feb '18

#2077: include RNSID in ET -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: Hydro_RNSID | -----------------------------------+---------------------------------------- Pull request is here: https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests/3 /new-initial-data-thorn-for-grhydro/diff It generate ID for rotating star either with uniform rotational profile or describe by differentialy rotating j-law. testsuite par file provided and tested example of usage parfile in par subdirectory as perl script that generate par file with resolution dx=0.75 suited for workstation tests. Hydro_RNSID/par/speed.rpar generate par file usefull to peform speed test two stand alone utility are generate at compile time to [RNS] generate initial models (to be imported in Cactus) amd to read [RNS_read] the generated initial model -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2077> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2018