Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #73: Decouple submit and run scripts from configurations
by Einstein Toolkit 01 Nov '10

01 Nov '10

#73: Decouple submit and run scripts from configurations -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- Currently, SimFactory embeds the submit script and the run script in a configuration when the configuration is built. Neither of these are intrinsic properties of a configuration from a Cactus point of view. For example, they could be changed at job submission time. I think it would make a lot of sense for these to be decoupled from the configuration and chosen at job submission and job run time respectively. Here are some real-world situations where this would be useful: 1. At the AEI, we have workstations built into the same environment as our cluster, so that the same configuration/executable can run on both. At the moment, since the submission script (which would be different for a workstation and the cluster) is part of the configuration, you need to build two configurations even though it would be logical to just choose a different submit script at submit time. 2. When modifying a submit script or a run script, it is currently necessary to use "sim build". This can take a very long time (several minutes) on some clusters, even when there are no changes. There is no logical reason to recompile the configuration when only the submit or run script has changed. 3. It is very confusing that editing the submit script does not lead to it being used in subsequent submissions. I have very often forgotten that you need to do a new "build --submitscript..." command. 4. When SimFactory gains support for running testsuites, it will probably happen by having an alternate run script. In this case, it would be necessary to have a configuration specifically for testsuites, where the only difference is that the run script is a testsuite script rather than a parameter file script. I propose removing --submitscript and --runscript from the "sim build" command and moving them to "sim submit" and "sim run" respectively. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/73> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

Re: [ET Trac] [Einstein Toolkit] #61: make COMPONENTLIST_TARGET 'stable'
by Einstein Toolkit 29 Oct '10

29 Oct '10

1 0

Re: [ET Trac] [Einstein Toolkit] #1: Cactus doesn't support __unused__ for gcc
by Einstein Toolkit 27 Oct '10

27 Oct '10

#1: Cactus doesn't support __unused__ for gcc --------------------------+------------------------------------------------- Reporter: knarf | Owner: knarf Type: enhancement | Status: accepted Priority: minor | Milestone: Component: Cactus | Version: ET_2010_06 Resolution: | Keywords: --------------------------+------------------------------------------------- Comment (by knarf): I added a patch, tested on my laptop (gcc), a numrel station (icc) and pelican (ibm compiler). Please test and report. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1#comment:5> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #70: Cactus segfaults with incorrectly specified grid array sizes
by Einstein Toolkit 27 Oct '10

27 Oct '10

#70: Cactus segfaults with incorrectly specified grid array sizes --------------------+------------------------------------------------------- Reporter: knarf | Owner: knarf Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: ET_2010_06 Keywords: | --------------------+------------------------------------------------------- Cactus doesn't detect missing size arguments in multi-D grid array declarations, segfaulting in the process -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/70> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

Re: [ET Trac] [Einstein Toolkit] #20: trac.einsteintoolkit.org SSL certificate for svn.einsteintoolkit.org
by Einstein Toolkit 27 Oct '10

27 Oct '10

#20: trac.einsteintoolkit.org SSL certificate for svn.einsteintoolkit.org -----------------------------------+---------------------------------------- Reporter: hinder | Owner: mthomas Type: defect | Status: closed Priority: major | Milestone: Component: EinsteinToolkit trac | Version: Resolution: fixed | Keywords: -----------------------------------+---------------------------------------- Changes (by mthomas): * status: assigned => closed * resolution: => fixed Comment: this certificate is in place. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/20#comment:3> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

Re: [ET Trac] [Einstein Toolkit] #50: Mailing lists should "reply to all" by default
by Einstein Toolkit 26 Oct '10

26 Oct '10

#50: Mailing lists should "reply to all" by default -----------------------+---------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: closed Priority: major | Milestone: Component: Other | Version: Resolution: invalid | Keywords: -----------------------+---------------------------------------------------- Changes (by knarf): * status: new => closed * resolution: => invalid -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/50#comment:12> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #67: Output more information after testsuite run
by Einstein Toolkit 26 Oct '10

26 Oct '10

#67: Output more information after testsuite run -------------------------+-------------------------------------------------- Reporter: knarf | Owner: knarf Type: enhancement | Status: new Priority: major | Milestone: ET_2010_11 Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- It would be nice to output more information into the testsuite log file, e.g. time, user name and hostname. This would help when e.g. collecting testsuite results from a lot of people and machines. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/67> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

Re: [ET Trac] [Einstein Toolkit] #61: make COMPONENTLIST_TARGET 'stable'
by Einstein Toolkit 26 Oct '10

26 Oct '10

1 0

Re: [ET Trac] [Einstein Toolkit] #61: make COMPONENTLIST_TARGET 'stable'
by Einstein Toolkit 24 Oct '10

24 Oct '10

#61: make COMPONENTLIST_TARGET 'stable' ----------------------------+----------------------------------------------- Reporter: knarf | Owner: eric9 Type: enhancement | Status: accepted Priority: minor | Milestone: Component: GetComponents | Version: Resolution: | Keywords: ----------------------------+----------------------------------------------- Changes (by eric9): * status: new => accepted Comment: That would be fine with me. I guess that would also include moving the component list includes to 'stable'? It seems that there wouldn't be much point in writing the component list if it hadn't been modified, unless the original list was specified as a URL. I've never used the includes myself, would you consider them stable? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/61#comment:1> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

Re: [ET Trac] [Einstein Toolkit] #60: Checkpoint and recovery does not work
by Einstein Toolkit 21 Oct '10

21 Oct '10

#60: Checkpoint and recovery does not work -------------------------+-------------------------------------------------- Reporter: hinder | Owner: mthomas Type: defect | Status: closed Priority: blocker | Milestone: Component: SimFactory | Version: Resolution: fixed | Keywords: -------------------------+-------------------------------------------------- Changes (by mthomas): * status: new => closed * resolution: => fixed Comment: This has been fixed and verified working by Ian. Yipee!! -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/60#comment:1> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac