Trac April 2011

trac@lists.einsteintoolkit.org

1 participants
139 discussions

[Einstein Toolkit] #162: Document CCTK_GFINDEX3D and friends in reference manual
by Einstein Toolkit 23 Oct '11

23 Oct '11

#162: Document CCTK_GFINDEX3D and friends in reference manual ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- I believe the reference manual does not describe any of the CCTK_GFINDEX* and CCTK_VECTGFINDEX* functions. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/162> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #367: When a repo URL changes, GetComponents should offer more help
by Einstein Toolkit 19 Oct '11

19 Oct '11

#367: When a repo URL changes, GetComponents should offer more help ---------------------------+------------------------------------------------ Reporter: eschnett | Owner: eric9 Type: enhancement | Status: new Priority: major | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ When a repo URL changes, GetComponents currently suggests to check out the repo from scratch (and presumably delete/ignore the old repo). This is very inflexible, in particular when the user has changes in the old repository, which often happens during development. SVN (and presumably all other VC software) offer commands to update the URL, so that one can keep the current checkout. Of course, this makes only sense if this is the same repository that only moved to a new URL, but this seems to happen often enough. GetComponents should at least output instructions for updating the URL. It would be even better if GetComponents detected that new and old repo are the same, and then update the repo URL by itself. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/367> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #414: --parallel option not documented in GetComponents
by Einstein Toolkit 19 Oct '11

19 Oct '11

#414: --parallel option not documented in GetComponents ---------------------------+------------------------------------------------ Reporter: bmundim | Owner: eric9 Type: defect | Status: new Priority: minor | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ The --parallel option is not documented in both versions of GetComponents, the released and development ones. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/414> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #219: ExternalLibraries method should be documented
by Einstein Toolkit 19 Oct '11

19 Oct '11

#219: ExternalLibraries method should be documented ---------------------------+------------------------------------------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: documentation | ---------------------------+------------------------------------------------ The Cactus documentation http://einsteintoolkit.org/info/documentation/UsersGuide/UsersGuidech6.html… (scroll down to Compiling with Extra Packages) currently tells people to use the "extras" method for enabling access to external libraries such as HDF5, MPI etc. As I understand it, this method is deprecated in favour of the ExternalLibraries method, and both should not be used at the same time for the same library. The documentation should be updated to describe the ExternalLibraries method, and the old method description should be moved to an appendix with a clear warning that this is deprecated. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/219> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #206: Add --xml option to GetComponents
by Einstein Toolkit 19 Oct '11

19 Oct '11

#206: Add --xml option to GetComponents ---------------------------+------------------------------------------------ Reporter: eric9 | Owner: eric9 Type: enhancement | Status: new Priority: minor | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ GetComponents should support machine readable output using XML. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/206> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #395: Thorns providing interpolator routines should provide testcases for them
by Einstein Toolkit 18 Oct '11

18 Oct '11

#395: Thorns providing interpolator routines should provide testcases for them -------------------------+-------------------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: ET_2011_11 Component: Other | Version: Keywords: | -------------------------+-------------------------------------------------- Errors in the interpolator often show up in the output of other thorns, depending on those interpolating routines. Figuring out that this is caused by problem while interpolating can take quite a bit of time, which could be saved if the interpolating thorns would include testsuites themselves. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/395> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #369: Add command to update thorn list
by Einstein Toolkit 18 Oct '11

18 Oct '11

#369: Add command to update thorn list ---------------------------+------------------------------------------------ Reporter: eschnett | Owner: eric9 Type: defect | Status: new Priority: minor | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ When the thorn list changes, then I have to run GetComponents --update twice: first to update the thorn list, and then to actually check out these thorns. Currently, I have to update all thorns twice, which is a waste of time. Ideally, GetComponents would first update the thorn list, then update itself, then update everything else, and thus perform three passes over the thorn list, but not perform the work three times. Can we achieve this somehow? For example, we could mark the CRL script and the thorn lists with special tags, and GetComponents would then perform the work in three stages, restarting in between. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/369> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[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] #112: Python version of Simfactory should be made default before next ET release
by Einstein Toolkit 29 Sep '11

29 Sep '11

#112: Python version of Simfactory should be made default before next ET release ------------------------+--------------------------------------------------- Reporter: knarf | Owner: mthomas Type: task | Status: new Priority: critical | Milestone: ET_2011_06 Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/112> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #131: Cactus produces way too much output with SILENT!=no
by Einstein Toolkit 26 Sep '11

26 Sep '11

#131: Cactus produces way too much output with SILENT!=no -------------------------+-------------------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- I frequently find me scrolling through a lot of not necessary output from Cactus, including a lot of divider lines (___). I propose a mechanism to disable most of that output. There is currently one parameter which influences the amount of output from Cactus. If SILENT is set to 'no', Cactus provides way more output. All other values produce the usual output (including not setting it). I propose to use this existing variable to make Cactus less verbose if SILENT ist set to 'yes'. The default is 'undefined', so this would preserve the default Cactus behaviour. The attached patch attempts to do this: it suppresses divider lines, pre- and postprocessing infos if SILENT='yes'. I don't like that name though, as this is still not really silent, as you will still see one line per compiled file (ala COMPILING /home/frank.loeffler/mcrt/src/main/Banner.c), but I don't have a better idea right now and could live with it. The other option would be to introduce another variable (e.g. BRIEF), but then BRIEF and SILENT could contradict each other. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/131> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

← Newer
1
2
3
4
5
6
7
8
9
...
14
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac April 2011