Trac November 2021

trac@lists.einsteintoolkit.org

1 participants
77 discussions

#2332: piraha does not allow variable expansion in ActiveThorns
by Steven R. Brandt 29 Nov '21

29 Nov '21

#2332: piraha does not allow variable expansion in ActiveThorns Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): No. Obviously, nothing should happen before the release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2332/piraha-does-not-a…

1 0

#2580: GetComponents assumes that default branch name is "master"
by Roland Haas 25 Nov '21

25 Nov '21

#2580: GetComponents assumes that default branch name is "master" Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: minor Component: GetComponents When using a stanza like this: ``` !TARGET = $ARR !TYPE = git !URL = git@github.com:rhaas/Foo.git !REPO_BRANCH = main !REPO_PATH= $2 !CHECKOUT = Foo/Foo ``` GetComponents fails with: ``` > bin/GetComponents --verbose --root . thornlists/grhydrox.th ----------------------------------------------------------------- Checking out module: Foo/Foo from repository: git@github.com:rhaas/Foo.git into: ./arrangements Executing: mkdir -p './repos' Executing: git clone git@github.com:rhaas/Foo.git './repos/Foo' Cloning into './repos/Foo'... Executing: git tag -l In: './repos/Foo' Executing: git checkout --track -b main origin/main In: './repos/Foo' fatal: A branch named 'main' already exists. Executing: mv './repos/Foo' './repos/Foo.branch.failed.1' Warning: Could not checkout Foo/Foo, unable to switch to branch main. Any existing symlinks to Foo/Foo will be broken ``` This can be made to work by leaving out the `REPO_BRANCH` option altogether, which is doable but not ideal. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2580/getcomponents-ass…

1 0

#2173: Test "Poisson equation" example
by Miguel Gracia 25 Nov '21

25 Nov '21

#2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2021_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Miguel Gracia): I updated the website and uploaded the results. I ran the example using a machine configured with _Intel$R$ Xeon$R$ Gold 6226R CPU @ 2.90GHz and 64Gb of ram._ @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} the link [https://bitbucket.org/einsteintoolkit/manifest/raw/ET\_2021\_11/einsteintoo… doesn’t exist so I left the ET\_2021\_05 one instead. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equa…

1 0

#2579: CT_MultiLevel implicitly requires CT_Analytic
by Roland Haas 23 Nov '21

23 Nov '21

#2579: CT_MultiLevel implicitly requires CT_Analytic Reporter: Gabriele Bozzola Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): assignee: Eloisa Bentivegna (was ) responsible: [] (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2579/ct_multilevel-imp…

1 0

#2579: CT_MultiLevel implicitly requires CT_Analytic
by Gabriele Bozzola 23 Nov '21

23 Nov '21

#2579: CT_MultiLevel implicitly requires CT_Analytic Reporter: Gabriele Bozzola Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn I am trying to solve a Poisson equation with `CT_MultiLevel` but without including `CT_Analytic` $which is advertised as an helper thorn$. I found that this cannot be done because `CT_MultiLevel` explicitly calls the restriction operations on grid functions defined in `CT_Analytic`. For example, in `CT_RelaxError.cc`: ``` CT_Restrict(CCTK_PASS_CTOC, "CT_MultiLevel::psi"); CT_Restrict(CCTK_PASS_CTOC, "CT_MultiLevel::coeffs"); CT_Restrict(CCTK_PASS_CTOC, "CT_Analytic::CT_testK"); CT_Restrict(CCTK_PASS_CTOC, "CT_Analytic::CT_testdxK"); CT_Restrict(CCTK_PASS_CTOC, "CT_Analytic::CT_testdyK"); CT_Restrict(CCTK_PASS_CTOC, "CT_Analytic::CT_testdzK"); CT_Restrict(CCTK_PASS_CTOC, "CT_Analytic::CT_testc1"); CT_Restrict(CCTK_PASS_CTOC, "CT_Analytic::CT_testc2"); ``` If you don’t have `CT_Analytic` as an active thorn, the run will abort. $Are these restrictions needed?$ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2579/ct_multilevel-imp…

1 0

#2578: Kranc, Cactus, and MPI linking issues
by Roland Haas 20 Nov '21

20 Nov '21

#2578: Kranc, Cactus, and MPI linking issues Reporter: Nicholas Hugh Olsen Status: new Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: Cactus Changes (by Roland Haas): assignee: Ian Hinder (was ) responsible: [] (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2578/kranc-cactus-and-…

1 0

#2578: Kranc, Cactus, and MPI linking issues
by Roland Haas 20 Nov '21

20 Nov '21

#2578: Kranc, Cactus, and MPI linking issues Reporter: Nicholas Hugh Olsen Status: new Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: Cactus Comment (by Roland Haas): If it’s Kranc specific then you may consider using Kranc’s mailng list and issue tracker as mentioned on the Kranc website: [http://kranccode.org/support.html](http://kranccode.org/support.html) Having said that, the Kranc authors tend to see ET tickets and may speak up. ``` ~$ ls /usr/lib/x86_64-linux-gnu/openmpi/lib/ libmca_common_monitoring.so libmpi_cxx.so libopen-rte.so libmca_common_ofi.so libmpi_java.so liboshmem.so libmca_common_ompio.so libmpi_mpifh.so ompi_monitoring_prof.so libmca_common_sm.so libmpi_usempi_ignore_tkr.so openmpi3 libmca_common_ucx.so libmpi_usempif08.so pkgconfig libmca_common_verbs.so libompitrace.so libmpi.so libopen-pal.so ``` ie there is a library `mpi_cxx` in addition to `mpi`. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2578/kranc-cactus-and-…

1 0

#2578: Kranc, Cactus, and MPI linking issues
by Nicholas Hugh Olsen 20 Nov '21

20 Nov '21

#2578: Kranc, Cactus, and MPI linking issues Reporter: Nicholas Hugh Olsen Status: new Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: Cactus After installing Kranc and seeing a successful install message, I went to build the ET with the standard ``` simfactory/bin/sim build -j2 --thornlist manifest/einsteintoolkit.th ``` like I always do when changing or adding a thorn but I received a slew of errors about undefined references with MPI$See log file for details$. All of this is done on a personal computer which I have attached my previously working configuration file$I think$ for, along with options and thorn lists just in case. The make.log was made with ``` VERBOSE=1 simfactory/bin/sim build -j1 2>&1 | tee make.log ``` as found on the support page without any changes made that might have messed with building. attachment: config-info (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: einsteintoolkit.th (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: make.log (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: OptionList (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2578/kranc-cactus-and-…

1 0

#2332: piraha does not allow variable expansion in ActiveThorns
by Roland Haas 19 Nov '21

19 Nov '21

#2332: piraha does not allow variable expansion in ActiveThorns Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} any progress on this? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2332/piraha-does-not-a…

1 0

#2575: online thorn documentation only lists thorns active in thorn list
by Roland Haas 19 Nov '21

19 Nov '21

#2575: online thorn documentation only lists thorns active in thorn list Reporter: Roland Haas Status: invalid Milestone: ET_2021_11 Version: development version Type: bug Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: invalid (was new) Comment (by Roland Haas): I was mistaken. All thorn documentation is build for all thorns in arrangements no matter whether they are in a thornlist or not. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2575/online-thorn-docu…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac November 2021