<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 16 Jan 2012, at 23:21, Jose Fiestas Iquira wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Thanks, I am attaching the output file.<br></div></blockquote><div><br></div><div>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!</div><div><br></div><blockquote type="cite"><div>I did copy the development version. As I can see, it was already<br>fixed, so I should not get this warning, since I copied the<br>development version.<br></div></blockquote><div><br></div><div>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</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>cd repos/carpet</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>hg tip</div><div><br></div><div>to be sure you are using the development version?</div><div><br></div><blockquote type="cite"><div>Is the puncture tracker not a better way to plot BH trajectories. </div></blockquote><div><br></div><div>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.</div><div><br></div><div><div>If you want to figure out how to add the puncture tracker to the simulation, you can start with these parameters:</div><div><br></div><div>ActiveThorns = "PunctureTracker"</div><div><br></div><div>PunctureTracker::track [0] = yes</div><div>PunctureTracker::initial_x [0] = $xp</div><div>PunctureTracker::which_surface_to_store_info[0] = 0</div><div>PunctureTracker::track [1] = yes</div><div>PunctureTracker::initial_x [1] = $xm</div><div>PunctureTracker::which_surface_to_store_info[1] = 1</div><div><br></div><div>IOASCII::out0D_vars = "PunctureTracker::pt_loc"</div><div><br></div><div>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 (<a href="https://docs.einsteintoolkit.org/et-docs/Einstein_Toolkit_standards">https://docs.einsteintoolkit.org/et-docs/Einstein_Toolkit_standards</a>) 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.</div><div><br></div></div><blockquote type="cite"><div>I<br>did some plots, what are really the combinations xx, xy, xz, yy, zz ?<br>Are they related to the trajectories of one BH (projections)? What<br>about the second BH?<br></div></blockquote><div><br></div><div>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 (<a href="http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech128.html#x144-2264000O4">http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech128.html#x144-2264000O4</a>). Specifically, information about the BH_diagnostics output files is at <a href="http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech128.html#x144-2274000O4.5.5">http://einsteintoolkit.org/documentation/ThornGuide/ThornGuidech128.html#x144-2274000O4.5.5</a></div><div><br></div><div>To plot the trajectory of one of the BHs, you want to plot column 3 and column 4 in a parametric plot.</div><div><br></div><br><blockquote type="cite"><div>Cheers,<br>Jose<br><br>On Mon, Jan 16, 2012 at 4:39 AM, Ian Hinder <<a href="mailto:ian.hinder@aei.mpg.de">ian.hinder@aei.mpg.de</a>> wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On 14 Jan 2012, at 00:41, Jose Fiestas Iquira wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi Ian,<br></blockquote><blockquote type="cite">I did the changes but it started and finished early. I am attaching<br></blockquote><blockquote type="cite">the qc0-mclachlan.err file. At the end there is a warning in one of<br></blockquote><blockquote type="cite">the Carpet files (mask_test.c)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The warning you see,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">WARNING level 1 in thorn CarpetReduce processor 0 host qb517<br></blockquote><blockquote type="cite"> (line 120 of<br></blockquote><blockquote type="cite">/home/ettest24/Cactus/arrangements/Carpet/CarpetReduce/src/mask_test.c):<br></blockquote><blockquote type="cite"> -> Simulation domain volume and reduction weight sum differ<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">is a known issue (<a href="https://trac.einsteintoolkit.org/ticket/434">https://trac.einsteintoolkit.org/ticket/434</a>) which was<br></blockquote><blockquote type="cite">fixed after the last release and the fix is only available in the<br></blockquote><blockquote type="cite">development version. I believe that the warning is not fatal, and it should<br></blockquote><blockquote type="cite">not have terminated the simulation. Can you also post the qc0-mclachlan.out<br></blockquote><blockquote type="cite">file?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Where can I find the puncture tracker?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The PunctureTracker thorn is part of the Einstein Toolkit thornlist, so you<br></blockquote><blockquote type="cite">should have it already. However, I think the best thing for you to do<br></blockquote><blockquote type="cite">initially would be to look at the BH_diagnostics files for the apparent<br></blockquote><blockquote type="cite">horizon centroid locations for tracking the locations of the BHs.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite">Jose<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Fri, Jan 13, 2012 at 4:38 AM, Ian Hinder <<a href="mailto:ian.hinder@aei.mpg.de">ian.hinder@aei.mpg.de</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 13 Jan 2012, at 12:32, Jose Fiestas Iquira wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Yes, trajectories and wave forms would be enough for now. Which are<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">the names of this files? Many of the .asc files have data like kxx,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">kxy, kxz, etc. Is there any description of them?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Not that I am aware of. Files with extension .x.asc are 1D ascii output of<br></blockquote><blockquote type="cite">grid functions from CarpetIOASCII. kxy is the variable name for the x,y<br></blockquote><blockquote type="cite">component of the extrinsic curvature tensor K. The waveform file should be<br></blockquote><blockquote type="cite">in mp_psi4_l2_m2_r*.asc where * corresponds to the radius of the extraction<br></blockquote><blockquote type="cite">sphere. However, looking at the qc0-mclachlan.par file, I see that there is<br></blockquote><blockquote type="cite">no wave extraction switched on. You should be able to enable wave<br></blockquote><blockquote type="cite">extraction by adding something like the following to the parameter file:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ActiveThorns = "WeylScal4 CarpetInterp AEILocalInterp Multipole"<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Multipole::nradii = 3<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Multipole::radius[0] = 30<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Multipole::radius[1] = 40<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Multipole::radius[2] = 50<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Multipole::variables = "WeylScal4::Psi4r{sw=-2 cmplx=’WeylScal4::Psi4i’}"<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Multipole::l_max = 4<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">WeylScal4::fdOrder = 4<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">(I haven't tested this, so let me know if it doesn't work)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I've just found that the usual PunctureTracker thorn is not enabled in this<br></blockquote><blockquote type="cite">example parameter file. So to look at trajectories you will have to use the<br></blockquote><blockquote type="cite">apparent horizon centroids. These are in the files BH_diagnostics.ah*.gp.<br></blockquote><blockquote type="cite"> The meanings of the columns are at the top of the files. You want the<br></blockquote><blockquote type="cite">centroid x and y columns to plot in GnuPlot.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Jose<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Fri, Jan 13, 2012 at 12:41 AM, Ian Hinder <<a href="mailto:ian.hinder@aei.mpg.de">ian.hinder@aei.mpg.de</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 12 Jan 2012, at 23:46, Jose Fiestas Iquira wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Dear all,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I run the tutorial and found other interesting examples like the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">McLachlan tool for Binary Black Holes.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regarding the McLachlan tool,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Could somebody help me finding a description of the output? Is all<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">contained in the .asc files? I would like to visualize it.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi Jose,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">What sort of output do you want to visualise? Cactus thorns typically<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">output "lightweight" information such as BH trajectories and waveforms as<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ASCII, and more heavyweight data -- like gridfunctions -- as HDF5. For the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">trajectories (from thorn Puncture Tracker) and waveforms (from Multipole)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">you can use gnuplot or anything that can read standard ASCII output to<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">visualise them. For gridfunctions in HDF5 format, I think the easiest way<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">to get started is to use VisIt, for which there is a Carpet plugin (though<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">installing VisIt is sometimes not so easy!).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Does anyone know if the Carpet plugin is distributed with VisIt yet? I<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">believe that was the intention.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Jose<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Wed, Jan 11, 2012 at 7:06 PM, Jose Fiestas Iquira <<a href="mailto:jafiestas@lbl.gov">jafiestas@lbl.gov</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks to Erik for advise. ETK example simulation run successfully.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Wed, Jan 11, 2012 at 11:49 AM, Jose Fiestas Iquira <<a href="mailto:jafiestas@lbl.gov">jafiestas@lbl.gov</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Right, it looks good now:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">./simfactory/bin/sim list-simulations<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> static_tov [ACTIVE (RUNNING), restart 0000, job id 595490]<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Let see how it looks when it finishes. The example was set to 8 hours.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Jose<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Wed, Jan 11, 2012 at 11:45 AM, Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu">schnetter@cct.lsu.edu</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Wed, Jan 11, 2012 at 2:42 PM, Jose Fiestas Iquira <<a href="mailto:jafiestas@lbl.gov">jafiestas@lbl.gov</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The only thing is that now<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">$ ./simfactory/bin/sim list-simulations<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">returns<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Error: unknown command list-simulation<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Aborting Simfactory.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Did you really type "list-simulations", and the error message says<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">"list-simulation" (without the final "s")?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-erik<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu">schnetter@cct.lsu.edu</a>> <a href="http://www.cct.lsu.edu/~eschnett/">http://www.cct.lsu.edu/~eschnett/</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Users mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="http://lists.einsteintoolkit.org/mailman/listinfo/users">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Ian Hinder<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="http://numrel.aei.mpg.de/people/hinder">http://numrel.aei.mpg.de/people/hinder</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Ian Hinder<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="http://numrel.aei.mpg.de/people/hinder">http://numrel.aei.mpg.de/people/hinder</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><qc0-mclachlan.err><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--<br></blockquote><blockquote type="cite">Ian Hinder<br></blockquote><blockquote type="cite"><a href="http://numrel.aei.mpg.de/people/hinder">http://numrel.aei.mpg.de/people/hinder</a><br></blockquote><blockquote type="cite"><br></blockquote><span><qc0-mclachlan.out></span></div></blockquote></div><br><div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 12px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>-- </div><div>Ian Hinder</div><div><a href="http://numrel.aei.mpg.de/people/hinder">http://numrel.aei.mpg.de/people/hinder</a></div></div></span></div></span></div>
</div>
<br></body></html>