Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2535: ET_2020_11 build issue
by Edwin 31 May '21

31 May '21

#2535: ET_2020_11 build issue Reporter: Edwin Status: new Milestone: Version: development version Type: bug Priority: blocker Component: Comment (by Edwin): Thank you very much! I can access [FFTW Home Page](http://fftw.org/) but still can not install all thorns correctly. When I run \( in subsystem of win10 and Ubuntu 20.04 LTS\) ./GetComponents --parallel [https://bitbucket.org/einsteintoolkit/manifest/raw/ET\_2021\_05/einsteintoo… \(The newest introductions on [Download \(einsteintoolkit.org\)](http://einsteintoolkit.org/download.html)\) in order to download again but get responses Unable to process NRPyPN Unable to process ExternalLibraries/libjpeg Unable to process ExternalLibraries/zlib Unable to process ExternalLibraries/FFTW3 Unable to process ExternalLibraries/pthreads Unable to process ExternalLibraries/BLAS Unable to process KrancNumericalTools/GenericFD Unable to process ExternalLibraries/hwloc Unable to process ExternalLibraries/LAPACK Unable to process ExternalLibraries/OpenSSL Unable to process ExternalLibraries/MPI Unable to process ExternalLibraries/PETSc Unable to process ExternalLibraries/GSL Unable to process EinsteinExact/doc Unable to process ExternalLibraries/OpenCL Unable to process ExternalLibraries/HDF5 Summary of Warnings: Could not checkout module NRPyPN fatal: unable to access '[https://github.com/zachetienne/nrpytutorial.git/':](https://github.com/zachetienne/nrpytutorial.git/':) GnuTLS recv error \(-110\): The TLS connection was non-properly terminated. Could not checkout module ExternalLibraries/libjpeg svn: E170013: Unable to connect to a repository at URL '[https://github.com/EinsteinToolkit/ExternalLibraries-libjpeg.git/branches/E…'](https://github.com/EinsteinToolkit/ExternalLibraries-libjpeg.git/branches/ET_2021_05') svn: E000110: Error running context: Connection timed out … ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2535/et_2020_11-build-…

1 0

#2535: ET_2020_11 build issue
by Zach Etienne 31 May '21

31 May '21

#2535: ET_2020_11 build issue Reporter: Edwin Status: new Milestone: Version: development version Type: bug Priority: blocker Component: Comment (by Zach Etienne): Hi Edwin It seems that when you followed the Download instructions there were errors in downloading certain thorns \(the errors you shared indicate they do not exist\). I know this can happen if you are behind a firewall. Please follow the download instructions again, but first make sure you have the ability to clone the needed repositories. One thing you could first check is if you can access [fftw.org](http://fftw.org) . ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2535/et_2020_11-build-…

1 0

#2535: ET_2020_11 build issue
by Edwin 31 May '21

31 May '21

#2535: ET_2020_11 build issue Reporter: Edwin Status: new Milestone: Version: development version Type: bug Priority: blocker Component: I run ./simfactory/bin/sim -j2 --thornlist ../einsteintoolkit.th in orde to build the toolkit but get responses There were 57 errors during execution of the CST These must be corrected before compilation can proceed Warnings were generated during execution of the CST CST error in /home/zhaodingyi/Cactus/lib/sbin/CST \(at 322\) -> Missing thorn ExternalLibraries/FFTW3 CST error in /home/zhaodingyi/Cactus/lib/sbin/CST \(at 322\) -> Missing thorn ExternalLibraries/GSL … /home/zhaodingyi/Cactus/lib/make/make.configuration:212: recipe for target '/home/zhaodingyi/Cactus/configs/sim/config-data/make.thornlist' failed make\[1\]: \*\*\* \[/home/zhaodingyi/Cactus/configs/sim/config-data/make.thornlist\] Error 1 Makefile:260: recipe for target 'sim' failed make: \*\*\* \[sim\] Error 2 It seems I have missed some thorns but I do not know how to install them correctly！ ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2535/et_2020_11-build-…

1 0

#2533: "ActiveThorns" not accepted in parameter file
by Steven R. Brandt 28 May '21

28 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: major Component: Comment (by Steven R. Brandt): [https://bitbucket.org/cactuscode/cactus/pull-requests/124/fixing-2533](http… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2469: None of the thorns in WVUThorns_Diagnostics have documentation
by Zach Etienne 28 May '21

28 May '21

#2469: None of the thorns in WVUThorns_Diagnostics have documentation Reporter: Roland Haas Status: new Milestone: ET_2021_05 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Zach Etienne): I just merged two PRs from Leo Werneck, who wrote documentation for each of the two VolumeIntegrals\* thorns. Documentation for * particle\_tracerET * Seed\_Magnetic\_Fields\_BNS * smallbPoynET is still planned. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2469/none-of-the-thorn…

1 0

#2533: "ActiveThorns" not accepted in parameter file
by Roland Haas 28 May '21

28 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: major Component: Comment (by Roland Haas): My take would be that to me: ``` IO::out_dir = ``` would be an error but that: ``` IO::out_dir = "" ``` is valid \(so not the RHS is emtpy but the value\). The tricky bit would seem to classify: ``` foo = bar = 12 ``` as an error on foo, while allowing: ``` foo = bar baz = 12 ``` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2533: "ActiveThorns" not accepted in parameter file
by Steven R. Brandt 28 May '21

28 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: major Component: Comment (by Steven R. Brandt): The thing that confused the parser was the empty assignment to out\_dir. It was looking for the value of output\_dir, and found ActiveThorns. Should we disallow empty RHS? At the moment, I’m working to fix the line number issue. ``` IO::out_dir = ``` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2534: Evolution of grid arrays with Mol no longer works
by Yosef Zlochower 27 May '21

27 May '21

#2534: Evolution of grid arrays with Mol no longer works Reporter: Status: new Milestone: Version: development version Type: bug Priority: major Component: Carpet Comment (by Yosef Zlochower): The following patch seems to “fix” the problem. ``` diff --git a/Carpet/src/Poison.cc b/Carpet/src/Poison.cc index 12fc3d3..39a989a 100644 --- a/Carpet/src/Poison.cc +++ b/Carpet/src/Poison.cc @@ -131,12 +131,16 @@ void PoisonGroup(cGH const *const cctkGH, int const group, END_LOCAL_MAP_LOOP; // mark as invalid - for (int var = 0; var < nvar; ++var) { - int const map0 = 0; - ggf *const ff = arrdata.AT(group).AT(map0).data.AT(var); - assert(ff); - for (int tl = min_tl; tl <= max_tl; ++tl) { - ff->set_valid(mglevel, reflevel, tl, CCTK_VALID_NOWHERE); + // Exclude CCTK_ARRAY from this + if (CCTK_GroupTypeI(group) != CCTK_ARRAY) + { + for (int var = 0; var < nvar; ++var) { + int const map0 = 0; + ggf *const ff = arrdata.AT(group).AT(map0).data.AT(var); + assert(ff); + for (int tl = min_tl; tl <= max_tl; ++tl) { + ff->set_valid(mglevel, reflevel, tl, CCTK_VALID_NOWHERE); + } } } ``` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2534/evolution-of-grid…

1 0

#2413: Include "POWER" code to extrapolate waveforms to scri+ into ET
by Maria 26 May '21

26 May '21

#2413: Include "POWER" code to extrapolate waveforms to scri+ into ET Reporter: Roland Haas Status: open Milestone: Version: Type: task Priority: major Component: EinsteinToolkit thorn Comment (by Maria): Roland, ‌ In your documentation, you write: “Please consult the output of power.py --help for details on the supported command line options.“ Running ./power.py --help, as you instructed, gives me a long list of options, and I am overwhelmed. I read that I need to “Use 'QuasiLocalMeasures' or ‘QLM' to deduce fromquasilocalmeasures-qlm\_scalars..asc \(the default\)”. I don’t have quasilocalmeasures-qlm\_scalars..asc as output. Is there another way to recover those parameters without redoing the runs? An example on how to use the script with BNS data will be much appreciated. If not, a short instruction on how do I find the steering parameters will be useful. Or, if this is possible only within Python, a short example of what functions should be called to obtain the necessary parameters. ‌ Oh, one more thing: please include in the documentation the essential lines that must be included in the par file, in order to be able to use POWER. There is this: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ WeylScal4::fdOrder = 8 WeylScal4::calc\_scalars = "psis" WeylScal4::calc\_invariants = "always" Multipole::nradii = 7 Multipole::radius\[0\] = 100 Multipole::radius\[1\] = 115 Multipole::radius\[2\] = 136 Multipole::radius\[3\] = 167 Multipole::radius\[4\] = 214 Multipole::radius\[5\] = 300 Multipole::radius\[6\] = 500 Multipole::ntheta = 120 Multipole::nphi = 240 Multipole::variables = "WeylScal4::Psi4r\{sw=-2 cmplx='WeylScal4::Psi4i' name='psi4'\}" Multipole::out\_every = 512 Multipole::l\_max = 4 [~~#8~~](https://bitbucket.org/einsteintoolkit/tickets/issues/8/unable-to-do-remote-submission-without) Multipole::output\_hdf5 = yes Multipole::output\_ascii = no \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ ‌ Besides, shall one add quasilocalmeasures-qlm\_scalars..asc? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2413/include-power-cod…

1 0

#2534: Evolution of grid arrays with Mol no longer works
by Yosef Zlochower 26 May '21

26 May '21

#2534: Evolution of grid arrays with Mol no longer works Reporter: Status: new Milestone: Version: development version Type: bug Priority: major Component: Carpet Comment (by Yosef Zlochower): The attached thorn simply registers and array with for evolution with MoL. The thorn is not intended to actually evolve a real array. The issue also only shows up if the number of refinement levels is larger than 1 ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2534/evolution-of-grid…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac