Trac March 2013

trac@lists.einsteintoolkit.org

1 participants
161 discussions

[Einstein Toolkit] #1286: SimFactory should not run queued chained jobs if a previous job fails
by Einstein Toolkit 11 Mar '13

11 Mar '13

#1286: SimFactory should not run queued chained jobs if a previous job fails -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- When a simulation consists of multiple chained jobs, the failure of one job is likely to lead to the failure of subsequent jobs. Possible reasons for failure of a job include: 1. Running out of disk quota; 2. An error in the code; 3. A numerical problem; 4. A problem with the cluster Of all these, only the last could potentially be recovered from by simply running the next job in the chain, and in any case, if this is done immediately, it is likely to fail because the problem may not have resolved itself. As a result, to avoid wasting CPU hours on the remaining jobs in the chain, I think simfactory should hold or remove the subsequent chained jobs. Probably removing the jobs would be easier and simpler, and users can always run "submit" on them to restart them. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1286> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #624: Replace Cactus complex number implementation with C/C++ standard implementation
by Einstein Toolkit 08 Mar '13

08 Mar '13

#624: Replace Cactus complex number implementation with C/C++ standard implementation -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- Cactus offers CCTK_COMPLEX. This maps to the standard datatype in Fortran, but not in C or C++. It should map to the standard datatypes in C and C++ as well, so that the growing body of code written in C and C++ can reasonably make use of complex numbers. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/624> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1148: New thorn CactusTest/TestCrayPointers
by Einstein Toolkit 08 Mar '13

08 Mar '13

#1148: New thorn CactusTest/TestCrayPointers -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- I want to add a thorn CactusTest/TestCrayPointers that tests whether the Cray pointer syntax is accepted by the Fortran compiler. If so, please create the respective repository. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1148> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1284: Want stand-alone parameter parser
by Einstein Toolkit 08 Mar '13

08 Mar '13

#1284: Want stand-alone parameter parser -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- I would like to have an easy-to-use stand-alone parameter file parser. Presumably, this utility would be build as a Cactus utility in the flesh. I would take a parameter file as input, and would output parameter values as output (probably either in some ASCII format or in xml). It would also know about default values of parameters. This utility could answer the following questions: - which parameters are set in a parameter file? - what is the value of parameter X (which may have its default value)? - list all parameters that are set in the parameter file - list all parameters and their values Bonus points if it also knows about which thorns are active; this is non- trivial since some thorns are activated automatically. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1284> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

[Einstein Toolkit] #1277: GRHydro updates
by Einstein Toolkit 05 Mar '13

05 Mar '13

#1277: GRHydro updates -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: GRHydro | -----------------------------------+---------------------------------------- mostly Christian Reisswig's work on WENO and MP5 reconstruction in GRHydro. One trivial patch to remove a parfile for test output. Will commit on Wednesday unless objections are raised. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1277> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1281: SimFactory should expire its executable cache
by Einstein Toolkit 05 Mar '13

05 Mar '13

#1281: SimFactory should expire its executable cache ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- SimFactory stores executables in a CACHE directory in basedir. This directory seems to grow without limit. I just discovered that I had 73 GB of executables in there. SimFactory should probably delete anything older than a few weeks. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1281> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

Re: [ET Trac] [Einstein Toolkit] #30: Implement a "get" command
by Einstein Toolkit 05 Mar '13

05 Mar '13

#30: Implement a "get" command --------------------------+------------------------------------------------- Reporter: hinder | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment (by hinder): There is a tool called "h5check" (http://www.hdfgroup.org/products/hdf5_tools/h5check.html) which checks hdf5 files for consistency. It is probably too slow to run this on every transfer, but this would be the most robust solution. I have just encountered an HDF5 file which gives no errors with h5ls but fails an h5check. This file was being written when I ran out of quota. h5dump also fails, on all the datasets I have tried in the file, so I expect the file is not usable due to the header being corrupted. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/30#comment:8> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #1280: include warning in "No files created in test directory" test system output if no extensions were registered
by Einstein Toolkit 04 Mar '13

04 Mar '13

#1280: include warning in "No files created in test directory" test system output if no extensions were registered -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: test system | -------------------------+-------------------------------------------------- The test system finds out about which files to compile by merging all EXTENSIONS options from all thorns. If none are registered it just reports "no files were generated" since no files match the patterns. It might be useful to include a hint "Did you add file extensions in any test.ccl file?" in the test system output. This issue can arise if for example only some tests are transferred to a cluster or one inserts test cases into a source tree from a formaline tarball (to verify if that particular code would still pass the test). The tests then appear to all pass since 0 out of 0 files compare identical. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1280> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #1278: Handle inf and nan in parameter file parser
by Einstein Toolkit 03 Mar '13

03 Mar '13

#1278: Handle inf and nan in parameter file parser ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- The test case in CactusTest/TestPar fails because inf is not recognised as number. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1278> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #1262: simfactory doesn't know how to handle 'old' simulations
by Einstein Toolkit 02 Mar '13

02 Mar '13

#1262: simfactory doesn't know how to handle 'old' simulations ------------------------+--------------------------------------------------- Reporter: knarf | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: ET_2013_05 Component: SimFactory | Version: development version Keywords: | ------------------------+--------------------------------------------------- Trying to restart a simulation after an update of simfactory I get {{{ $ sim submit A3_oct --procs=256 Assigned restart id: 2 Traceback (most recent call last): File "/home/knarf/utils/simfactory/bin/../lib/sim.py", line 148, in <module> main() File "/home/knarf/utils/simfactory/bin/../lib/sim.py", line 144, in main CommandDispatch() File "/home/knarf/utils/simfactory/bin/../lib/sim.py", line 106, in CommandDispatch module.main() File "/home/knarf/utils/simfactory/lib/sim-manage.py", line 397, in main CommandDispatch() File "/home/knarf/utils/simfactory/lib/sim-manage.py", line 376, in CommandDispatch exec("command_%s()" % command) File "<string>", line 1, in <module> File "/home/knarf/utils/simfactory/lib/sim-manage.py", line 267, in command_submit restart.userSubmit(simulationName) File "/home/knarf/utils/simfactory/lib/simrestart.py", line 353, in userSubmit self.submit(submitScript) File "/home/knarf/utils/simfactory/lib/simrestart.py", line 590, in submit (nodes, ppn_used, procs, ppn, procs_requested, num_procs, num_threads, num_smt) = simlib.GetProcs(existingProperties) File "/home/knarf/utils/simfactory/lib/simlib.py", line 834, in GetProcs num_smt = existingProperties.numsmt AttributeError: SimProperties instance has no attribute 'numsmt' }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1262> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 11

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac March 2013