Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2590: Uninitialized variable in Perl code
by Steven R. Brandt 26 Jan '22

26 Jan '22

#2590: Uninitialized variable in Perl code Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): Sorry, it _IS_ a syntax error. I would not expect PrintInterfaceStatistics to run in that case. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2590/uninitialized-var…

1 0

#2590: Uninitialized variable in Perl code
by Steven R. Brandt 26 Jan '22

26 Jan '22

#2590: Uninitialized variable in Perl code Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): Hmm. That looks like a syntax error to me. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2590/uninitialized-var…

1 0

#2591: New `CENTERING` syntax not documented
by Steven R. Brandt 26 Jan '22

26 Jan '22

#2591: New `CENTERING` syntax not documented Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: major Component: Cactus Comment (by Steven R. Brandt): OMG, I can’t believe Roland didn’t notice :stuck_out_tongue: -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2591/new-centering-syn…

1 0

#2591: New `CENTERING` syntax not documented
by Erik Schnetter 26 Jan '22

26 Jan '22

#2591: New `CENTERING` syntax not documented Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: major Component: Cactus The new syntax `CENTERING...` to define vertex/cell centred grid functions is not documented. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2591/new-centering-syn…

1 0

#2590: Uninitialized variable in Perl code
by Erik Schnetter 26 Jan '22

26 Jan '22

#2590: Uninitialized variable in Perl code Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: minor Component: Cactus I receive this error from the CST stage: ``` CST error in /Users/eschnett/Cactus/arrangements/CarpetX/CarpetX/interface.ccl (at 129) -> SYNTAX ERROR Use of uninitialized value in concatenation (.) or string at /Users/eschnett/Cactus/repos/flesh/lib/sbin/interface_parser.pl line 985. ``` for this code: ``` CCTK_REAL regrid_error TYPE=gf CENTERING={ccc TAGS='index={1 1 1}' { regrid_error } "Regridding condition" ``` The code is wrong $it’s missing a closing brace$, but the error message should be better. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2590/uninitialized-var…

1 0

#178: New command that runs non-interactively
by Roland Haas 25 Jan '22

25 Jan '22

#178: New command that runs non-interactively Reporter: Erik Schnetter Status: resolved Milestone: Version: Type: enhancement Priority: minor Component: SimFactory Changes (by Roland Haas): status: resolved (was new) SimFactory should offer a command that is halfway in between "submit" and run". This command should start a simulation immediately, but should run it in the background while redirecting stdout and stderr to the usual locations in the simulation's output directory. Technically, this command would be on the same level as "submit", while "run" would reside at a lower level. For example, "run" would expect an active simulation (and would not activate a simulation), while this new command would activate the simulation. **Keyword:** -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/178/new-command-that-r…

1 0

#178: New command that runs non-interactively
by Roland Haas 25 Jan '22

25 Jan '22

#178: New command that runs non-interactively Reporter: Erik Schnetter Status: new Milestone: Version: Type: enhancement Priority: minor Component: SimFactory Comment (by Roland Haas): As of git hash [868ec6aa](https://bitbucket.org/simfactory/simfactory2/commits/868ec6aad881… "simrestart: duplicate log data to file in sim run" of [simfactory2](https://bitbucket.org/simfactory/simfactory2) one can use: ```shell nohup sim run --parfile foo.par &>/dev/null & ``` or one’s favorite equivalent for this since `run` duplicates output to both `stdout` and the simfactory `foo.out` log file. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/178/new-command-that-r…

1 0

#1301: Formaline should store the thornlist
by Roland Haas 25 Jan '22

25 Jan '22

#1301: Formaline should store the thornlist Reporter: Ian Hinder Status: wontfix Milestone: Version: Type: enhancement Priority: minor Component: Cactus Changes (by Roland Haas): status: wontfix (was resolved) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1301/formaline-should-…

1 0

#1301: Formaline should store the thornlist
by Roland Haas 25 Jan '22

25 Jan '22

#1301: Formaline should store the thornlist Reporter: Ian Hinder Status: resolved Milestone: Version: Type: enhancement Priority: minor Component: Cactus Changes (by Roland Haas): status: resolved (was new) Formaline should store the thornlist used to build the configuration. This will make it easier to reconstruct a working Cactus tree from the Formaline output. **Keyword:** Comment (by Roland Haas): Since thornlist is included in the tarball and the list of compiled thorns is also in formaline-jar.txt which contains both thorn names eg: ``` thorns/zlib="active" ``` as well as arrangements: ``` thorn_arrangements/zlib="ExternalLibraries" ``` all information is present. Eg a: ``` awk -v FS='[/="]' '/^thorn_arrangements/{print $4"/"$2}' formaline-jar.txt ``` gets the thornlist required to compile (but not to checkout which Cactus does not know anything about). That latter one is only stored on the tarball. I think there is direct need to add extra code for all conceivable cases of Formaline use if that leads to extra output files and extra code to maintain. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1301/formaline-should-…

1 0

#1680: GetComponents does not prompt for a password for a private SVN repository
by Roland Haas 25 Jan '22

25 Jan '22

#1680: GetComponents does not prompt for a password for a private SVN repository Reporter: Bruno Mundim Status: duplicate Milestone: Version: development version Type: bug Priority: minor Component: GetComponents Changes (by Roland Haas): status: duplicate (was open) Comment (by Roland Haas): Duplicate of #68. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1680/getcomponents-doe…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac