Trac October 2011

trac@lists.einsteintoolkit.org

1 participants
179 discussions

[Einstein Toolkit] #617: Norm of NxNx1 grid gives poison in new version of Carpet
by Einstein Toolkit 27 Jan '12

27 Jan '12

#617: Norm of NxNx1 grid gives poison in new version of Carpet ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: regression | ------------------------+--------------------------------------------------- I am having a problem with a 2D Carpet unigrid simulation with NxNx1 grid points in each direction. I have 0 boundary points and 0 ghost points in the z direction. The norm2 and other norms computed by CarpetIOBasic and CarpetIOScalar are showing poison. The same happens if I use one boundary point and one ghost point. The important feature is that zmin = zmax. If I make zmax = zmin + dz, then the norms are fine. This works fine in the git version of Carpet - it seems to be a regression in the Mercurial version. Parameter file is attached. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/617> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #592: simfactory --mdbkey syntax is horrible
by Einstein Toolkit 20 Dec '11

20 Dec '11

#592: simfactory --mdbkey syntax is horrible --------------------+------------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | --------------------+------------------------------------------------------- apparently simfactory requires me to do: {{{ sim --mdbkey=optionlist my-very-own-option-list --thornlist=einsteintoolkit.th }}} to overwrite mdb entries from the command line (and --define --substitue --replace --append --mdbkey). I have to admit I would not have guessed that from the help text which states: {{{ options: -h, --help show this help message and exit --define=DEFINE set additional definition --mdbkey=MDBKEY override an mdb key }}} I would like to suggest to either change the help text to {{{ --mdbkey=MDBKEY MDBVALUE }}} or to support something like {{{ --mdbkey="MDBKEY=VALUE" }}} with or without quotation marks instead maybe. Is there a full documented list of valid mdb entries somewhere? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/592> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #523: schedule MoL_DecrementCounter and friends BEFORE MoL_PostStepModify
by Einstein Toolkit 20 Dec '11

20 Dec '11

#523: schedule MoL_DecrementCounter and friends BEFORE MoL_PostStepModify --------------------+------------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | --------------------+------------------------------------------------------- right now MoL_DecrementCounter (and MoL_ResetTime and MoL_ResetDeltaTime) is/are scheduled BEFORE MoL_PostStep which caused MoL_PostStepModify to run before MoL_DecrementCounter for me. The means that routines that are moved from MoL_PostStep to MoL_PostStepModify see a different MoL_IntermediateStep possibly confusing users. Also MoL_Add should be explicitly schedules before MoL_PostStepModify (again right now it says MoL_PostStep). It still ends up before due to the alphabetic sorting it seems. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/523> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #66: IOHDF5::out3D_ghosts and friends doesn't work and corrupts 2D data slices
by Einstein Toolkit 20 Dec '11

20 Dec '11

#66: IOHDF5::out3D_ghosts and friends doesn't work and corrupts 2D data slices ----------------------------------+----------------------------------------- Reporter: bcmsma@… | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | ----------------------------------+----------------------------------------- While the assigned values for the parameters IOASCII::output_symmetry_points = "no" IOASCII::out3D_ghosts = "no" IOASCII::out3D_outer_ghosts = "no" work as intended when CarpetIOASCII is active, it doesn't work for CarpetIOHDF5: IOHDF5::out3D_ghosts = "no" IOHDF5::out3D_outer_ghosts = "no" IOHDF5::output_symmetry_points = "no" It doesn't do anything to the 3D data but it corrupts the 2D data slices while chopping out those regions. It would be nice to have them working for IOHDF5 method, specially when visualising Pi symmetric data. Note also that this report is for git version of Carpet. These parameters seem to become deprecated for the hg version. Does anyone use them regularly? Any substitute in mind? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/66> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #527: Thorn Dissipation should have 9th order dissipation added
by Einstein Toolkit 16 Dec '11

16 Dec '11

#527: Thorn Dissipation should have 9th order dissipation added -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: Dissipation | -----------------------------------+---------------------------------------- The current standard in BBH evolutions is to use 8th order accurate finite differencing with 9th order accurate dissipation. Thorn Dissipation currently only supports up to 7th order accurate dissipation, and should be extended to support 9th order. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/527> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #578: Vectorize WeylScal4
by Einstein Toolkit 13 Dec '11

13 Dec '11

#578: Vectorize WeylScal4 -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Set UseVectors->True in WeylScal4. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/578> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #597: WeylScal4 should use the kranc script rather than calling Mathematica directly
by Einstein Toolkit 12 Dec '11

12 Dec '11

#597: WeylScal4 should use the kranc script rather than calling Mathematica directly -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: WeylScal4 testsuite | -----------------------------------+---------------------------------------- The attached patch makes WeylScal4 use the "kranc" script rather than calling Mathematica directly. This enables all the error-detection provided by Kranc and leads to tidier output. This patch can either be committed now or after the release. The files it touches are not used during use of WeylScal4, only during generation. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/597> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #645: Error concerning missing -V option when submitting job on LoneStar
by Einstein Toolkit 12 Dec '11

12 Dec '11

#645: Error concerning missing -V option when submitting job on LoneStar ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: ET_2011_10 Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- I used the following command to submit an ET testsuite job on LoneStar. The intention is to run on 1 process with 6 threads. sim --remote lonestar create-submit maxwell_1proc_2 --testsuite --procs 6 --num-threads 6 --walltime 4:00:00 --ppn-used 6 and got a weird error. SimFactory didn't report any error or return a nonzero exit code, even though it was unable to determine a job ID. I repeated the submission, and the second time it worked, so the fault appears to be intermittent. There was no difference in the submit script in each case, apart from the job name. The log file is attached, but the final error message from the log file is: {{{ [LOG:2011-10-22 11:29:05] self.submit(submitScript)::Executing submission command: qsub /scratch/00915/hinder/simulations/maxwell_1proc/output-0000/SIMFACTORY/SubmitScript [LOG:2011-10-22 11:29:05] self.makeActive()::Simulation maxwell_1proc with restart-id 0 has been made active [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::received raw output: Unable to run job: JSV rejected job. [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::Exiting. [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::----------------------------------------------------------------- [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::-- Welcome to the Lonestar4 Westmere/QDR IB Linux Cluster -- [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::----------------------------------------------------------------- [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::--> Checking that you specified -V... [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::--------------------------> Rejecting job <-------------------------- [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::-V is now a required option. Please specify it in your submit script. [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::--------------------------------------------------------------------- [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output):: [LOG:2011-10-22 11:29:06] job_id = self.extractJobId(output)::using submitRegex: Your job (\d+) $.*?$ has been submitted [LOG:2011-10-22 11:29:06] self.submit(submitScript)::After searching raw output, it was determined that the job_id is: -1 [LOG:2011-10-22 11:29:06] self.submit(submitScript)::If this is -1, that means the regex did NOT match anything. No job_id means no control. }}} Full log.txt file is attached. The job was not submitted. The weird thing is that I do have -V in my submission script. The file /scratch/00915/hinder/simulations/maxwell_1proc/output-0000/SIMFACTORY/SubmitScript has {{{ #! /bin/bash #$ -A TG-MCA02N014 #$ -q normal #$ -r n #$ -l h_rt=4:00:00 #$ -pe 1way 12 #$ #$ -V #$ -N maxwell_1proc-0 #$ -M ian.hinder(a)aei.mpg.de #$ -m abe #$ -o /scratch/00915/hinder/simulations/maxwell_1proc/output-0000/maxwell_1proc.out #$ -e /scratch/00915/hinder/simulations/maxwell_1proc/output-0000/maxwell_1proc.err cd /work/00915/hinder/Cactus/EinsteinToolkit /work/00915/hinder/Cactus/EinsteinToolkit/simfactory/bin/sim run maxwell_1proc --machine=lonestar --restart-id=0 }}} Any ideas? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/645> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #635: Cactus should print the number of processes used when running tests
by Einstein Toolkit 11 Dec '11

11 Dec '11

#635: Cactus should print the number of processes used when running tests -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- When running a test suite, it is usually important to know how many MPI processes are being used, as this determines which tests are run. This information is not currently present in the summary.log file, and is not output to standard output either. This makes it hard to check that simfactory is actually running a test on the expected number of processes. The attached patch outputs the number of processes to these two places. OK to apply before the release? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/635> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #223: Make declaration of CCTK_ARGUMENTS safer
by Einstein Toolkit 01 Dec '11

01 Dec '11

#223: Make declaration of CCTK_ARGUMENTS safer -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- I suggest to change the declaration of CCTK_ARGUMENTS in C from cGH * cctkGH to cGH const * CCTK_RESTRICT const cctkGH which should lead to safer code and may even enable some optimisations. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/223> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

← Newer
1
...
7
8
9
10
11
12
13
...
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