Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #317: Unproper bevaviour of sim submit when changing the parfile
by Einstein Toolkit 09 Aug '11

09 Aug '11

#317: Unproper bevaviour of sim submit when changing the parfile ----------------------------------------------+----------------------------- Reporter: alexander.beck-ratzka@… | Owner: mthomas Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: ET_2010_11 Keywords: | ----------------------------------------------+----------------------------- If I make changes to the parfile of my simulation, and call then simfactory submit with the option --parfile=newpar, simfactory does not take this parfile. Instead of this, simfactory uses an old parfile from the old output-xxxx directory in my simualations direrctory. This usage of the old parfile might be wished. However, if this is the case, simfactory must complain if invoked with the option "parfile=...". But simfactory does not complain. In my case, the parfile has been modfied, but I am using the same name. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/317> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #370: New TRAC status "please commit"
by Einstein Toolkit 09 Aug '11

09 Aug '11

#370: New TRAC status "please commit" ----------------------------------+----------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- We seem to have tickets stuck in the "review" stage that effectively have been reviewed, but have not been applied yet. We may want to introduce a new status for that. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/370> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #486: New TRAC status "confirmed"
by Einstein Toolkit 09 Aug '11

09 Aug '11

#486: New TRAC status "confirmed" ----------------------------------+----------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- It would be useful to have a new TRAC status for tickets "confirmed" which would be used between "new" and "accepted" to indicate that the ticket is valid and the issue can be reproduced. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/486> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #123: Run a syntax checker in a pre-commit hook
by Einstein Toolkit 09 Aug '11

09 Aug '11

#123: Run a syntax checker in a pre-commit hook ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: mthomas Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- I am getting annoyed by the frequent syntax errors in SimFactory that used to be caught by Perl and are now not caught by Python. It would be ideal if syntax checking could be built into SimFactory, so that it executes automatically during startup if that isn't too slow. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/123> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #124: Implement a testing mechanism for simfactory
by Einstein Toolkit 09 Aug '11

09 Aug '11

#124: Implement a testing mechanism for simfactory -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: enhancement | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- Currently there is no easy way to check that a change to simfactory hasn't broken critical functionality. A system could be introduced to run through each command and check that it does the right thing. It won't be possible to check every single combination of possible options, but the most commonly used options should be tested. A first attempt could involve testing that the commands work locally on the current machine. This would involve submitting jobs and testing that they have the expected behaviour. On busy machines, this means that the tests could potentially take a long time to complete. Remote submission could be tested by running these tests from a central location (e.g. the developer's workstation or laptop). We could also include a python correctness checking step in these tests (e.g. using pychecker or pylint). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/124> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #485: Purge command should take multiple simulations as arguments
by Einstein Toolkit 08 Aug '11

08 Aug '11

#485: Purge command should take multiple simulations as arguments -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- The purge command currently only purges the first simulation given to it on the command line. It does not complain about any additional arguments, but neither does it attempt to purge them as simulations. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/485> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #483: Simulation descriptions
by Einstein Toolkit 02 Aug '11

02 Aug '11

#483: Simulation descriptions -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- I think it would be useful to attach short descriptive text to a simulation when it is created so that the user can go back to a simulation much later and see what it was for. At the moment, we only have the parameter file and the Formaline source. I'm thinking of something similar to VCS commit messages. For example: sim create-submit -m "Wave test - try better initial data" par/wavetest_3.par 32 1:00:00 If the user wants it, they could set an option to *require* a description for every simulation, in which case omitting one could give an editor prompt like in svn, git, etc, and the possibility of more than one line in the description becomes available. I would find this extremely convenient. The description could be given in the output of list- simulations, which might help when purging old simulations. The first line of the description could be expanded into cctk_run_title in the parameter file (I'm not sure what uses this parameter, but maybe it's useful). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/483> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #473: Add support for parameter file scripts
by Einstein Toolkit 30 Jul '11

30 Jul '11

#473: Add support for parameter file scripts -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- It is often useful to specify simulations by higher-level descriptions than Cactus parameter files. For example, when performing a convergence test, many parameters might change between simulations at different resolutions, and changing them all manually is tedious and error-prone. Similarly, it can be very useful to set parameters to values computed from simple expressions. For this reason, I usually use a "parameter file script" as my basic description of a simulation. A parameter file script is a file with a ".rpar" extension which, when executed, generates a file in the same place but with a ".par" extension. The resulting file should be a valid simfactory parameter file. The attached patch adds support in SimFactory for these scripts. Use a script in place of a parameter file when invoking SimFactory. When a simulation is run, the script will be executed and the resulting parameter file will be used by Cactus. Also attached is an example of a parameter file script written in Perl. It looks exactly like a Cactus parameter file apart from a header and footer, and $-replacements in the main body. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/473> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

Re: [ET Trac] [Einstein Toolkit] #31: Support HPSS archive system on Kraken
by Einstein Toolkit 30 Jul '11

30 Jul '11

#31: Support HPSS archive system on Kraken --------------------------+------------------------------------------------- Reporter: hinder | Owner: mthomas Type: enhancement | Status: closed Priority: minor | Milestone: Component: SimFactory | Version: Resolution: duplicate | Keywords: --------------------------+------------------------------------------------- Changes (by hinder): * status: new => closed * resolution: => duplicate Comment: Essentially a duplicate of #64. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/31#comment:1> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #475: apply "Carpet: Increase warning level for synchronising groups without storage" to Carpet/git
by Einstein Toolkit 19 Jul '11

19 Jul '11

#475: apply "Carpet: Increase warning level for synchronising groups without storage" to Carpet/git -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- I'd like to apply changeset: 3225:517449a54b9e user: Erik Schnetter <schnetter(a)cct.lsu.edu> date: Wed Dec 22 20:37:26 2010 -0600 summary: Carpet: Increase warning level for synchronising groups without storage to the git version of Carpet since these warnings pollute stdout in runs using the current release version of the ET thorns (would it be possible to apply this to the ET branch as well since it is also affected?). Unless this is vetoed I'll do so tomorrow. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/475> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac