Trac January 2011

trac@lists.einsteintoolkit.org

1 participants
147 discussions

[Einstein Toolkit] #216: Thorns in ExternalLibraries should abort if the old "extras" mechanism has been selected
by Einstein Toolkit 02 Apr '11

02 Apr '11

#216: Thorns in ExternalLibraries should abort if the old "extras" mechanism has been selected -------------------------------+-------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: ExternalLibraries | -------------------------------+-------------------------------------------- The old way of specifying the location of external libraries, from Cactus/lib/make/extras, for example setting HDF5 = yes, is not compatible with the new mechanism where you must simply include the appropriate thorn from ExternalThorns. Using both can be confusing. I propose modifying the thorns in ExternalLibraries to check if the old mechanism has been selected, and to abort with an explanatory error message telling the user not to set, e.g. HDF5 = yes, if they are using ExternalLibraries/HDF5. I am attaching a completely untested patch for the HDF5 thorn which implements something like this. The code to determine if the user selected HDF5 = yes was taken from the extras directory. Comments? If this is appropriate, it can be adapted to all the thorns in ExternalLibraries. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/216> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #225: Patch: Create prototypes for all scheduled functions
by Einstein Toolkit 30 Mar '11

30 Mar '11

#225: Patch: Create prototypes for all scheduled functions -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- The attached patch makes the CST stage create prototypes for all scheduled functions into a new file cctk_ScheduleFunctions.h, which is included into cctk.h. This is done only for C (and C++) since Fortran prototypes cannot be declared at file scope. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/225> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #218: Documentation page should be better organised
by Einstein Toolkit 25 Mar '11

25 Mar '11

#218: Documentation page should be better organised ----------------------------+----------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus website | Version: Keywords: documentation | ----------------------------+----------------------------------------------- The documentation page of the Cactus website, http://cactuscode.org/documentation/ currently consists of a main body of text and a sidebar on the right. The main body contains links to the PDF versions of some of the documentation, and the sidebar contains links to other pieces of documentation, some but not all of which are in the main body as well. I propose that the sidebar is redundant, and not going to be noticed by most people as it is a sidebar, and should be removed. The documentation that is linked to from the sidebar should be linked to from the main part of the page, and the links should be to the HTML versions of the documentation. We could also provide links to the PDF versions as well, if anyone likes them. We could also be more descriptive about what each piece of documentation is. For example, indicating which document new users should start with (User's Guide). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/218> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #132: TRAC home page does not give a link for ET tickets
by Einstein Toolkit 21 Mar '11

21 Mar '11

#132: TRAC home page does not give a link for ET tickets ----------------------------------+----------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: trivial | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- The "TRAC home" page in the ET TRAC does not give a hyperlink for Einstein Toolkit tickets. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/132> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #154: docs.einsteintoolkit.org certificate is invalid due to hostname mismatch
by Einstein Toolkit 21 Mar '11

21 Mar '11

#154: docs.einsteintoolkit.org certificate is invalid due to hostname mismatch -------------------------------------+-------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- If I go to https://docs.einsteintoolkit.org I get a certificate warning from my browser because the certificate is for wiki.cct.lsu.edu, not docs.einsteintoolkit.org. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/154> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #122: Code documentation
by Einstein Toolkit 12 Mar '11

12 Mar '11

#122: Code documentation -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- In order to help new developers understand the code, the following would be useful: * Provide some sort of high-level overview of the internal components of simfactory. This could be in the form of a class diagram with annotations indicating what each class does, and its relationship to the other classes (inheritence/object membership etc). There must be tools for doing this for python and generating doxygen-type output. * Within the source code, provide at least a one-line comment for each function indicating what it does. * Ensure that the readmes etc in the repository are up-to-date, or at least remove any out-of-date information. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/122> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #200: IDAnalyticBH: Kerr initial data not smooth near z-axis
by Einstein Toolkit 08 Mar '11

08 Mar '11

#200: IDAnalyticBH: Kerr initial data not smooth near z-axis --------------------------------------+------------------------------------- Reporter: bernard.j.kelly@… | Type: defect Status: new | Priority: minor Milestone: ET_2010_11 | Component: Cactus Version: ET_2010_11 | Keywords: Kerr discontinuity --------------------------------------+------------------------------------- The Kerr initial data (in EinsteinInitialData/IDAnalyticBH/src/Kerr.c) has a defect along the z-axis (that is, the spin axis of the hole). The three- metric (for instance) is not smooth across this axis, leading to discontinuities in second spatial derivatives near there. This appears to be due to overly crude safety measures protecting from division by zero when calculating this data. Tweaking these measures for more self-consistency leads to much smoother behaviour. I'm attaching a simple patch that fixes the problem at least for metric_type = physical. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/200> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #172: CCL error message has no file name
by Einstein Toolkit 08 Mar '11

08 Mar '11

#172: CCL error message has no file name ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- I just received the following fatal error message from Cactus: Processing CCL files CST error 1: -> Error parsing optional block line '' Missing { at start of block. This error message does not tell me which thorn or file causes this. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/172> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #164: Support user directories for configuration files
by Einstein Toolkit 08 Mar '11

08 Mar '11

#164: Support user directories for configuration files -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- It would be nice to have a separate simfactory directory for all user customisations rather than mixing them in with the code. This way, one can update simfactory (or delete/recheckout) without having to extract all changes. Here is one possible solution: Allow the user to specify a "sf-config" directory (maybe there is a better name) in the defs.local.ini. Any configuration files, for example mdb entries, scriptfiles etc, should be searched for under sf-config first before looking in the standard location. One could then set sf-config = simfactory.user and put local machine definitions and scriptfiles and modifications to the standard ones which are never going to be committed. One could keep the same directory structure under simfactory.user as is in simfactory, or it might be better to just search for files in that directory, since all the files should have different names, and an extra hierarchy is just annoying. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/164> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #129: Warnings during syncing
by Einstein Toolkit 08 Mar '11

08 Mar '11

#129: Warnings during syncing ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: mthomas Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- When I synchronise with the Python SimFactory, I receive many warnings such as: cannot delete non-empty directory: simfactory/branches/PYSIM_2010/lib/modules cannot delete non-empty directory: simfactory/branches/PYSIM_2010/lib/modules cannot delete non-empty directory: simfactory/branches/PYSIM_2010/lib/archive cannot delete non-empty directory: simfactory/branches/PYSIM_2010/lib/archive cannot delete non-empty directory: simfactory/branches/PYSIM_2010/lib cannot delete non-empty directory: simfactory/branches/PYSIM_2010/lib cannot delete non-empty directory: simfactory/branches/PYSIM_2010 cannot delete non-empty directory: simfactory/branches/PYSIM_2010 cannot delete non-empty directory: simfactory/branches I know where they come from; however, they are nevertheless annoying. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/129> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2011