Users May 2020

users@lists.einsteintoolkit.org

16 participants
24 discussions

New Einstein Toolkit Release (Turing)
by Roland Haas 03 Jun '20

03 Jun '20

Release Announcement Click here to read the announcement in HTML (with hyperlinks): https://einsteintoolkit.org/about/releases/ET_2020_05_announcement.html We are pleased to announce the twentieth release (code name "Turing") of the Einstein Toolkit, an open, community developed software infrastructure for relativistic astrophysics. The highlights of this release are: Cactus now supports tracking of data dependencies at runtime using schedule annotations. These can be used to check correctness of a schedule and also to automate data synchronizations between MPI ranks. Two new thorns have been added: * Baikal, a spacetime evolution code using NRPy+ for code generation * BaikalVacuum, a version of Baikal optimized for vacuum only simulations In addition, bug fixes accumulated since the previous release in October 2019 have been included. The Einstein Toolkit is a collection of software components and tools for simulating and analyzing general relativistic astrophysical systems that builds on numerous software efforts in the numerical relativity community including the spacetime evolution codes Baikal, lean_public, and McLachlan, analysis codes to compute horizon characteristics and gravitational waves, the Carpet AMR infrastructure, and the relativistic magneto-hydrodynamics codes GRHydro and IllinoisGRMHD. The Einstein Toolkit also contains a 1D self-force code. For parts of the toolkit, the Cactus Framework is used as the underlying computational infrastructure providing large-scale parallelization, general computational components, and a model for collaborative, portable code development. The Einstein Toolkit uses a distributed software model and its different modules are developed, distributed, and supported either by the core team of Einstein Toolkit Maintainers, or by individual groups. Where modules are provided by external groups, the Einstein Toolkit Maintainers provide quality control for modules for inclusion in the toolkit and help coordinate support. The Einstein Toolkit Maintainers currently involve staff and faculty from five different institutions, and host weekly meetings that are open for anyone to join in. Guiding principles for the design and implementation of the toolkit include: open, community-driven software development; well thought-out and stable interfaces; separation of physics software from computational science infrastructure; provision of complete working production code; training and education for a new generation of researchers. For more information about using or contributing to the Einstein Toolkit, or to join the Einstein Toolkit Consortium, please visit our web pages at http://einsteintoolkit.org, or contact the users mailing list users(a)einsteintoolkit.org. The Einstein Toolkit is primarily supported by NSF 1550551/1550461/1550436/1550514 (Einstein Toolkit Community Integration and Data Exploration). The Einstein Toolkit contains about 300 regression test cases. On a large portion of the tested machines, almost all of these tests pass, using both MPI and OpenMP parallelization. The changes between this and the previous release include: Larger changes since last release * Automatic synchronization and correctness checking: For some time, Cactus has supported READS/WRITES declarations in the schedule. These declarations named grid functions and/or groups as well as the relevant region a function was reading and writing, e.g. "interior," "boundary," etc. In this release, we make it (1) possible to check the correctness of these declarations (both compile time and run time checks are implemented); and (2) we make it possible to automatically synchronize ghost zones and apply boundary conditions to grid functions when that is needed. By default, this functionality is off but can be enabled by setting the Cactus parameter "presync_mode." Please see the documentation for details. * Baikal - new thorn that solves Einstein's equations, using the BSSN 3+1 formalism, in Cartesian coordinates. + extensively documented in pedagogical Jupyter notebooks + borrows extensively from lean_public - makes extensive use of the Python and SymPy-based NRPy+ code generation infrastructure available on GitHub, which aims to provide a completely free, open-source means for converting expressions in Einstein-like tensorial notation into highly optimized C-code kernels. - implements most common (highly robust) options for numerical relativity GRHD and GRMHD simulations + moving-puncture gauge conditions (1+log lapse and Gamma-driving shift condition) enabled by default. + options of 2nd or 4th order finite-difference kernels, Kreiss-Oliger dissipation enabled by default via tunable parameter - validated to agree with ML_BSSN in case of BNS evolutions * BaikalVacuum - version of Baikal optimized for vacuum (e.g., black hole and binary black hole) spacetimes * ExternalLibraries - the HDF5 tarball included in the EinsteinToolkit has been updated to 1.10.5, which changed the hid_t types to 64bit integers - the hwloc tarball included in the EinsteinToolkit has been updated to 2.0.1, which is incompatible with version 1.X * new features and enhancements - thorn Vectors now supports vectorization on IBM POWER9 cpus used in Summit - Carpet will allocate less memory if `enable_no_storage = yes`, which is useful when testing parameter files using `cactus_sim -P parfile.par` - CarpetLib speedup during regridding by removing expensive debug checks - temperature finding for tabulated EOS in EOS_Omni become more robust for situations of almost degenerate internal energy functions - the MakeThornList utility was updated to support more use cases * important bugfixes - Carpet fix bug when using "along-z", "along-dir" and "manual" processor decomposition - AHFinderDirect has been fixed to avoid a long-standing issue where the number of metric timelevels needed to be set to 3 to avoid errors during recovery from a checkpoint - the parameter file for the Kasner example in Class. Quantum Grav. 29 115001 (2012) was corrected to produce the results shown in the paper - bug was found in Multipole's default "midpoint" integration scheme, lowering its integration order, the released version changes the default method as a workaround and a full fix will be backported after the release * Cactus - Cactus documentation now contains information on the git revisions used to produce documentation - a long standing bug in CCTK_TraverseString when traversing "all" groups was fixed - the testsuite mechanism provides options to run only some tests - the testsuite mechanism provides options to postprocess data before comparison, for example to compare HDF5 files - the testsuite mechanism will run all tests that request less than the available number of processes, running more tests - Cactus option lists can now refer to environment variables using ${ENV-VAR-NAME} - cross compiling support in Cactus has been improved - Cactus now supports building on Raspberry Pi out of the box * more thorn documentation available online * machine definition files were updated Deprecated functionality The following features are being marked as deprecated in this release and will be removed in the next release * the non-Piraha parser in CST, available only by modifying the CST source code, will be removed since it fails to correctly parse READS / WRITES clauses * READS / WRITES statements that refer to non-existing variables will cause compile time errors and no longer be ignored at runtime even if `presync_mode = off` * the fourth order accurate second derivative operators in SummationByParts will default to use the "Minimal Bandwidth" version, as already is the case for the other second derivatives Contributors This release includes contributions by Eloisa Bentivegna, Erik Schnetter, Federico Cipolletta, Frank Loeffler, Giuseppe Ficarra, Ian Hinder, Jascha Schewtschenko, Ken Sible, Lorenzo Sala, Miguel Zilhao, Philipp Moesta, Roland Haas, Samuel Cupp, Steven R. Brandt, and Zachariah Etienne. How to upgrade from Mayer (ET_2019_10) To upgrade from the previous release, use GetComponents with the new thornlist to check out the new version. See the Download page (http://einsteintoolkit.org/download.html) on the Einstein Toolkit website for download instructions. The SelfForce-1D code uses a single git repository, thus using `git pull ; git checkout ET_2020_05` will update the code. Machine notes Supported (tested) machines include: * Default Debian, Ubuntu, Fedora, CentOS 7, Mint, OpenSUSE and MacOS Mojave (MacPorts) installations * Bluewaters * Comet * Cori * Queen Bee 2 * Stampede 2 * Mike / Shelob * SuperMUC-NG * Wheeler Note for individual machines: * TACC machines: defs.local.ini needs to have `sourcebasedir = $WORK` and `basedir = $SCRATCH/simulations` configured for this machine. You need to determine $WORK and $SCRATCH by logging in to the machine. * SuperMUC-NG: defs.local.ini needs to have `sourcebasedir = $HOME` and `basedir = $SCRATCH/simulations` configured for this machine. You need to determine $HOME and $SCRATCH by logging in to the machine. * compiling with the gcc compiler version 9.3.0 or later can be very slow. A workaround is to replace -O2 in the option list by the individual optimization flags reported by `gcc -O2 --help=optimizers` All repositories participating in this release carry a branch ET_2020_05 marking this release. These release branches will be updated if severe errors are found. The "Turing" Release Team on behalf of the Einstein Toolkit Consortium (2020-05-31) * Roland Haas * Brockton Brendal * William E. Gabella * Beyhan Karakas * Atul Kedia * Shawn G. Rosofsky * Steven R. Brandt * Alois Peter Schaffarczyk * Helvi Witek May, 2020

2 2

meeting minutes for 2020-05-28
by Roland Haas 28 May '20

28 May '20

Present: Roland, Steve, Peter S., Maria, Atul, Beyhan, Peter D., Chris, Federico, Liu, Bill, Yosef, Zach, Zhao Zhichao code freeze * no more changes until after release * all release branches (ET_2020_05) are in place and can be used for testing * some cleanup required (docs, Kranc) open tickets for release: * release branch of SelfForce-1D referred to non-existing file, turned out that the branch was incorrectly created https://bitbucket.org/einsteintoolkit/tickets/issues/2399 * Roland asks that tickets that are not preventing the release be downgraded to "minor" gallery testing: * Bill and Beyhan will upload there results and update the website * Shawn will upload and update once done, is in the process of running at this point * Peter and Atul, are working on BBH gallery example POWER code: * waveform extrapolator (psi4 -> strain, finite r to scrI+) * available free and open source, not yet in ET * https://git.ncsa.illinois.edu/elihu/Gravitational_Waveform_Extractor * there is a summer project at NCSA this year to build on it and turn it into a tool that takes and ET simulation and produces a LIGO style waveform HDF5 file including metadata ILGRMHD: * minimum resolution for neutron star in BNS merger simulation * depends on setup, in Cartesian at least 75points across the diameter, better 120 points for trustworthy results * use Trigger thorn to increase resolution once a BH is found next release: * will solicit contributions in June next minute takers: Bill, Maria next call chairs: Zach, Peter Yours, Roland -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu .

1 0

Mixed binaries setup with TwoPunctures
by Andrea Endrizzi 28 May '20

28 May '20

Hi, I'm trying to set up a mixed binary via TwoPunctures and the TOVSolver. I found a "test" directory in the TwPuncture thorn with several parfiles and no documentation.... I tested the parfiles and, ok, I figured out which one does what, but I'm not yet clear on how to combine the results to obtain the actual NSBH initial data. I tried to understand what the test.ccl was and how it should be used, but I'm still unclear on how to proceed. Am I missing something? Thanks for your help Andrea Endrizzi

2 1

Einstein Toolkit Meeting Reminder
by users＠einsteintoolkit.org 27 May '20

27 May '20

Hello, Please consider joining the weekly Einstein Toolkit phone call at 9:00 am US central time on Thursdays. For details on how to connect and what agenda items are to be discussed, use the link below. https://docs.einsteintoolkit.org/et-docs/Main_Page#Weekly_Users_Call --The Maintainers

1 0

[USERS] Problems regarding Binary neutron star merger parameter file available on the Gallery of Einstein Toolkit Website
by Aryan Sharma 27 May '20

27 May '20

Hi all, These are the questions regarding the binary neutron stars merger parameter file which is openly available on the Einstein Toolkit website under the Gallery section of the the website. The name of the parameter file is nsnstohmns.par. I have* total** three questions* regarding this as follows:-- *Question --1:-* So, when I downloaded this parameter file and ran it after I had compiled all the necessary thorns; I got the errors that the grid structure is inconsistent and it is impossible to continue. Can this be fixed? I have attached the error that appeared multiple times in the standard error output file as follows:-- '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ml=0 rl=0 c=7 dh::light_dboxes:{ exterior: ([1536,0,2816]:[5376,2304,5888]:[256,256,256]/[6,0,11]:[21,9,23]/[16,10,13]/2080) owned: ([2304,768,3584]:[4608,1536,5120]:[256,256,256]/[9,3,14]:[18,6,20]/[10,4,7]/280) interior: ([2304,0,3584]:[4608,1536,5120]:[256,256,256]/[9,0,14]:[18,6,20]/[10,7,7]/490) active_size: 280 } The grid structure is inconsistent. It is impossible to continue. Writing backtrace to nsnstohmns_from-ET-website/backtrace.42.txt Writing backtrace to nsnstohmns_from-ET-website/backtrace.45.txtreceived signal 6 Writing backtrace to nsnstohmns_from-ET-website/backtrace.63.txt cactus_sim: /home/ with PID 76212cactus_sim: /home/sharmaar/Cactus/arrangements/Carpet/Carpet/src/helpers.cc:275: int Carpet::Abort(const _cGH *, int): Assertion `0' failed. Rank cactus_sim: /home/sharmaar/Cactus/arrangements/Carpet/Carpet/src/helpers.cc:275: int Carpet::Abort(const _cGH *, int): Assertion `0' failed. 19 with PID 7231 received signal 6ml=0 ml=0 rl=0 dh::level_dboxes:{ active: bboxset<CCTK_INT4,3>(set<bbox>:{([768,768,768]:[6144,11520,6144]:[256,256,256]/[3,3,3]:[24,45,24]/[22,43,22]/20812)},stride:[256,256,256],offset:[0,0,0]) } '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ml=0 rl=0 dh::fast_dboxes:{ fast_mg_rest_sendrecv: [] fast_mg_prol_sendrecv: [] fast_ref_prol_sendrecv: [] fast_ref_rest_sendrecv: [] fast_sync_sendrecv: [(send:(ext:([2304,0,0]:[2816,1536,1536]:[256,256,256]/[9,0,0]:[11,6,6]/[3,7,7]/147),c:1),recv:(ext:([2304,0,0]:[2816,1536,1536]:[256,256,256]/[9,0,0]:[11,6,6]/[3,7,7]/147),c:0)),(send:(ext:([0,0,1792]:[2048,1536,2304]:[256,256,256]/[0,0,7]:[8,6,9]/[9,7,3]/189),c:3),recv:(ext:([0,0,1792]:[2048,1536,2304]:[256,256,256]/[0,0,7]:[8,6,9]/[9,7,3]/189),c:0)),(send:(ext:([2304,0,1792]:[2816,1536,2304]:[256,256,256]/[9,0,7]:[11,6,9]/[3,7,3]/63),c:4),recv:(ext:([2304,0,1792]:[2816,1536,2304]:[256,256,256]/[9,0,7]:[11,6,9]/[3,7,3]/63),c:0)),(send:(ext:([0,1792,0]:[2048,2304,1536]:[256,256,256]/[0,7,0]:[8,9,6]/[9,3,7]/189),c:12),recv:(ext:([0,1792,0]:[2048,2304,1536]:[256,256,256]/[0,7,0]:[8,9,6]/[9,3,7]/189),c:0)),(send:(ext:([2304,1792,0]:[2816,2304,1536]:[256,256,256]/[9,7,0]:[11,9,6]/[3,3,7]/63),c:13),recv:(ext:([2304,1792,0]:[2816,2304,1536]:[256,256,256]/[9,7,0]:[11,9,6]/[3,3,7]/63),c:0)),(send:(ext:([0,1792,1792]:[2048,2304,2304]:[256,256,256]/[0,7,7]:[8,9,9]/[9,3,3]/81),c:15),recv:(ext:([0,1792,1792]:[2048,2304,2304]:[256,256,256]/[0,7,7]:[8,9,9]/[9,3,3]/81),c:0)),(send:(ext:([2304,1792,1792]:[2816,2304,2304]:[256,256,256]/[9,7,7]:[11,9,9]/[3,3,3]/27),c:16),recv:(ext:([2304,1792,1792]:[2816,2304,2304]:[256,256,256]/[9,7,7]:[11,9,9]/[3,3,3]/27),c:0)),(send:(ext:([1536,0,0]:[2048,1536,1536]:[256,256,256]/[6,0,0]:[8,6,6]/[3,7,7]/147),c:0),recv:(ext:([1536,0,0]:[2048,1536,1536]:[256,256,256]/[6,0,0]:[8,6,6]/[3,7,7]/147),c:1)),(send:(ext:([0,0,1024]:[2048,1536,1536]:[256,256,256]/[0,0,4]:[8,6,6]/[9,7,3]/189),c:0),recv:(ext:([0,0,1024]:[2048,1536,1536]:[256,256,256]/[0,0,4]:[8,6,6]/[9,7,3]/189),c:3)),(send:(ext:([1536,0,1024]:[2048,1536,1536]:[256,256,256]/[6,0,4]:[8,6,6]/[3,7,3]/63),c:0),recv:(ext:([1536,0,1024]:[2048,1536,1536]:[256,256,256]/[6,0,4]:[8,6,6]/[3,7,3]/63),c:4)),(send:(ext:([0,1024,0]:[2048,1536,1536]:[256,256,256]/[0,4,0]:[8,6,6]/[9,3,7]/189),c:0),recv:(ext:([0,1024,0]:[2048,1536,1536]:[256,256,256]/[0,4,0]:[8,6,6]/[9,3,7]/189),c:12)),(send:(ext:([1536,1024,0]:[2048,1536,1536]:[256,256,256]/[6,4,0]:[8,6,6]/[3,3,7]/63),c:0),recv:(ext:([1536,1024,0]:[2048,1536,1536]:[256,256,256]/[6,4,0]:[8,6,6]/[3,3,7]/63),c:13)),(send:(ext:([0,1024,1024]:[2048,1536,1536]:[256,256,256]/[0,4,4]:[8,6,6]/[9,3,3]/81),c:0),recv:(ext:([0,1024,1024]:[2048,1536,1536]:[256,256,256]/[0,4,4]:[8,6,6]/[9,3,3]/81),c:15)),(send:(ext:([1536,1024,1024]:[2048,1536,1536]:[256,256,256]/[6,4,4]:[8,6,6]/[3,3,3]/27),c:0),recv:(ext:([1536,1024,1024]:[2048,1536,1536]:[256,256,256]/[6,4,4]:[8,6,6]/[3,3,3]/27),c:16))] fast_ref_bnd_prol_sendrecv: [] fast_ref_refl_sendrecv_0_0: [] fast_ref_refl_sendrecv_0_1: [] fast_ref_refl_sendrecv_1_0: [] fast_ref_refl_sendrecv_1_1: [] fast_ref_refl_sendrecv_2_0: [] fast_ref_refl_sendrecv_2_1: [] fast_ref_refl_prol_sendrecv_0_0: [] WARNING level 0 from host nid00272 process 0 in thorn CarpetLib, file /home/sharmaar/Cactus/arrangements/Carpet/CarpetLib/src/dh.cc:2123: -> The grid structure is inconsistent. It is impossible to continue.=0 c=8 dh::light_dboxes:{ exterior: ([4096,0,2816]:[6912,2304,5888]:[256,256,256]/[16,0,11]:[27,9,23]/[12,10,13]/1560) owned: ([4864,768,3584]:[6144,1536,5120]:[256,256,256]/[19,3,14]:[24,6,20]/[6,4,7]/168) interior: ([4864,0,3584]:[6912,1536,5120]:[256,256,256]/[19,0,14]:[27,6,20]/[9,7,7]/441) active_size: 168WARNING level 1 from host nid00805 process 0 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *Question-- 2:-* So, When I saw this I changed the grid structure as below and removed rotating symmetry180 and made it a simple grid structure and it worked. But now the problem is with the thorn NSTracker which calls the Hydrobase_analysis to calculate the maximum rho and it's location but I keep getting the below mentioned warnings and thus the refinement regions centered on the neutron stars are not moving. Could you please help me in this? Like is it possible to do it work correctly? ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Changes to grid structure:-- OLD CoordBase::xmin = 0.00 CoordBase::ymin = -396.00 CoordBase::zmin = 0.00 CoordBase::xmax = 396.00 CoordBase::ymax = 396.00 CoordBase::zmax = 396.00 ActiveThorns = "RotatingSymmetry180 ReflectionSymmetry" ReflectionSymmetry::reflection_z = "yes" NEW CoordBase::xmin = -396.00 CoordBase::ymin = -396.00 CoordBase::zmin = -396.00 CoordBase::xmax = 396.00 CoordBase::ymax = 396.00 CoordBase::zmax = 396.00 ActiveThorns = "ReflectionSymmetry" ##RotatingSymmetry180 ReflectionSymmetry::reflection_z = "no" '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Warnings after this:-- Found more than one (3) identical maximum, using average location (15.1875,0,0). while executing schedule bin Hydro_Analysis_LocationSearch, routine Hydro_Analysis::Hydro_Analysis_LocationSearch_Combine in thorn Hydro_Analysis, file /home/sharmaar/Cactus/arrangements/EinsteinAnalysis/Hydro_Analysis/src/Hydro_Analysis.c:199: -> Found more than one (3) identical maximum, using average location (15.1875,0,0). } ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; WARNING level 1 from host nid00805 process 0 while executing schedule bin Hydro_Analysis_LocationSearch, routine Hydro_Analysis::Hydro_Analysis_LocationSearch_Combine in thorn Hydro_Analysis, file /home/sharmaar/Cactus/arrangements/EinsteinAnalysis/Hydro_Analysis/src/Hydro_Analysis.c:228: -> Could not find grid point with maximum density 0.000956964 on grid. Using old location (15.1875,0,0). Could not find grid point with maximum density 0.000956964 on grid. Using old location (15.1875,0,0). ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *Question--3:-* So, this is my final query. Seeing this I thought of trying to remove the refinement regions centered at the stars and now what I did was to remove the active thorns like CarpetTracker, NSTracker and Hydro_Analysis that were used mainly for the refinement regridding at the center of the stars and I also changed the num_centers to 1 centered at origin. Now the problem is that the evolution is happening but the reductions(max,min) obtained by Carpet IOScalar for hydrobase variables like rho is wrongly shown in the .asc files. They are showing for rho the value 1e-11 for max and min both which I think is the value of rho at the origin i.e the center of the refinement levels. The fact that I know that the initial data was correctly calculated and that the evolution does not have all rho values as 1e-11 is that I visualized the initial data (IOHDF5 3D data) using VisIt and it showed me the stars with the correct values of rho and other variables. Also the evolved values of rho along x,y,z axis seem to be correctly evolving as the data in these .asc files is also correct. I also checked the reductions of GRHydro::dens variable which seems to be correct. Thus there maybe problem in the reductions. Could you please help me in this and give me some insight into it if possible? I have attached the Carpet IOScalar parameters that are set. ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' IOBasic::outInfo_reductions = "maximum" IOBasic::outInfo_vars = " Carpet::physical_time_per_hour HydroBase::rho ML_ADMConstraints::ML_Ham SystemStatistics::maxrss_mb GRHydro::dens{reductions = 'sum maximum'} HydroBase::w_lorentz " IOScalar::outScalar_every = 256 # every_coarse #IOScalar::all_reductions_in_one_file = "yes" IOScalar::one_file_per_group = "no" IOScalar::outScalar_reductions = "minimum maximum average norm1 norm2" IOScalar::outScalar_vars = " ADMBase::lapse ADMBase::shift ADMBase::metric ADMBase::curv HydroBase::rho HydroBase::vel HydroBase::w_lorentz GRHydro::dens{reductions = 'minimum maximum average norm1 norm2 sum'} SystemStatistics::process_memory_mb SphericalSurface::sf_radius ML_ADMConstraints::ML_Ham " '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Finally I have also attached the final parameter file which I am using which have a few more changes that I did apart from the above mentioned ones. I thank you for taking out the time to read through this long mail. I really hope you could help me out in this. Thanks and regards Aryan Sharma ᐧ

2 1

Issues to install: failed to configure openmpi
by Rodriguez, Shanshan 26 May '20

26 May '20

Dear group, We are reinstalling the ET_2019_10 version following the CactusTutorial.ipynb and keep running into issues when installing the prerequisites. Our system is macOS Catalina with Xcode and Macports installed successfully. When we use the commend: sudo port -N install pkgconfig gcc9 openmpi-gcc9 fftw-3 gsl jpeg zlib hdf5 +fortran +gfortran openssl subversion ld64 We get the following errors: ---> Computing dependencies for pkgconfig ---> Cleaning pkgconfig ---> Computing dependencies for gcc9 ---> Cleaning gcc9 ---> Computing dependencies for openmpi-gcc9 ---> Configuring openmpi-gcc9 Error: Failed to configure openmpi-gcc9, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_openmpi/openmpi-gcc9/work/build/config.log Error: Failed to configure openmpi-gcc9: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_openmpi/openmpi-gcc9/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port openmpi-gcc9 failed We are wondering if anyone have ran into similar issues and could give us a hint about how to fix this. Thank you very much, Shanshan

2 5

Agenda for Thursday's Meeting
by users＠einsteintoolkit.org 25 May '20

25 May '20

Please update the Wiki with agenda items for Thursday's meeting. Thanks! https://docs.einsteintoolkit.org/et-docs/meeting_agenda --The Maintainers

1 0

North American EinsteinToolkit Workshop, Aug 3-7
by Steven R. Brandt 21 May '20

21 May '20

North American EinsteinToolkit Workshop, August 3-7 *Update:*The in-person event has been postponed until next year due to concerns relating to COVID19. An online event is planned during the Aug 3-7 event, details of which will be forthcoming. Stay safe. --Steve

1 0

ETK Meeting Minutes 2020-05-21
by Federico Cipolletta 21 May '20

21 May '20

Participants: Steve Brandt, Roland Haas, Zach Etienne, Peter Diener, Yosef Zlochower, Maria Hamilton, Bill Gabella, Evans Christopher, Liu Hooyoung, Atul Kedia, Federico Cipolletta Chair: Roland Haas Minutes: Federico Cipolletta Release Team + Reviewers + Contributors List: Roland asked if anyone has any particular preference on how the total list of people who worked in the next release will be presented. The list is available at the wiki webpage: https://docs.einsteintoolkit.org/et-docs/Meeting_agenda Zach suggested having just a total list with simply names of people + special mentions if needed. Roland approved to have a look at that, in order to render the list as compact as possible. Testsuite Results: Roland said that the current situation with testsuites is presented in http://einsteintoolkit.org/testsuite_results/index.php?show_all=1 In particular, some clusters seem to fail with tests that previously were successful. This can be due to changes in compilers or other technicalities in each cluster (e.g. BlueWaters had a change in compilers' version). Results of tests are held in this repository: https://bitbucket.org/einsteintoolkit/testsuite_results/src/master/ Federico asked what the blue dots mean. Roland answered that these dots represent tests that are not executed. Roland noticed that there is currently no information on tests performed in any European cluster. He asked Federico if he or Bruno has some info about that (not mandatory). Federico reported that the group in Italy recently performed the testsuite on Marconi. He will share the results with Roland. Gallery Test: Roland asked participants if there were some news about tests to be performed, listed at https://bitbucket.org/einsteintoolkit/tickets/issues?kind=task&milestone=ET… Bill Gabella reported that the Poisson test was performed one or two months ago and it was performing well. Roland reported that the Multi Patch Scalar Wave Test is expected to work fine. Atul Kedia asked if any one of the participants has any clue on how to show horizon in the BBH test. Roland suggested that this information should be contained as an output of one thorn (probably QuasiLocalMeasures), but it would be better to ask the community. Unanswered Questions: Roland noticed that there were no new unanswered questions, but asked the participants if they have some update on that. Federico said that he was in touch with Alessandro Ciarfella for the scalar 1D Wave equation and Alessandro managed to solve his issue. Steve suggested Federico contact himself, who will take care of closing the question. Tickets: Roland reported that he had no current news. Steve reported that there is a change with Ubuntu which recently had some issue with some new library dependency (probably something related to hwloc). He will give updates about that later. Best Regards, Federico Cipolletta.

1 0

Einstein Toolkit Meeting Reminder
by users＠einsteintoolkit.org 20 May '20

20 May '20

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users May 2020