Trac February 2013

trac@lists.einsteintoolkit.org

1 participants
177 discussions

[Einstein Toolkit] #959: Move pthreads to ExternalLibraries
by Einstein Toolkit 13 Aug '15

13 Aug '15

#959: Move pthreads to ExternalLibraries -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- We should move pthreads support to ExternalLibraries (or to the flesh). I have asked CCT to create the respective repository. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/959> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 14

[Einstein Toolkit] #816: include SphericalHarmonicReconASCII from incoming in PITTNULLCode
by Einstein Toolkit 04 Aug '15

04 Aug '15

#816: include SphericalHarmonicReconASCII from incoming in PITTNULLCode -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Christian Reisswig provided a copy of SphericalHarmonicReconASCII and alternative thorn that reads in CCE boundary data (similar SphericalHarmonicRecon) but supporting a wider variety of input file formats (HDF5 among them, irrespective of the name). Used by SpEC and Llama. There are no docs or test cases as of now. Test data would be welcome (SpEC, Llama or Cactus provided, I don't think it makes a difference). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/816> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 17

[Einstein Toolkit] #1252: Thorn configuration scripts should not be run if there are missing thorns
by Einstein Toolkit 09 Jun '15

09 Jun '15

#1252: Thorn configuration scripts should not be run if there are missing thorns -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- If there are thorns present in the thornlist which are not present in the source tree, Cactus currently displays the corresponding error message, and then runs the rest of the CST including thorn configuration scripts. Since these can build large external libraries (e.g. LORENE), it can be a long time before the user notices that the build has failed. I would prefer if Cactus aborted before running the CST scripts. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1252> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #796: Support https for einsteintoolkit.org
by Einstein Toolkit 22 May '15

22 May '15

#796: Support https for einsteintoolkit.org -------------------------------------+-------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- To show our commitment to privacy and IT safety, we should enable https support for our web site. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/796> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1211: CarpetIOScalar should write file info for restart files
by Einstein Toolkit 22 Apr '15

22 Apr '15

#1211: CarpetIOScalar should write file info for restart files --------------------+------------------------------------------------------- Reporter: knarf | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | --------------------+------------------------------------------------------- Currently Carpet doesn't write file info for files created by a restarted simulation (from a checkpoint, writing into a new file). It should instead write the header if it created the file - which means it need to check whether it appends or created the file new. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1211> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1204: carpet bug
by Einstein Toolkit 22 Mar '15

22 Mar '15

#1204: carpet bug -------------------------------------+-------------------------------------- Reporter: abdik@… | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | -------------------------------------+-------------------------------------- The latest version of carpet seems to contain a bug that affects AMR+multipatch runs. My stderr and stdout and par file are attached. Found by Roland and Ernazar. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1204> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #997: problem in appending output after recovery
by Einstein Toolkit 22 Mar '15

22 Mar '15

#997: problem in appending output after recovery ----------------------------------------+----------------------------------- Reporter: corvino.giovanni@… | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | ----------------------------------------+----------------------------------- I have a problem in appending output files from Carpet. I used to produce 3d HDF5 output of grid variables and write the output in the same directory also after recovery from checkpoint. The new output was automatically appended to the existing one. Now I am producing h5 output also on 2D slices but in this case the output is overwritten so I lost the data for all but the last recovery. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/997> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #428: Forbid configuration names ending in -reconfig
by Einstein Toolkit 12 Jan '15

12 Jan '15

#428: Forbid configuration names ending in -reconfig ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- I accidentally created a Cactus configuration with a name like "sim- reconfig". This confuses Cactus, because the command "make sim-reconfig" can then mean either to build the "sim-reconfig" configuration, or to reconfigure the "sim" configuration. Cactus should catch and forbid these cases. This is probably most cleanly handled by using a script instead of a Makefile to interpret the user commands. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/428> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 12

[Einstein Toolkit] #1039: Web-based documentation should be automatically updated
by Einstein Toolkit 09 Dec '14

09 Dec '14

#1039: Web-based documentation should be automatically updated -------------------------------------+-------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: Documentation | -------------------------------------+-------------------------------------- We have documentation for Cactus and the ET on their respective websites. This should be updated automatically when the source is changed, so it is never out of date. There should be documentation for the current release as well as the current development version. There is one technical problem standing in the way of this. The system should be automated, and it needs to have commit rights to a specific directory in the SVN repository hosting the files. SVN accounts for CCT machines tend to be the same as CCT login accounts, so we don't want to store the username and password. I think the best solution is to create an SVN account specifically for the documentation build system which is not tied to a CCT login account. This account would be given commit access to just the directories necessary. The "checkout, build doc, commit" script should be kept in version control somewhere, and a machine should be chosen on which to run it. It could be run regularly, or just in response to commits. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1039> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #791: Output timer tree as XML
by Einstein Toolkit 08 Dec '14

08 Dec '14

#791: Output timer tree as XML -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- The attached patch to Carpet adds a parameter (off by default) which outputs the timer tree from each process to an XML file in the output directory at the end of the run. The output looks like this: {{{ <timer name = "main"> 7.7702 <timer name = "CallFunction"> 0.000241 <timer name = "thorns"> 0.000233 <timer name = "CaKernel_FreeDevMem"> 0.000221 <timer name = "PostCall"> 2e-06 </timer> <timer name = "PreCall"> 1e-06 </timer> </timer> </timer> </timer> <timer name = "CarpetStartup"> 0.00982 <timer name = "AllocateGridHierarchy"> 5e-06 </timer> }}} An alternative schema would be to have the name and timer value as subelements; i.e. {{{ <timer> <name>main</name> <value>7.7702</value> <children> <timer> <name>CallFunction</name> <value<0.000241</name> ... </timer> }}} The <children> tag might not be necessary, but might make it easier to parse. Having one file per process is not ideal; we would like to add reductions across processes to give min, max, average, standard deviation etc, also for the standard output display. OK to commit as a work-in-progress? We can change the schema later if it turns out to be easier to deal with. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/791> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 15

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac February 2013