Users January 2017

users@lists.einsteintoolkit.org

12 participants
19 discussions

Re: [Users] [ET Trac] [Einstein Toolkit] #1326: running loopcontrol on strange number of threads fails
by Erik Schnetter 11 Apr '19

11 Apr '19

Do you have a backtrace? -erik On Sunday, March 22, 2015, Einstein Toolkit < trac-noreply(a)einsteintoolkit.org> wrote: > #1326: running loopcontrol on strange number of threads fails > ------------------------------------+--------------------------------------- > Reporter: rhaas | Owner: > Type: defect | Status: new > Priority: minor | Milestone: > Component: EinsteinToolkit thorn | Version: > Resolution: | Keywords: LoopControl > ------------------------------------+--------------------------------------- > > Comment (by rhaas): > > This still happens even with current (Sun Mar 22 18:46:21 CET 2015) trunk, > though failure looks a bit different now: > {{{ > actus_sim: > /data/rhaas/postdoc/gr/ET_trunk/configs/sim/build/LoopControl/loopcontrol.cc:312: > T {anonymous}::divexact(T, T) [with T = int]: Assertion `i % j == 0' > failed > }}} > > -- > Ticket URL: <https://trac.einsteintoolkit.org/ticket/1326#comment:1> > Einstein Toolkit <http://einsteintoolkit.org> > The Einstein Toolkit > _______________________________________________ > Trac mailing list > Trac(a)einsteintoolkit.org > http://lists.einsteintoolkit.org/mailman/listinfo/trac > -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.perimeterinstitute.ca/personal/eschnetter/

3 2

GRHydro_InitData - magnetic fields - neutron stars
by Daniel Gerlicher 10 Feb '17

10 Feb '17

Hi! I have a question regarding the initial data thorn of GRHydro. The documentation and ccl files didn't really help me. The following was taken from paper [1] and now I am trying to add magnetic fields to the stars. My questions are: 1) What are the units of (A) and (B) below? Is the following conversion factor correct? The star should have a field strength of 10^16 Gauss. Using the following conversion would give "0.00011973228161339154" for (A) and (B). 2) What are reasonable values for (C..F)? Can I just use the default ones given in param.ccl? Is there a reason not to use the default ones? My plan is to analyse the structure of the field after the collapse and the influence on the wave signal. > # constants, in SI > G = 6.673e-11 # m^3/(kg s^2) > c = 299792458 # m/s > M_sun = 1.98892e30 # kg > mu0 = 1.2566370614e-6 # Newton/Ampere^2 > Kb = 1.3806488e-23 # Joule/K > Mparsec = 3.08567758e19 # km > CU_to_Tesla = c**4 / M_sun / G**(1.5)* mu0**(0.5) > CU_to_Gauss = c**4 / M_sun / G**(1.5)* mu0**(0.5) * 10000 > #------------------------------------------------- > # Magentic Fields: > #------------------------------------------------- > (A) GRHydro_InitData::poloidal_A_b_1 = 0.00011973228161339154 > (B) GRHydro_InitData::poloidal_A_b_2 = 0.00011973228161339154 > (C) GRHydro_InitData::poloidal_P_cut_1 = 3.72e-6 #Non è in > percentuale!! > (D) GRHydro_InitData::poloidal_P_cut_2 = 3.72e-6 #Non è in > percentuale!! > (E) GRHydro_InitData::poloidal_n_p = 1 #Esponente di max((rho-rho_cut),0) > (F) GRHydro_InitData::poloidal_P_p = 2 #Esponente di max((P-P_cut),0) > GRHydro_InitData::Xc_1 = -13.5 > GRHydro_InitData::Xc_2 = 13.5 > GRHydro_InitData::Yc_1 = 0.0 > GRHydro_InitData::Yc_2 = 0.0 > GRHydro_InitData::Zc_1 = 0.0 > GRHydro_InitData::Zc_2 = 0.0 3) These should be fine, right? > GRHydro::transport_constraints = "yes" > GRHydro::track_divB = "yes" > GRHydro::calculate_bcom = "yes" > #GRHydro::clean_divergence = "no" > GRHydro::Grhydro_MaxNumConstrainedVars = 33 > GRHydro::GRHydro_MaxNumEvolvedVars = 10 > > HydroBase::initial_Bvec = "bin_ns_poloidalmagfield" The field is evolved and everything seems okay, I am just not sure about the units and (C..F). 4) Is there a good method to visualize the B-field? Visit + Carpet hdf5 reader + Streamlines? (seems to be "buggy") Thank you! Best regards, Daniel References: [1] "R. De Pietri, A. Feo, F. Maione, and F. Löffler, “Modeling Equal and Unequal Mass Binary Neutron Star Mergers Using Public Codes,” Phys. Rev., vol. D93, no. 6, p. 064047, 2016."

3 3

Compile question
by Guy Pitman 10 Feb '17

10 Feb '17

Hi, I am trying to compile a new Kranc thorn on a MacBook Pro (Sierra) and am getting an error COMPILING arrangements/Carpet/CarpetLib/src/prolongate_3d_real8_tvd.F90 gfortran: warning: couldn’t understand kern.osversion ‘16.1.0 /Users/Guy/Documents/Einsteintoolkit/Cactus/configs/kranc/build/CarpetLib/prolongate_3d_real8_tvd.f90:128.11: CHKIDX (i0 ,j0 ,k0 , srciext,srcjext,srckext, "src") 1 Error: Unclassifiable statement at (1) /Users/Guy/Documents/Einsteintoolkit/Cactus/configs/kranc/build/CarpetLib/prolongate_3d_real8_tvd.f90:129.11: CHKIDX (i0+2,j0+2,k0+2, srciext,srcjext,srckext, "src") 1 Error: Unclassifiable statement at (1) /Users/Guy/Documents/Einsteintoolkit/Cactus/configs/kranc/build/CarpetLib/prolongate_3d_real8_tvd.f90:170.11: CHKIDX (dstioff+i+1, dstjoff+j+1, dstkoff+k+1, dstiext,dstjext,dstke 1 Error: Unclassifiable statement at (1) make[4]: *** [prolongate_3d_real8_tvd.F90.o] Error 1 make[3]: *** [make.checked] Error 2 make[2]: *** [/Users/Guy/Documents/Einsteintoolkit/Cactus/configs/kranc/lib/libthorn_CarpetLib.a] Error 2 make[1]: *** [kranc] Error 2 make: *** [kranc-config] Error 2 I previously installed the simple example for OSX and that ran OK. The attached file contains the ThornList that I am using. Do you have any suggestions? Thank you Regards Guy

4 19

new web page design
by Frank Loeffler 07 Feb '17

07 Feb '17

Hi The current Einstein Toolkit web pages at http://einsteintoolkit.org/ are about to be replaced with a newer design. Some content changes might go with that, but a strong emphasis is on the design change. Feel free to suggest content improvements, but please don't mix them with the design change. The new pages can currently be previewed at http://einsteintoolkit.org/new/index.html We would like to get feedback before making the switch. In particular, we are interested in experiences with all kinds of browsers and/or devices and screen sizes. If you think you've encountered a bug that relates to the layout, a screen-shot might be the best way to show what you see. You can view the source behind the web pages within the bitbucket repository https://bitbucket.org/einsteintoolkit/www (and separate, due to its size): https://bitbucket.org/einsteintoolkit/seminars If you are developer, you should have write permissions. Reporting something like a typo probably takes longer than fixing it there. If you like to make larger changes and feel unsure about them, feel free to open a pull request and a ticket. We will discuss received feedback at the next Einstein Toolkit call (Monday next week; 6th of February). Depending how things go, that might be as early as the new version goes live. Frank Löffler PS: Don't report the crappy look of images in Microsoft Edge (probably all IE as well). That's due to the crappy image interpolation MS uses, and there isn't a good way to deal with that other than using a decent browser.

5 5

meeting minutes for 2017-01-30
by Roland Haas 30 Jan '17

30 Jan '17

Present: Frank, Roland, Ian, Gabrielle Allen, Vassili, Steve ET website: * online at http://einsteintoolkit.org/new/ * can be edited via git repo at https://bitbucket.org/einsteintoolkit/www/src which all maintainers should be able to edit * sub-menu button in About maybe too small, better to have a landing like page as for "Documentation" * find a middle ground between all on one page and very many tiny pages * needs to be tested on more common browsers, suggest at least Safari/OSX, Firefox, Chrome, Edge/Internet Explorer, mobile broswers on both IOS and Android both phone and tablets * contact someone with design experience about colour scheme Read/write driven SYNC: * Steve worked on this and has sent out a link: https://github.com/stevenrbrandt/PresyncWave * works for a wavetoy, not yet clear if prolongation would work or if works for production code * the README file should contain usage instructions * feedback would be appreciated Simfactory machine files/options/submit/run scripts * treat as documentation, ie no review is required but use your own good judgement 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://keys.gnupg.net.

2 2

Einstein Toolkit Meeting Reminder
by Frank Loeffler 30 Jan '17

30 Jan '17

Hi Please consider joining the weekly Einstein Toolkit phone call at 9:30 am US central time on Mondays. As usual, you can find instructions how to join on the following web site: http://einsteintoolkit.org/community/support/ We use a Google hangout, with an URL announced on this list before the meeting. Frank Loeffler

2 2

ADMMass Issue
by Gwyneth Allwright 29 Jan '17

29 Jan '17

Hi All, I've been trying to use the ADMMass thorn to calculate the ADM mass for a binary black hole system. The initial ADM mass given by TwoPunctures is 0.989, but ADMMass returns 0.031 (using both of the available methods). Does anyone know what could be going wrong? Alternatively, are there other thorns that can be used to calculate the ADM mass? Thanks in advance! Gwyneth

3 3

NSBH simulations with ET
by Maitraya Bhattacharyya 29 Jan '17

29 Jan '17

Hi all, Can anyone talk about the CPU hours that it takes to do NSBH simulations on ET. Also are there provisions available for rotating neutron stars ? I was asking around for some public catalogs of NSBH waveforms and so far the answer has been in the negative. Maitraya

1 0

Format of CactusPUGHIO/IOHDF5 output files
by Maitraya Bhattacharyya 24 Jan '17

24 Jan '17

Hi all, Does anyone know how the data is formatted into HDF5 files as outputted by CactusPUGHIO. I specifically want to know how the lapse, shift and spatial metric are stored in a unigrid inside the hdf5 files. Any example file would be most welcome. It's just that I am trying to format some data into a format which is recognized by EHFinder. Thanks, Maitraya.

2 1

meeting minutes for 2017-01-23
by Roland Haas 23 Jan '17

23 Jan '17

Present: Eloisa, Erik, Frank, Ian, Josh, Yosef, Vassili, Roberto, Roland, Cory, Steve tickets: * proposed VINFO macro fails when called with only a single argument. Use suggested change by Roland of absorbing all arguments in __VA_ARGS__. * piraha_everywhere: Philipp Moesta found issues with the ccl files in Zelmani, will post the files as stress test for piraha in a ticket Release and development plans for the spring * piraha_everywhere * include code changes from Parma group, incl. LORENE2 * compute RHS in MoL_PostStep rather than MoL_CalcRHS in at least McLachlan * GRHydro cleanup, move F90 code into an archive directory * include RNSID (Roberto and Nick Stergioulas), proposal should be ready in the next couple of weeks Updated website layout: * http://einsteintoolkit.org/new/ * Erik suggests to have the tutorial more prominent (ideally on the front page) ET workshop in summer in the US: * sometime in summer, but no concrete date is set 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://keys.gnupg.net.

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users January 2017