November 2022 - Trac - lists.einsteintoolkit.org

#2668: GRHydro: work around Intel 19 compiler issue
by Roland Haas 24 Nov '22

24 Nov '22

#2668: GRHydro: work around Intel 19 compiler issue Reporter: Roland Haas Status: new Milestone: ET_2022_11 Version: ET_2021_05 Type: bug Priority: major Component: EinsteinToolkit thorn The intel 19 compiler and newer apparently miscompile GRhydro’s HLLE code when MHD is enabled. This results in either a SEGFAULT of con2prim failures. This has been in the ET tests since around 2021 \(it shows up in the ET\_2021\_05\_v0 release tests\). Pull request [https://bitbucket.org/einsteintoolkit/einsteinevolve/pull-requests/18](http… provides a workaround. With it the affected tests pass, see eg qb an supermuc on [http://einsteintoolkit.org/testsuite\_results/index.php](http://einsteintoo… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2668/grhydro-work-arou…

1 0

#2667: Test periodic_weight of CarpetReduce produces non numeric output in grid_coordinates.asc
by Roland Haas 24 Nov '22

24 Nov '22

#2667: Test periodic_weight of CarpetReduce produces non numeric output in grid_coordinates.asc Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn `.asc` files are registered with the test system \(by the ASCII output thorn\) as output files to be compared and must be columnar ASCII data files. However `periodic_weight` enables output for `grid_coordinates.asc` which do not adhere to that format and instead contain descriptions of the boxes: ```text # grid coordinates # format: map reflevel region mglevel bounding-box iteration 0 maps 1 0 mglevels 1 0 0 reflevels 1 0 0 0 regions 1 0 0 0 0 ([-2.6,-2.6,-2.6]:[2.4,2.4,2.4]:[0.2,0.2,0.2]/[0,0,0]:[0,0,0]/[26,26,26]/17576) ``` which causes the test system to complain: ```text Argument "([-2.6,-2.6,-2.6]:[2.4,2.4,2.4]:[0.2,0.2,0.2]/[0,0,0]:[0..." isn't numeric in subtraction (-) at lib/sbin/RunTestUtils.pl line 1920, <INNEW> line 8. ``` the testsuite should be changed to not output this file or give a different name that does not match one of the registered extensions. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2667/test-periodic_wei…

1 0

#2666: Testsuite system does not recognize "Cactus" thorn
by Zach Etienne 24 Nov '22

24 Nov '22

#2666: Testsuite system does not recognize "Cactus" thorn Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Zach Etienne): @{5bae587b96242d2e2b6110a4} \(thorn author\) Could you please take a look at this? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2666/testsuite-system-…

1 0

#2666: Testsuite system does not recognize "Cactus" thorn
by Roland Haas 24 Nov '22

24 Nov '22

#2666: Testsuite system does not recognize "Cactus" thorn Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn The `ActiveThorns` directive in parameter files accepts a “secret” thorn “Cactus” that corresponds to the flesh and its `Cactus::` parameters. The testsuite system is however not aware of this and will not run tests with that pseudo-thorn activated and claims that there are missing thorns. Eg test `NRPyEllipticET_test_conformally_flat_BBH` on [https://einsteintoolkit.github.io/tests/](https://einsteintoolkit.github.io… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2666/testsuite-system-…

1 0

#2172: Test "Binary black hole GW150914" example
by Roland Haas 23 Nov '22

23 Nov '22

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: resolved Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2665: Two open pull requests in EinsteinInitialData
by Roland Haas 23 Nov '22

23 Nov '22

#2665: Two open pull requests in EinsteinInitialData Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: trivial Component: Comment (by Roland Haas): To the ticket, please. Although, given that it is a simple string search, my prior comment will trigger it. Best to put individual links to the pull requests in the ticket as well \(in case there are more than 2 open pull requests in EinsteinInitiial\). Ideally also link back to the ticket from the pull requests so that one knows which ticket they refer to and which ticket can be closed once the pull requests are closed. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2665/two-open-pull-req…

1 0

#2665: Two open pull requests in EinsteinInitialData
by Gabriele Bozzola 23 Nov '22

23 Nov '22

#2665: Two open pull requests in EinsteinInitialData Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: trivial Component: Comment (by Gabriele Bozzola): To the ticket \(ie, here\) or the PR? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2665/two-open-pull-req…

1 0

#2172: Test "Binary black hole GW150914" example
by Roland Haas 23 Nov '22

23 Nov '22

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): Before each release, check that http://einsteintoolkit.org/gallery/bbh/index.html still works and produces correct output. Then upload the results file to [https://bitbucket.org/einsteintoolkit/www/downloads/](https://bitbucket.org… Then update the last run time on [http://einsteintoolkit.org/gallery/bbh/index.html](http://einsteintoolkit.o… and update the plots. Prefix commit messages with “bbh: “ in the first line \(see eg the output of `git log --format=oneline gallery/bbh/index.html`\). **Keyword:** None -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2172: Test "Binary black hole GW150914" example
by Roland Haas 23 Nov '22

23 Nov '22

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was ) assignee: Allen Wen (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2172: Test "Binary black hole GW150914" example
by Roland Haas 23 Nov '22

23 Nov '22

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): Before each release, check that http://einsteintoolkit.org/gallery/bbh/index.html still works and produces correct output. Then upload the results file to [https://bitbucket.org/einsteintoolkit/www/downloads/](https://bitbucket.org… Then update the last run time on [http://einsteintoolkit.org/gallery/bbh/index.html](http://einsteintoolkit.o… and update the plots. Prefix commit messages with “bbh: “ in the first line \(see eg the output of \`git log --format=oneline gallery/bbh/index.html \`\). **Keyword:** None -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2665: Two open pull requests in EinsteinInitialData
by Roland Haas 22 Nov '22

22 Nov '22

#2665: Two open pull requests in EinsteinInitialData Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: trivial Component: Comment (by Roland Haas): Please add “Please review” to the associated tickets. This is what the “tickets ready for review” search in each ET call looks for. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2665/two-open-pull-req…

1 0

#2665: Two open pull requests in EinsteinInitialData
by Gabriele Bozzola 22 Nov '22

22 Nov '22

#2665: Two open pull requests in EinsteinInitialData Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: trivial Component: There are two open pull requests in EinsteinInitialData. One is trivial \(English typos, I just opened it\), the other concerns a possible typo in TOVSolver. I didn’t check that one. [https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests](ht… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2665/two-open-pull-req…

1 0

#1713: Avoid build-time warning
by Roland Haas 18 Nov '22

18 Nov '22

#1713: Avoid build-time warning Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): responsible: [] (was ) assignee: Roland Haas (was ) I see this warning when building. I assume this should instead be a run-time warning or error? /Users/eschnett/Cbeta/arrangements/EinsteinEvolve/GRHydro_InitData/src/GRHydro_PoloidalMagFieldM.F90:110:2: warning: #warning "This algorithm does only work on Cartesian grids!!" [-Wcpp] #warning "This algorithm does only work on Cartesian grids!!" ^ **Keyword:** -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1713/avoid-build-time-…

1 0

#1713: Avoid build-time warning
by Roland Haas 18 Nov '22

18 Nov '22

#1713: Avoid build-time warning Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): I have a beautiful patch for this but the comment field is too small to write it down. I’ll make a pull request after the release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1713/avoid-build-time-…

1 0

#2646: Replace error/warning messages by CCTK_ERROR/CCTK_WARN in IllinoisGRMHD
by Roland Haas 18 Nov '22

18 Nov '22

#2646: Replace error/warning messages by CCTK_ERROR/CCTK_WARN in IllinoisGRMHD Reporter: Leonardo Werneck Status: new Milestone: Version: Type: task Priority: minor Component: Comment (by Roland Haas): Can this be resolved? Please use the the big blue “resolve” button in that case. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2646/replace-error-war…

1 0

#1579: GRHydro does not build on Blue Gene/Q
by Roland Haas 18 Nov '22

18 Nov '22

#1579: GRHydro does not build on Blue Gene/Q Reporter: Erik Schnetter Status: wontfix Milestone: Version: development version Type: bug Priority: minor Component: Other Changes (by Roland Haas): status: wontfix (was new) Some of the C++ source files in GRHydro do not build on a Blue Gene/Q with IBM's compiler. The problem is that the compiler takes a very long time (>8h) even without (sic!) optimization. "The usual" playing with compiler options or changes to the source files had no effect. I consider this to be a bug in the compiler. A work-around may be to switch to Clang as C++ compiler. **Keyword:** Comment (by Roland Haas): There's no more BG/Qs around. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1579/grhydro-does-not-…

1 0

#2615: Riemann release not compiling with intel 2021.6.0
by Roland Haas 18 Nov '22

18 Nov '22

#2615: Riemann release not compiling with intel 2021.6.0 Reporter: Wolfgang Kastaun Status: new Milestone: Version: ET_2022_05 Type: bug Priority: minor Component: Comment (by Roland Haas): Note that if you set `FPP` you _must_ also set `FPPFLAGS` \(but you can leave _both_ out and get usually sane defaults\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2615/riemann-release-n…

1 0

#2615: Riemann release not compiling with intel 2021.6.0
by Roland Haas 18 Nov '22

18 Nov '22

#2615: Riemann release not compiling with intel 2021.6.0 Reporter: Wolfgang Kastaun Status: new Milestone: Version: ET_2022_05 Type: bug Priority: minor Component: Comment (by Roland Haas): @{557058:55837d30-c210-4b67-899f-972675258158} any news on this? If not I am tempted to close due to lack of activity after 2022-12-18. My best guess is some line length issue or incorrectly set up FPPFLAGS. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2615/riemann-release-n…

1 0

#2664: Publication webpage is outdated, sphinxcontrib-citations may help keeping it updated automatically
by Roland Haas 17 Nov '22

17 Nov '22

#2664: Publication webpage is outdated, sphinxcontrib-citations may help keeping it updated automatically Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: trivial Component: EinsteinToolkit website Comment (by Roland Haas): We already have a bibtex2html converter for use in the toolkit \(on the citations.html page\), so that is not a problem. We had some discussion on this during today’s call. Details can be found in the minutes. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2664/publication-webpa…

1 0

#2174: Test "Multi Patch Scalar Wave Equation" example
by Kalyanaraman, Hrishikesh 16 Nov '22

16 Nov '22

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Kalyanaraman, Hrishikesh): I’ve updated the tar file and made the changes to the www repo -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-…

1 0

#2664: Publication webpage is outdated, sphinxcontrib-citations may help keeping it updated automatically
by Gabriele Bozzola 15 Nov '22

15 Nov '22

#2664: Publication webpage is outdated, sphinxcontrib-citations may help keeping it updated automatically Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: trivial Component: EinsteinToolkit website The publication webpage hasn’t been updated in ~ 14 years judging from the last entry \([https://www.einsteintoolkit.org/publications.html](https://www.einsteintoolkit.org/publications.html)\). A while ago, I developed an extension for Sphinx to solve a similar problem. [https://github.com/Sbozzolo/sphinxcontrib-citations](https://github.com/Sbo… takes a list of ADS keys and returns a list of papers that cite the given keys. This Sphinx extension can be easily adjusted to automatically populate the publications webpage. The package does not necessarily need Sphinx: one could simply take the core.py and use it. A BibTeX to HTML parser would be required in that case, but there are many available online. Probably, the easiest solution is to include in the www repo both the core.py \(which fundamentally depends only on urlib3\) and a bib2html parser. It requires an ADS API key \(which can be obtained for free\) and I don’t know how this would be handled. For example, assuming one evaluates `core.py`, sets the ADS API, and `bibcodes = ["2021zndo...4884780E"]`, the Python function `write_citing_bibtex(citations_ads_token, bibcodes, "/tmp/et.bib") `will automatically fetch and clean all the entries and produce a valid bibtex file. I don’t know how the other scripts in the www repo are automatically run, but this could be the same. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2664/publication-webpa…

1 0

#2663: add an notice about minimum Intel / GCC version required to configure output
by Roland Haas 15 Nov '22

15 Nov '22

#2663: add an notice about minimum Intel / GCC version required to configure output Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: major Component: Comment (by Roland Haas): 2017 claims gcc 6 support here: [https://www.intel.com/content/www/us/en/developer/articles/release-notes/in… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-abo…

1 0

#2663: add an notice about minimum Intel / GCC version required to configure output
by Roland Haas 15 Nov '22

15 Nov '22

#2663: add an notice about minimum Intel / GCC version required to configure output Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: major Component: Cactus requires full C\+\+ 11 support, which for the Intel compiler suite requires a new enough Intel C\+\+ compiler _as well as_ a new enough STL \(from g\+\+\) to work. While configure tests for features it does not give a hint as to what compiler version is required. In particular for the Intel compiler whose default setup often uses an old system installed g\+\+ STL this can be annoying. It would thus be good if configure, at least when detecting an Intel compiler, could output a minimum known good combination of Intel and g\+\+ compiler to work. This may be Intel 2017 \+ gcc 6. Gcc 6 is a known requirement and stated in one of the release notes. Intel 2017 may be the first intel compiler to list compatibility with gcc 6 include files. Known to not work are versions Intel 2015 \([https://stackoverflow.com/questions/29371301/intel-c-compiler-what-is-highest-gcc-version-compatibility](https://stackoverflow.com/questions/29371301/intel-c-compiler-what-is-highest-gcc-version-compatibility)\) and earlier. The current minimum icpc version in simfactory option lists is intel 2017 or intel 2016 \(on Caltech’s wheeler cluster which has not been tested for a while\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-abo…

1 0

#2485: include complex and real scalar evolution code from Canuda in ET
by Roland Haas 10 Nov '22

10 Nov '22

#2485: include complex and real scalar evolution code from Canuda in ET Reporter: Roland Haas Status: open Milestone: Version: Type: task Priority: major Component: Comment (by Roland Haas): I just notice that none of the Scalar\* thorns have a documentation.tex file. Those files are required for inclusion and them not being there should have precluded acceptance \(and their lack was mentioned in the vote but then not acted on, sorry\). The release date has been pushed by a week, so if you can please do provide some documentation files as soon as possible. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

#2662: Try to get email from ~/.gitconfig
by Roland Haas 09 Nov '22

09 Nov '22

#2662: Try to get email from ~/.gitconfig Reporter: Steven R. Brandt Status: new Milestone: Version: Type: enhancement Priority: trivial Component: SimFactory Changes (by Roland Haas): responsible: [] (was ) assignee: Steven R. Brandt (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2662/try-to-get-email-…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac November 2022