Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #643: UserGuide: Document current TRAC system instead of GNATS for problem reports
by Einstein Toolkit 08 Nov '11

08 Nov '11

#643: UserGuide: Document current TRAC system instead of GNATS for problem reports ---------------------------+------------------------------------------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: documentation | ---------------------------+------------------------------------------------ The Cactus documentation (a shared appendix between the User Guide and the Reference Manual) currently talks about using the GNATS problem reporting system. We now use TRAC. The attached patch updates the documentation to describe the new system. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/643> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #637: output puncture velocity in puncturetracker
by Einstein Toolkit 04 Nov '11

04 Nov '11

#637: output puncture velocity in puncturetracker -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: PunctureTracker | -----------------------------------+---------------------------------------- the attached patch allows the puncture velocities to be output (simply moves the result of an interpolation into grid functions). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/637> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #661: have puncture tracker output the puncture velocities
by Einstein Toolkit 04 Nov '11

04 Nov '11

#661: have puncture tracker output the puncture velocities -------------------+-------------------------------------------------------- Reporter: rhaas | Type: enhancement Status: new | Priority: minor Milestone: | Component: EinsteinToolkit thorn Version: | Keywords: PunctureTracker -------------------+-------------------------------------------------------- the attached patch outputs the puncture velocity (ie the shift) at the location of the puncture. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/661> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #658: ET component homepages
by Einstein Toolkit 03 Nov '11

03 Nov '11

#658: ET component homepages -------------------------------------+-------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- It would be good to have a "home page" on the web for each important component in the ET. Components such as Cactus, Carpet, and Kranc have home pages already. We could host pages for the major thorns, linking to the documentation and the SVN repo. This is somewhat already accomplished by having the ET thorn guide available, but links to sections of this change when it is regenerated, and it is not very user-friendly. These pages could contain the information from the thorn README files (which should be kept up-to-date), and this could be the starting point. We could write the README files in a markdown language such as ReST, which is already human-readable in a text editor, and then use an automated tool such as Sphinx or rst2html to convert these to HTML for the web. Information on a homepage could include: * Author list and copyright; * Licence; * Brief description of what the thorn does; * Permanent link to the documentation (thorn-doc); * Instructions for checking out the thorn (svn); * Link to open tickets relating to this component (those with the component name in the keywords, for those that don't have a TRAC component assigned). Components such as McLachlan, TwoPunctures, WeylScal4 and GRHydro would be some good initial candidates for having pages describing them. It would be good if there was a web presence for ET thorns, so that Google searches might find them. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/658> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #656: GRHYdro::Bcons has wrong tensorparity in interface.ccl
by Einstein Toolkit 02 Nov '11

02 Nov '11

#656: GRHYdro::Bcons has wrong tensorparity in interface.ccl -------------------+-------------------------------------------------------- Reporter: rhaas | Type: defect Status: new | Priority: major Milestone: | Component: Other Version: | Keywords: GRHydro -------------------+-------------------------------------------------------- the B field is a pseudovector so tensorparity should be -1 (as it already is for HydroBase). Will commit fix later today. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/656> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #655: Broken links to documentation on cactuscode.org
by Einstein Toolkit 01 Nov '11

01 Nov '11

#655: Broken links to documentation on cactuscode.org ----------------------------+----------------------------------------------- Reporter: bentivegna | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus website | Version: Keywords: | ----------------------------+----------------------------------------------- On http://cactuscode.org/documentation/, the links to the PDF version of the user's guide and the reference manual point to http://cactuscode.org/documentation/usersguide/UsersGuide.pdf and http://cactuscode.org/documentation/referencemanual/ReferenceManual.pdf, whilst they should point to http://cactuscode.org/documentation/UsersGuide.pdf and http://cactuscode.org/documentation/ReferenceManual.pdf respectively. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/655> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #653: Create a CACTUS_EXE_DIR variable
by Einstein Toolkit 01 Nov '11

01 Nov '11

#653: Create a CACTUS_EXE_DIR variable -------------------------+-------------------------------------------------- Reporter: bmundim | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- CACTUS_CONFIGS_DIR allows us to have the configs directory outside the Cactus tree (please see ticket #652). I suggest to create a similar variable for the executables, a CACTUS_EXE_DIR variable. It would work in the direction of separating source code from generated executables, objects, libraries, etc... -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/653> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #544: Enable optimisation in Fortran array index calculations
by Einstein Toolkit 27 Oct '11

27 Oct '11

#544: Enable optimisation in Fortran array index calculations -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- In Fortran, Cactus passes all grid functions as arguments to routines, and the size of the grid functions are declared in DECLARE_CCTK_ARGUMENTS. In these declarations, Cactus assumes that the size of each grid variable group can be different, and the compiler thus does not see that all grid functions have (locally) the same array shape. The compiler can thus not simplify array index calculations. This is probably only relevant in short loops accessing grid functions from multiple groups (GRHydro?). The attached patch passes three additional integer arguments (cctk_lsh[123]) which contain the shape of grid functions, and uses these to declare grid functions. This patch is quite old, but was never applied. It comes from a time when g77 didn't support declaring array shapes via an integer array (since this is not allowed in Fortran 77). If this is now possible, one could use the array cctk_lsh instead of passing three extra integer arguments. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/544> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #235: Improve performance of Fortran index calculations
by Einstein Toolkit 27 Oct '11

27 Oct '11

#235: Improve performance of Fortran index calculations -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- In Fortran, Cactus currently declares grid functions e.g. as (this is the expansion of DECLARE_CCTK_ARGUMENTS) REAL*8 gxx (X0metric,X1metric,X2metric) where X0metric etc. are integers passed into the routine. Each grid function group has its own, independent size. This has two disadvantages: 1. The compiler does not know that all grid functions have the same size (namely cctk_lsh), and thus has to perform array index calculations separately for each group 2. The argument list is longer than neded The enclosed patch declares grid functions via cctk_lsh. Grid arrays are still declared independently. This reduces the code size of e.g. GRHydro/GRHydro_Tmunu.F90 from 6836 to 6241 bytes on my system. I have not attempted to measure a performance difference. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/235> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #458: Improve bboxset efficiency (e.g. for regridding)
by Einstein Toolkit 27 Oct '11

27 Oct '11

#458: Improve bboxset efficiency (e.g. for regridding) -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- The attached patch modifies the algorithm used to insert a new bbox into an existing bboxset. It reduces the computational complexity of this operation from O(n^2) to O(n), where n is the number of elements in the bboxset. This has the potential to speed up regridding significantly. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/458> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac