Users

users@lists.einsteintoolkit.org

3 participants
3984 discussions

Announcement: Einstein Toolkit New Users Workshop
by Frank Loeffler 06 Feb '12

06 Feb '12

The Einstein Toolkit (http://einsteintoolkit.org) will host its spring workshop 2012 following the April APS meeting in Atlanta, GA, from Tuesday, April 3rd, 4pm to Friday April 6th, noon. This workshop is targeted at new and potential new users of the relativity infrastructure. It will provide a general introductions into numerical relativity (although some previous knowledge would be beneficial) and in code development within large collaborations. Hands-on sessions will help to familiarize attendees with the Einstein Toolkit. Participants are asked to bring their own laptops. We would like to invite especially students from physics and computer science to participate. The number of attendees is limited, and while registration is free, it is required. We anticipate to be able to support a small number of participants financially, by covering parts/all of their travel, hotel and meal cost. Preference will be given to students. In order register, write an email to workshop(a)einsteintoolkit.org and specify: * your name, affiliation and title * your estimated arrival and departure time/date * whether you apply for support (and if so, state if you are undergraduate / graduate student / postdoc) * your special needs Detailed workshop information can be found at https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012. The Einstein Toolkit Consortium.

1 0

Einstein Toolkit Meeting Reminder
by Frank Loeffler 06 Feb '12

06 Feb '12

Hi Please consider joining the weekly Einstein Toolkit phone call at 10 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/ I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and the conference id is 118682#. Peter Diener will host this weeks call, and the main topic will be the organization of the Einstein Toolkit workshop in Atlanta [1], primarily the schedule [2]. The topics of the invited talks are still open, but with this in mind we should have a schedule ready after this call to have enough time for preparations. Frank Loeffler [1] https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012 [2] https://docs.einsteintoolkit.org/et-docs/Schedule_Proposal

1 0

Reorganisation of some of Carpet's internals
by Erik Schnetter 05 Feb '12

05 Feb '12

I have just re-organised some of Carpet's internal operators which implement the actual copy/restriction/prolongation operators. This will make it easier to implement new functionality that uses these operators, such as e.g. periodic boundary conditions within Carpet, or refluxing. The previous ad-hoc code was causing problems in some cases, and I hope that this cleaner re-implementation solves these. The main change is to pass an additional argument "slabinfo" argument to the operators that can encode additional information, such as is needed e.g. for periodic symmetries or refluxing. In addition, the respective ad-hoc "fixes" have been removed. -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.cct.lsu.edu/~eschnett/

1 0

Meeting minutes
by Roland Haas 30 Jan '12

30 Jan '12

Hello all, present were: Frank, Roland, Bruno, Tanja, Erik, Steve, Yosef, Josh, Ian, Peter ET seminars: * please add seminar proposals to the list, we'd rather have too many than not enough Spring workshop in Atlanta: * information (incl. proposed hotel) available at https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012 * we have not definitive answer on funding but are hopeful * will discuss and invite invited speakers off-line * mailing list: workshop(a)einsteintoolkit.org for participants to register. Currently subscribed: Josh, Pablo, Tanja, Frank * Frank will create and send around flyers to be hung in public place * possible topics: ** introduction to NR ** introduction to Cactus ** Visualization using VisIt, gnuplot/grace/matplotlib ** possibly Ian's Mathematica based postprocessing/visualization package * hands on cluster: ** will use QueenBee (Steve) ** reserve block of nodes (Steve), arrange with LONI to pay for this ** use gcc compilers (Intel licenses are scarce) ** virtualbox linux image for participant's computers Next week's host will be 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://keys.gnupg.net.

1 0

Einstein Toolkit Meeting Reminder
by Frank Loeffler 29 Jan '12

29 Jan '12

Hi Please consider joining the weekly Einstein Toolkit phone call at 10 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/ I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and the conference id is 118682#. Some of the things that will be discussed are: - Einstein Toolkit workshop in Atlanta [1] - Remind ourselves of submitting Einstein Seminar proposals [2] Frank Loeffler [1] https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012 [2] https://docs.einsteintoolkit.org/et-docs/Einstein_Toolkit_Seminar_Proposals

1 0

using WeylScal4 and Multipole thorns in McLachlan
by Jose Fiestas Iquira 25 Jan '12

25 Jan '12

Hello, I am using WeylScal4 and Multipole thorns in McLachlan, and started a run using simfactory. It started well but stops after an MPI error. Before I get some warnings related to the parameters m_mode and l_mode. I am attaching the error file. It runs only for the initial time step zero. Does somebody have probably a hint what is the best parameter setting? I am using following: ActiveThorns = "WeylScal4 Multipole" WeylScal4::offset = 1e-8 WeylScal4::fd_order = "4th" WeylScal4::verbose = 0 Multipole::nradii = 8 Multipole::out_every = 128 Multipole::radius[0] = 15 Multipole::radius[1] = 30 Multipole::radius[2] = 40 Multipole::radius[3] = 50 Multipole::radius[4] = 60 Multipole::radius[5] = 70 Multipole::radius[6] = 80 Multipole::radius[7] = 90 Multipole::variables = "WeylScal4::Psi4r{sw=-2 cmplx='WeylScal4::Psi4i' name='Psi4'}" Multipole::l_mode = 4 Multipole::m_mode = 4 Thanks, Jose

4 6

Hydro_Analysis problems
by Petr Tsatsin 23 Jan '12

23 Jan '12

I'm running the one from the repository from the official wiki page. I'm not sure if its "plain vanilla" ET checkout. >Hello Petr, Erik, >> I just added Hydro_Analysis thorn to static_tov.par and the run just >> crushes at the very beginning right after this warnings. I attached the >> full out file. >There was a bug in Hydro_Analysis_Init causing a segfault. It's fixed >now )in rev 119). Not sure where the L6 warnings came from though. Are >you running a plain vanilla ET checkout, Petr? Or a LSU/AEI version that >contains Multipatch code? > >Yours, >Roland -- Petr Tsatsin Graduate Student - Department of Physics Charles E. Schmidt College of Science Florida Atlantic University (561)-297-3386 cell: 561-692-2040 ptsatin(a)fau.edu, ptsatsin(a)gmail.com

2 1

Re: [Users] problem with first example simulation with ETK
by Ian Hinder 23 Jan '12

23 Jan '12

On 16 Jan 2012, at 23:21, Jose Fiestas Iquira wrote: > Thanks, I am attaching the output file. The output file looks fine - I can't see any problem with the simulation. According to the output file, it reached t = 100 M, and in the parameter file that is listed as cctk_final_time, so all looks well! > I did copy the development version. As I can see, it was already > fixed, so I should not get this warning, since I copied the > development version. Yes, if you are using the current development version, then I don't know why you get the warning. Can you check which version of Carpet you have by doing cd repos/carpet hg tip to be sure you are using the development version? > Is the puncture tracker not a better way to plot BH trajectories. It's cheaper to use the puncture tracker, because computing the horizon centroid is more expensive, but it has to be done every iteration, whereas the horizon can be found less frequently. For comparison with point-particle results, I don't think it makes much difference; the results are gauge dependent anyway so differences on the order of the horizon size cannot be interpreted physically. Since the parameter file already has horizon-finding built in, it is easier for you to use that. If you want to figure out how to add the puncture tracker to the simulation, you can start with these parameters: ActiveThorns = "PunctureTracker" PunctureTracker::track [0] = yes PunctureTracker::initial_x [0] = $xp PunctureTracker::which_surface_to_store_info[0] = 0 PunctureTracker::track [1] = yes PunctureTracker::initial_x [1] = $xm PunctureTracker::which_surface_to_store_info[1] = 1 IOASCII::out0D_vars = "PunctureTracker::pt_loc" Replace $xp and $xm with the initial x coordinates of the +x and -x punctures (this will be \pm TwoPunctures::par_b). You then need to choose two spherical surfaces (https://docs.einsteintoolkit.org/et-docs/Einstein_Toolkit_standards) which are not being used currently to store the puncture locations in. If there is already 0D output, just add the puncturetracker variable separated with a space. > I > did some plots, what are really the combinations xx, xy, xz, yy, zz ? > Are they related to the trajectories of one BH (projections)? What > about the second BH? You should have BH_diagnostics.ah1.gp and BH_diagnostics.ah2.gp. These correspond to the first and second BHs. If you look at the top of these files, you will see an explanation of the columns. More information about each column is available in the AHFinderDirect documentation (http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech128.html#x1…). Specifically, information about the BH_diagnostics output files is at http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech128.html#x1… To plot the trajectory of one of the BHs, you want to plot column 3 and column 4 in a parametric plot. > Cheers, > Jose > > On Mon, Jan 16, 2012 at 4:39 AM, Ian Hinder <ian.hinder(a)aei.mpg.de> wrote: >> >> On 14 Jan 2012, at 00:41, Jose Fiestas Iquira wrote: >> >> Hi Ian, >> I did the changes but it started and finished early. I am attaching >> the qc0-mclachlan.err file. At the end there is a warning in one of >> the Carpet files (mask_test.c) >> >> >> The warning you see, >> >> WARNING level 1 in thorn CarpetReduce processor 0 host qb517 >> (line 120 of >> /home/ettest24/Cactus/arrangements/Carpet/CarpetReduce/src/mask_test.c): >> -> Simulation domain volume and reduction weight sum differ >> >> is a known issue (https://trac.einsteintoolkit.org/ticket/434) which was >> fixed after the last release and the fix is only available in the >> development version. I believe that the warning is not fatal, and it should >> not have terminated the simulation. Can you also post the qc0-mclachlan.out >> file? >> >> Where can I find the puncture tracker? >> >> >> The PunctureTracker thorn is part of the Einstein Toolkit thornlist, so you >> should have it already. However, I think the best thing for you to do >> initially would be to look at the BH_diagnostics files for the apparent >> horizon centroid locations for tracking the locations of the BHs. >> >> >> >> >> Thanks, >> Jose >> >> On Fri, Jan 13, 2012 at 4:38 AM, Ian Hinder <ian.hinder(a)aei.mpg.de> wrote: >> >> >> On 13 Jan 2012, at 12:32, Jose Fiestas Iquira wrote: >> >> >> Yes, trajectories and wave forms would be enough for now. Which are >> >> the names of this files? Many of the .asc files have data like kxx, >> >> kxy, kxz, etc. Is there any description of them? >> >> >> Not that I am aware of. Files with extension .x.asc are 1D ascii output of >> grid functions from CarpetIOASCII. kxy is the variable name for the x,y >> component of the extrinsic curvature tensor K. The waveform file should be >> in mp_psi4_l2_m2_r*.asc where * corresponds to the radius of the extraction >> sphere. However, looking at the qc0-mclachlan.par file, I see that there is >> no wave extraction switched on. You should be able to enable wave >> extraction by adding something like the following to the parameter file: >> >> >> ActiveThorns = "WeylScal4 CarpetInterp AEILocalInterp Multipole" >> >> >> Multipole::nradii = 3 >> >> Multipole::radius[0] = 30 >> >> Multipole::radius[1] = 40 >> >> Multipole::radius[2] = 50 >> >> Multipole::variables = "WeylScal4::Psi4r{sw=-2 cmplx=’WeylScal4::Psi4i’}" >> >> Multipole::l_max = 4 >> >> WeylScal4::fdOrder = 4 >> >> >> (I haven't tested this, so let me know if it doesn't work) >> >> >> I've just found that the usual PunctureTracker thorn is not enabled in this >> example parameter file. So to look at trajectories you will have to use the >> apparent horizon centroids. These are in the files BH_diagnostics.ah*.gp. >> The meanings of the columns are at the top of the files. You want the >> centroid x and y columns to plot in GnuPlot. >> >> >> >> >> >> >> Thanks, >> >> Jose >> >> >> On Fri, Jan 13, 2012 at 12:41 AM, Ian Hinder <ian.hinder(a)aei.mpg.de> wrote: >> >> >> On 12 Jan 2012, at 23:46, Jose Fiestas Iquira wrote: >> >> >> Dear all, >> >> >> I run the tutorial and found other interesting examples like the >> >> McLachlan tool for Binary Black Holes. >> >> >> Regarding the McLachlan tool, >> >> Could somebody help me finding a description of the output? Is all >> >> contained in the .asc files? I would like to visualize it. >> >> >> >> Hi Jose, >> >> >> What sort of output do you want to visualise? Cactus thorns typically >> >> output "lightweight" information such as BH trajectories and waveforms as >> >> ASCII, and more heavyweight data -- like gridfunctions -- as HDF5. For the >> >> trajectories (from thorn Puncture Tracker) and waveforms (from Multipole) >> >> you can use gnuplot or anything that can read standard ASCII output to >> >> visualise them. For gridfunctions in HDF5 format, I think the easiest way >> >> to get started is to use VisIt, for which there is a Carpet plugin (though >> >> installing VisIt is sometimes not so easy!). >> >> >> Does anyone know if the Carpet plugin is distributed with VisIt yet? I >> >> believe that was the intention. >> >> >> >> >> Cheers, >> >> Jose >> >> >> >> On Wed, Jan 11, 2012 at 7:06 PM, Jose Fiestas Iquira <jafiestas(a)lbl.gov> >> >> wrote: >> >> >> Thanks to Erik for advise. ETK example simulation run successfully. >> >> >> >> >> On Wed, Jan 11, 2012 at 11:49 AM, Jose Fiestas Iquira <jafiestas(a)lbl.gov> >> >> wrote: >> >> >> Right, it looks good now: >> >> >> >> ./simfactory/bin/sim list-simulations >> >> >> static_tov [ACTIVE (RUNNING), restart 0000, job id 595490] >> >> >> >> Let see how it looks when it finishes. The example was set to 8 hours. >> >> >> >> Thanks, >> >> >> Jose >> >> >> >> >> On Wed, Jan 11, 2012 at 11:45 AM, Erik Schnetter <schnetter(a)cct.lsu.edu> >> >> wrote: >> >> >> On Wed, Jan 11, 2012 at 2:42 PM, Jose Fiestas Iquira <jafiestas(a)lbl.gov> >> >> wrote: >> >> >> >> The only thing is that now >> >> >> $ ./simfactory/bin/sim list-simulations >> >> >> returns >> >> >> >> Error: unknown command list-simulation >> >> >> Aborting Simfactory. >> >> >> >> Did you really type "list-simulations", and the error message says >> >> >> "list-simulation" (without the final "s")? >> >> >> >> -erik >> >> >> >> -- >> >> >> Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.cct.lsu.edu/~eschnett/ >> >> >> _______________________________________________ >> >> >> Users mailing list >> >> Users(a)einsteintoolkit.org >> >> http://lists.einsteintoolkit.org/mailman/listinfo/users >> >> >> >> -- >> >> Ian Hinder >> >> http://numrel.aei.mpg.de/people/hinder >> >> >> >> -- >> >> Ian Hinder >> >> http://numrel.aei.mpg.de/people/hinder >> >> >> <qc0-mclachlan.err> >> >> >> -- >> Ian Hinder >> http://numrel.aei.mpg.de/people/hinder >> > <qc0-mclachlan.out> -- Ian Hinder http://numrel.aei.mpg.de/people/hinder

2 7

Hydro_Analysis
by Petr Tsatsin 23 Jan '12

23 Jan '12

Hello, I'm trying to use Hydro_Analysis thorn and after I add it to my parameters simulations fails in the beginning giving a following warnings: WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerflux[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerminus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerplus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerrhs[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerfminus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerfplus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerminus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerplus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracer[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracer[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'Coordinates::general_coordinates' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerflux[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerminus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerplus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracerrhs[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerfminus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerfplus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerminus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracerplus[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::cons_tracer[0]' found WARNING[L6,P0] (Cactus): CCTK_VarIndex: No variable named 'GRHydro::tracer[0]' found Apparently there are non of this variables has been allocated. Basically I have a question how to use Hydro_Analysis thorn? How I can allocate this variables? Or maybe I have to add some parameters to get it to work? -- Petr Tsatsin Graduate Student - Department of Physics Charles E. Schmidt College of Science Florida Atlantic University (561)-297-3386 cell: 561-692-2040 ptsatin(a)fau.edu, ptsatsin(a)gmail.com

3 3

Carpet moving grids
by Petr Tsatsin 23 Jan '12

23 Jan '12

Hello , I'm trying to test a new version of my thorn which sets up initial data for moving neutron star. And I have couple questions about the Carpet moving grids. I was wondering if you could help answer it or suggest some recent documentation for Carpet which I can refer to? The question is simple: How to move grids in case of the moving neutron star? By looking at bbh parameter file I understood that Carpet gets information about position of the puncture from puncture tracker. Is there any trons which is providing this information in case of a neutron star or I have to write some thorn which is actually will track a center of the neutron star or its surface? Thank you! -- Petr Tsatsin Graduate Student - Department of Physics Charles E. Schmidt College of Science Florida Atlantic University (561)-297-3386 cell: 561-692-2040 ptsatin(a)fau.edu, ptsatsin(a)gmail.com

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users