Trac May 2021

trac@lists.einsteintoolkit.org

1 participants
79 discussions

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

24 May '21

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2021_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by William Gabella): Running VisIt you can restore the attached session files. Here the 8 files u.file\_N.h5 with N=0…7 are the 3D “database” files of format CarpetHPDF5. However if you did not run with 8 MPI tasks $?$ or have a different file structure than this run, you will have to create the plot with VisIt manually. The following should get you pretty close: ``` singularity run docker://symerio/visit And is currently version 2.12.3 . You can restore the *.session file, or if your file structure is different do the following "by hand." o Start VisIT; o Sources Open file name like u.file.* as database and select manually CarpetHDF5 as file type. o Plots Add Pseudocolor. Load the data is called "LLAMAWAVETOY--u_lp_MP_rp_" . o On Pseudocolor add operator Slice. o Click Draw. The defaults are not good and note this is a movie and we show the time stamp is 5.04, Cycle 56. o Also click the "Swap foreground / background colors" icon on the Drawing window---icon with white upper triangle and black lower triangle. o Double click on the Pseudocolor and select the "orangehot" Color Table, and set the minimum to -0.5 and maximum to +0.5. ``` ‌ -- 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 24 May '21

24 May '21

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2021_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by William Gabella): The Original par file and the one with the Presync option seem to generate the same X-Y figure, files about the same size, etc. Runtimes are very similar. For our Vanderbilt ACCRE cluster with 8 MPI tasks and 8 CPUs runtime is about 5 minutes. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-…

1 0

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

21 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: bug Priority: major Component: Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

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

21 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: major Component: Changes (by Roland Haas): assignee: Steven R. Brandt (was ) responsible: [] (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2533: "ActiveThorns" not accepted in parameter file
by Erik Schnetter 21 May '21

21 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: major Component: Comment (by Erik Schnetter): … and the reason the parameter file was duplicated was that I wrote `IO::out_dir = $parfile` in an `*.rpar` file. ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2533: "ActiveThorns" not accepted in parameter file
by Erik Schnetter 21 May '21

21 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: major Component: Comment (by Erik Schnetter): I figured it out: The parameter file has two `ActiveThorns` declarations. The parser complains about the second one. Line numbers would be useful… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2533: "ActiveThorns" not accepted in parameter file
by Erik Schnetter 21 May '21

21 May '21

#2533: "ActiveThorns" not accepted in parameter file Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: major Component: I see an error with a parameter file that used to work fine. The error is ‌ ``` WARNING level 0 from host redshift.local process 0 in thorn cactus, file qc0.par:1: -> ERROR IN PARAMETER FILE:Parse Error Expected one of the following characters: ':', '(', '*', '/', '%', '+', '-', '<', '>', '&', '|', '!', '$', 'a', 'A' # run.memory: 1.0e9 # run.time: 7200.0 ActiveThorns = " ^ ``` The parameter file starts with ``` # run.me: # run.cores: 40 # run.memory: 1.0e9 # run.time: 7200.0 ActiveThorns = " ADMBase CarpetX Coordinates ErrorEstimator Formaline IOUtil ODESolvers TimerReport TmunuBase TwoPunctures Weyl Z4c " ``` I attach the full parameter file. attachment: qc0.par (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2533/activethorns-not-…

1 0

#2530: Thorn Vectors fails to compile using gcc 8.X on POWER9
by Roland Haas 20 May '21

20 May '21

#2530: Thorn Vectors fails to compile using gcc 8.X on POWER9 Reporter: Roland Haas Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/cactuscode/cactusutils/pull-requests/37/vectors-work-… To be applied after the release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2530/thorn-vectors-fai…

1 0

#2530: Thorn Vectors fails to compile using gcc 8.X on POWER9
by Roland Haas 20 May '21

20 May '21

#2530: Thorn Vectors fails to compile using gcc 8.X on POWER9 Reporter: Roland Haas Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2530/thorn-vectors-fai…

1 0

#2530: Thorn Vectors fails to compile using gcc 8.X on POWER9
by Roland Haas 20 May '21

20 May '21

#2530: Thorn Vectors fails to compile using gcc 8.X on POWER9 Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): It turns out it wants a cast to `vector double *` $see [http://openpowerfoundation.org/wp-content/uploads/resources/Intrinsics-Refe… which does list both `vec_st(vector double x, long long int, double * )` and `vec_st(vector double x, long long int, vector double * )` and apparently gcc 8 only supports the latter one$. So this: ```c++ #if 0 g++ -c -g3 -mcpu=power9 -mvsx -O1 -Wall $@ $0 exit #endif #include <altivec.h> void foo(vector double x, double &p, double &q, double &r, double &s) { const long long null = 0; *(vector double*)&p = x; vec_vsx_st(x, null, &q); vec_st(x, null, (vector double*)&r); } ``` and produces code: ```plaintext Disassembly of section .text: 0000000000000000 <_Z3fooDv2_dRdS0_S0_S0_>: #include <altivec.h> void foo(vector double x, double &p, double &q, double &r, double &s) { const long long null = 0; *(vector double*)&p = x; 0: 0d 00 45 f4 stxv vs34,0(r5) vec_vsx_st(x, null, &q); 4: 0d 00 46 f4 stxv vs34,0(r6) vec_st(x, null, (vector double*)&r); 8: ce 39 40 7c stvx v2,0,r7 } c: 20 00 80 4e blr 10: 00 00 00 00 .long 0x0 14: 00 09 00 00 .long 0x900 18: 00 00 00 00 .long 0x0 ``` where `stvx` is the regular altivec one and `stxv` is the ISA3 $POWER9$ instruction. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2530/thorn-vectors-fai…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac May 2021