May 2022 - Trac - lists.einsteintoolkit.org

#2198: simfactory's user level run command does not record jobid in a segment's properties.ini file
by Roland Haas 27 May '22

27 May '22

#2198: simfactory's user level run command does not record jobid in a segment's properties.ini file Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: minor Component: SimFactory Changes (by Roland Haas): The \(user level\) run command does not record a jobid in a segment's properties.ini file which means one cannot eg restart from a checkpoint since simfactory complains about an unset jobid: ``` simfactory/bin/sim create-run test1 --parfile par/tov_ETK_2018_lisbon.par --procs 1 --walltime 0:5:0 & grep jobid ~/simulations/test1/output-0000/SIMFACTORY/properties.ini ``` shows the issue \(but not producing any output\). And the error obtained when trying to restart is along the lines of > Simulation name: binarybh9 Error: job id is negative Aborting Simfactory This was reported by Qingwen Wang in http://lists.einsteintoolkit.org/pipermail/users/2018-September/006524.html A workaround is to not use run as a user but always submit or to use the cleanup command after which simfactory is fine with there not being a job id. **Keyword:** None -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2198/simfactorys-user-…

1 0

#2174: Test "Multi Patch Scalar Wave Equation" example
by William Gabella 26 May '22

26 May '22

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2022_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by William Gabella): I have successfully run the example last weekend. And generated a new, correct looking graphic with the Singularity VisIT \(see above\). However, code freeze is today and will re-run with the final code in the next days. If successful will then need to update the gallery example web page with the new graphic and tarball and date-time stamps. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-…

1 0

#2174: Test "Multi Patch Scalar Wave Equation" example
by William Gabella 26 May '22

26 May '22

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2022_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by William Gabella): status: open (was resolved) Comment (by William Gabella): Updating gallery example for May 2022 ET release. Also changed the Milestone to ET_2022_05. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-…

1 0

#2174: Test "Multi Patch Scalar Wave Equation" example
by William Gabella 26 May '22

26 May '22

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: resolved Milestone: ET_2022_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by William Gabella): milestone: ET_2022_05 (was ET_2021_11) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-…

1 0

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it
by Roland Haas 20 May '22

20 May '22

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it Reporter: Status: new Milestone: Version: development version Type: bug Priority: minor Component: Comment (by Roland Haas): Though if this is slated to be removed in favor of Boost anyway, I may just sit it out. Though boost of course is also not part of the ET and not particularly version stable :slight_smile: -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2610/reprimand-thorn-r…

1 0

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it
by Roland Haas 20 May '22

20 May '22

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it Reporter: Status: new Milestone: Version: development version Type: bug Priority: minor Component: Comment (by Roland Haas): There’s no real good way. There is a “version” attached with an ExternalLibrary but that does not give any guarantee about the version of the library actually used \(in particular when using a system provided one and not building from source\). I have a bad way of testing for GSL in: [https://github.com/rhaas80/RePrimAnd/commit/a8f5a6664739b676e1fb44208cae5a7… but is is kludgy since I basically do a mini autoconf. Meson of course contains the correct version dependency but for the ET build I am not using Meson \(too many dependencies on Python\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2610/reprimand-thorn-r…

1 0

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it
by Wolfgang Kastaun 20 May '22

20 May '22

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it Reporter: Status: new Milestone: Version: development version Type: bug Priority: minor Component: Comment (by Wolfgang Kastaun): What would be the cactus way of requiring a minimum GSL version from the externallibraries GSL thorn? Note: The GSL dependence will probably be removed in the foreseeable future in favor of BOOST. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2610/reprimand-thorn-r…

1 0

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it
by Roland Haas 19 May '22

19 May '22

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it Reporter: Status: new Milestone: Version: development version Type: bug Priority: minor Component: Changes (by Roland Haas): priority: minor (was major) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2610/reprimand-thorn-r…

1 0

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it
by Anonymous 19 May '22

19 May '22

#2610: RePrimAnd thorn requires GSL 2.0 but does not test for it Reporter: Status: new Milestone: Version: development version Type: bug Priority: major Component: The RePrimAnd thorn currently does not document its need for GSL 2.0 in a way Cactus can check. The meson build file contains the check there is no check in configuration.ccl or build.sh. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2610/reprimand-thorn-r…

1 0

#2601: Add four more parameters for carpet
by Roland Haas 10 May '22

10 May '22

#2601: Add four more parameters for carpet Reporter: Liwei Ji Status: new Milestone: Version: development version Type: enhancement Priority: major Component: Carpet Comment (by Roland Haas): There are some suggestions on the “How to review a patch” page of the wiki \(somewhat hidden, since it is listed in the “maintainers” section of the front page only\): [https://docs.einsteintoolkit.org/et-docs/How\_to\_Review\_a\_Patch](https:/… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…

1 0

#2601: Add four more parameters for carpet
by Liwei Ji 10 May '22

10 May '22

#2601: Add four more parameters for carpet Reporter: Liwei Ji Status: new Milestone: Version: development version Type: enhancement Priority: major Component: Carpet Comment (by Liwei Ji): Hi Roland, I’m not sure how to review. Could you help me with more details? Thanks -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…

1 0

#2601: Add four more parameters for carpet
by Roland Haas 10 May '22

10 May '22

#2601: Add four more parameters for carpet Reporter: Liwei Ji Status: new Milestone: Version: development version Type: enhancement Priority: major Component: Carpet Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…

1 0

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString
by Roland Haas 10 May '22

10 May '22

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): To be reviewed after the ET\_2022\_05 release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2609/trigger-thorn-doe…

1 0

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString
by Roland Haas 10 May '22

10 May '22

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/cactuscode/cactusutils/pull-requests/39/trigger-handl… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2609/trigger-thorn-doe…

1 0

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString
by Roland Haas 10 May '22

10 May '22

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Working on this. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2609/trigger-thorn-doe…

1 0

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString
by Roland Haas 10 May '22

10 May '22

#2609: Trigger thorn does not properly check return value from CCTK_TraverseString Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn On the mailing list in thread [http://lists.einsteintoolkit.org/pipermail/users/2022-May/008511.html](http… an issue with the Trigger thorn has been deduced to be due to incomplete return code checks in Trigger. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2609/trigger-thorn-doe…

1 0

#2397: incorporate envssetup into Cactus option list
by Roland Haas 04 May '22

04 May '22

#2397: incorporate envssetup into Cactus option list Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: major Component: Cactus Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} points out that this envsetup will also have to be propagated to submit and run scripts. Likely requiring simfactory to parse the cfg file for envsetup. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2397/incorporate-envss…

1 0

#2409: update simfactory files to use compilers new enough to avoid C++ math workarounds
by Roland Haas 02 May '22

02 May '22

#2409: update simfactory files to use compilers new enough to avoid C++ math workarounds Reporter: Roland Haas Status: resolved Milestone: Version: Type: enhancement Priority: major Component: SimFactory Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2409/update-simfactory…

1 0

#2409: update simfactory files to use compilers new enough to avoid C++ math workarounds
by Roland Haas 02 May '22

02 May '22

#2409: update simfactory files to use compilers new enough to avoid C++ math workarounds Reporter: Roland Haas Status: open Milestone: Version: Type: enhancement Priority: major Component: SimFactory Comment (by Roland Haas): Done as of as git hash [5739bd2b](https://bitbucket.org/simfactory/simfactory2/commits/5739bd2bd7a6… "smic: update intel to 19.0 and gcc to new version" of [simfactory2](https://bitbucket.org/simfactory/simfactory2) and will be in `2022_05`. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2409/update-simfactory…

1 0

#2608: list of substitutions variables @FOO@ is not consistent among commands or options
by Roland Haas 02 May '22

02 May '22

#2608: list of substitutions variables @FOO@ is not consistent among commands or options Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: minor Component: Simfactory does not use a consistent list of replacement variables for all substitutions. There are differences between runscripts and submitscripts, some of which are justified, eg the job id is not yet available by the time the submit script is created. Some are not justified, for example the machine ini files replace `@USER@` in the `basedir` setting but not in `optionlist` settings. Ideally these should be handled consistently using a single replacement function. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2608/list-of-substitut…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac May 2022