Trac October 2011

trac@lists.einsteintoolkit.org

1 participants
179 discussions

[Einstein Toolkit] #458: Improve bboxset efficiency (e.g. for regridding)
by Einstein Toolkit 27 Oct '11

27 Oct '11

#458: Improve bboxset efficiency (e.g. for regridding) -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- The attached patch modifies the algorithm used to insert a new bbox into an existing bboxset. It reduces the computational complexity of this operation from O(n^2) to O(n), where n is the number of elements in the bboxset. This has the potential to speed up regridding significantly. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/458> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #611: Have Carpet print info about number of buffer zones
by Einstein Toolkit 27 Oct '11

27 Oct '11

#611: Have Carpet print info about number of buffer zones ---------------------------------------+------------------------------------ Reporter: baiotti@… | Owner: eschnett Type: enhancement | Status: new Priority: optional | Milestone: Component: Carpet | Version: Keywords: info buffer | ---------------------------------------+------------------------------------ I would like Carpet to print to stdout during initialization the number of buffer points used in the simulation. I attach a patch, written by Ian Hinder. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/611> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #329: SimFactory/ranger-intel11.cfg: Are BLAS and LAPACK compilations on Ranger optimized?
by Einstein Toolkit 27 Oct '11

27 Oct '11

#329: SimFactory/ranger-intel11.cfg: Are BLAS and LAPACK compilations on Ranger optimized? -------------------------+-------------------------------------------------- Reporter: bmundim | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- ranger-intel11.cfg now sets BLAS and LAPACK to be built along with the Cactus and other external libraries. Usually the host system BLAS and LAPACK are fine tuned to take advantage of the particular memory hierarchy of the host machine. I was wondering if this fine tuning is performed when we set BLAS = BUILD or LAPACK = BUILD, and, in case it is not, if it would be interesting to define Cactus env variables to set the size of the several cache memories for example and use it for this necessary fine tuning. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/329> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #604: LocalReduce: Initialize variables to avoid compiler warnings
by Einstein Toolkit 27 Oct '11

27 Oct '11

#604: LocalReduce: Initialize variables to avoid compiler warnings -------------------------+-------------------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- The following one-line change would initialize the inval variable, avoiding compiler warnings for almost all variable types. {{{ Index: local_reductions.h =================================================================== --- local_reductions.h (revision 86) +++ local_reductions.h (working copy) @@ -32,6 +32,7 @@ iter = 0; \ sum_indices = 0; \ num_points = 1; \ + REDUCTION_INITIAL(inval) \ REDUCTION_INITIAL( * outval) \ \ if ( N_dims == 0 ) \ }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/604> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #610: IDAnalyticBH: Smooth out singularities
by Einstein Toolkit 27 Oct '11

27 Oct '11

#610: IDAnalyticBH: Smooth out singularities -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- IDAnalyticBH has an "epsilon" parameter to smooth out singularites. This parameter should also be used in Brill-Lindquist initial data. Otherwise, moving puncture evolution of these data is not possible without an explicit smoothing step. {{{ Index: src/BrillLindquist.c =================================================================== --- src/BrillLindquist.c (revision 180) +++ src/BrillLindquist.c (working copy) @@ -143,7 +143,7 @@ tmp1 = sqrt(SQR(xval+hole_x0[n]) +SQR(yval+hole_y0[n]) +SQR(zval+hole_z0[n]) - +1.0e-20); + +SQR(epsilon)); psi[i] += hole_mass[n]/tmp1*0.5; }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/610> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #271: python simfactory submit creates only the SubmitScript
by Einstein Toolkit 27 Oct '11

27 Oct '11

#271: python simfactory submit creates only the SubmitScript ----------------------------------------------+----------------------------- Reporter: alexander.beck-ratzka@… | Type: defect Status: new | Priority: major Milestone: | Component: Other Version: | Keywords: simfactory submit ----------------------------------------------+----------------------------- The python version of simfactory submit creates only the submitScript called PreparedSubmitScript. The RunScript is created at the moment of the simfactory run call at the end of the SubmitScript. So a user has no possibilty to check whether his settings e.g. for mpirun have been correct or not for all the time where the job is only queued. I feel this is not a user friendly solution. The RunScript should be created together with the SubmitScript. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/271> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #326: Update gsl path in Ranger option file to gsl 1.13
by Einstein Toolkit 27 Oct '11

27 Oct '11

#326: Update gsl path in Ranger option file to gsl 1.13 ---------------------------------------------+------------------------------ Reporter: bmundim | Owner: mthomas Type: task | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: Ranger option configuration gsl | ---------------------------------------------+------------------------------ Ranger config file has been updated recently, so I thought to bring to your attention that gsl library on Ranger now defaults to version 1.13. Cheers, Bruno. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/326> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #327: Simfactory: ranger-intel11.run question.
by Einstein Toolkit 27 Oct '11

27 Oct '11

#327: Simfactory: ranger-intel11.run question. ------------------------+--------------------------------------------------- Reporter: bmundim | Owner: mthomas Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- Shouldn't we load intel/11.1 there, since the default on Ranger is intel/10.1? Also unless "module load intel/11.1" is in your .login_user, it will fail to "module load mvapich" since no compiler has been selected. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/327> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #472: Correct scheduling of TmunuBase's SetTmunu
by Einstein Toolkit 27 Oct '11

27 Oct '11

#472: Correct scheduling of TmunuBase's SetTmunu ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | ----------------------+----------------------------------------------------- I notice that TmunuBase doesn't schedule the group SetTmunu often enough. In particular, it is not scheduled after recovery, and it's scheduling at evol is also questionable. I also notice that GRHydro "fixes" this by scheduling SetTmunu by itself. This needs to be cleaned up. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/472> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #480: Problem with determining host name in SimFactory 1
by Einstein Toolkit 27 Oct '11

27 Oct '11

#480: Problem with determining host name in SimFactory 1 ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- On the new Scientific Linux 6 installation at the AEI, SimFactory 1 thinks that the local machine is called localhost.localdomain: $ simfactory/sim build --thornlist WaveToy.th --optionlist damiana_sl6.cfg Simulation Factory: Configuration name(s) not specified -- using default configuration "sim" Uncaught exception from user code: Unknown machine name "localhost.localdomain" at simfactory/sim line 5061. at simfactory/sim line 5061 main::get_machine('') called at simfactory/sim line 1498 main::command_build() called at simfactory/sim line 454 Looking at the code for get_hostnamealias, it appears to look for all the host name aliases of the current machine and select the first one in the returned list which contains a dot. On the workstation in question, I get: [ianhin@sl-18 ~]$ hostname -a localhost.localdomain localhost localhost6.localdomain6 localhost6 sl-18 sl-18.damiana.admin which explains the behaviour. My first reaction would be to filter the list to remove all the "local" aliases. This might break peoples' existing setup. I have seen mailing list posts which indicate that people use localhost as their machine name in simfactory. Since SimFactory 1 is approaching end-of-life, it might just be better to say that you need to use the --hostname option directly if you run into this problem, rather than breaking peoples' existing workflow. Thoughts? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/480> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

← Newer
1
...
11
12
13
14
15
16
17
18
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac October 2011