Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #465: Hydro_InitExcision test cases take a long time
by Einstein Toolkit 04 Aug '12

04 Aug '12

#465: Hydro_InitExcision test cases take a long time -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- I am just running all test cases with an executable without optimisation, and I find that Hydro_InitExcision takes a long time. While most other test cases finish in a few minutes, Hydro_InitExcision takes two hours to run. The test cases should be reduced in number, size, or duration. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/465> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #1012: trac patch display page should contain a download button
by Einstein Toolkit 03 Aug '12

03 Aug '12

#1012: trac patch display page should contain a download button ----------------------------------+----------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- the marked up patches that Trac shows (eg on https://trac.einsteintoolkit.org/attachment/ticket/1003/0003-GRHydro-add- routines-to-access-CarpetEvolutionMask-e.patch) should offer an option to download the "raw" patch. Ie. the same as the download button on the main ticket page. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1012> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1010: ExternalLibraries/MPI should check that MPI_DIR points to a valid directory
by Einstein Toolkit 03 Aug '12

03 Aug '12

#1010: ExternalLibraries/MPI should check that MPI_DIR points to a valid directory -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- The MPI thorn currently does not check that MPI_DIR points to a valid directory. The attached patch fixes this and also prints a message containing the (possibly inferred) location of the MPI installation. OK to apply? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1010> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1007: Improve flesh MPI configuration messages
by Einstein Toolkit 03 Aug '12

03 Aug '12

#1007: Improve flesh MPI configuration messages -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- When using ExternalLibraries/MPI, the flesh prints the message "Configuring without MPI" because the flesh MPI support is not being used. This could be confusing. The attached patch changes the messages to read Configuring with flesh MPI Warning: use of flesh MPI via MPI option is deprecated and should be replaced with the thorn ExternalLibraries/MPI and its MPI_DIR option when the flesh MPI is being used, and Configuring without flesh MPI support (MPI may be provided by a thorn) when it is not. OK to apply? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1007> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #998: The --define option does not work
by Einstein Toolkit 03 Aug '12

03 Aug '12

#998: The --define option does not work ---------------------+------------------------------------------------------ Reporter: alibeck | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Other | Version: Keywords: | ---------------------+------------------------------------------------------ At a simfactory call it should be possible to define a value of a variable by setting --define VAR=NEWVALUE Them the variable @VAR@ in a run- or submitscript should be expanded to NEWVALUE. Using define a shown above leads to the error: [snip] sim.py: error: --define option requires 2 arguments [snip] So I have tried also --define VAR NEWVALUE Using this --define in this way, the submission is successful, however @VAR@ is never evaluated by simfactory, so in the submit- and runscript @VAR@ instead of NEWVALUE can still be found. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/998> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1005: update list of publications on ET website
by Einstein Toolkit 03 Aug '12

03 Aug '12

#1005: update list of publications on ET website -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: task | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- * list of publications using ET (http://einsteintoolkit.org/publications/) is out of date * would like either automated system to collect papers based on whether the reference the ET paper or that extracts specially tagged entries from master bibtext file at https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.bib * poll authors regularly (3months interval) to report new papers on the users list * we have a list of all Cactus-using papers in the CIGR renewal grant proposal (the citeUS entries). See http://www.tapir.caltech.edu/~rhaas/cactususers.bib * need volunteer to collect information, produce web-page -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1005> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #1000: mistake in Cactus documentation
by Einstein Toolkit 02 Aug '12

02 Aug '12

#1000: mistake in Cactus documentation -----------------------+---------------------------------------------------- Reporter: anonymous | Type: task Status: new | Priority: minor Milestone: | Component: Other Version: | Keywords: mistake in documentation -----------------------+---------------------------------------------------- Revision : 4846 A152/A271 of the ReferenceManual has a trivial mistake: when describing CCTK_LocalArrayReductionHandle it says: Synopsys int handle = CCTK_ReduceLocalArrays(const char *operator); -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1000> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #839: MoL Multirate capabilities. This add three new multirate RK schemes to MoL.
by Einstein Toolkit 02 Aug '12

02 Aug '12

#839: MoL Multirate capabilities. This add three new multirate RK schemes to MoL. ----------------------------------------+----------------------------------- Reporter: reisswig@… | Type: enhancement Status: new | Priority: optional Milestone: | Component: Cactus Version: | Keywords: MoL Multirate ----------------------------------------+----------------------------------- In order to make multirate work, we need to introduce new registration routines that explicitly register variables with the "slow" sector, i.e. those variables which are integrated by the lower order scheme. This also means that we require new "accumulator" parameters indicating how many "slow" variables we want to register. Flags indicate whether it is time to execute slow RHS computation. For instance, in the RK4-RK2 scheme, there are 4 substeps in total, but the RK2 RHS are only evaluated in the very first and in the very last step of the four substeps. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/839> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 15

[Einstein Toolkit] #550: CarpetIOHDF5 too verbose while reading from checkpoint
by Einstein Toolkit 02 Aug '12

02 Aug '12

#550: CarpetIOHDF5 too verbose while reading from checkpoint -------------------------+-------------------------------------------------- Reporter: knarf | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- It is not that uncommon that I recover using a different number of processors. Every time I do this I see the error file cluttered with messages like WARNING level 1 in thorn CarpetIOHDF5 processor 21 host c312-313.ls4.tacc.utexas.edu (line 640 of /work/00920/tg459479/Cactus/arrangements/Carpet/CarpetIOHDF5/src/Input.cc): -> Variable AHFINDERDIRECT::ahmask on rl 0 and tl 0 not read completely. Will have to look for it in other files I expect this, this is not an error and not really something to warn about. I acknowledge that this might have been introduced when recovering using the same number of processors was a problem and caused reading all files, but I don't think this is an issue anymore. I propose to change the warnlevel for this message to CCTK_WARN_DEBUG(4). In addition it would be good to have _one_ separate message with level CCTK_WARN_PICKY(3) if any variable/reflevel/timelevel could not be read completely (but not one for each of these), ideally only once for all processors. This would not clutter the output of the default simfactory runs (-L 3) too much, but would indicate that this happened - and in case this is a problem it's easy to enable -L 4. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/550> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

[Einstein Toolkit] #996: change default values of PUGH's periodic parameters to "no"
by Einstein Toolkit 02 Aug '12

02 Aug '12

#996: change default values of PUGH's periodic parameters to "no" -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: PUGH | -----------------------------------+---------------------------------------- Right now the default values between Carpet and PUGH (who both implement) "Driver" differ (see #745). Since they should not (for reasons that it prevents users from easily switching from one to the other and because the current Cactus implementation has a bug when handling this case) and because Carpet (which does not even support periodic boundary conditions in this manner) is by far the more common driver in production simulations I would like to change the defaults. Users who actually use PUGH and use its periodic boundary condition without setting the periodic parameters please speak up. Ideally one would precede the change of defaults with an announcement to the mailing list and maybe even spread it over two ET releases. It should be done though (and #745 ought to be fixed). Otherwise other users might have to experience the joy of having to wait for a day for a test run on a busy cluster only to have it fail due to Carpet complaining about the periodic Parameters being set (since the debug executable had PUGH compiled in but the one to generate the checkpoints I was investigating had not). Fixing #745 would solve the problem of mysterious error messages aborting runs but would still leave two implementations with different default parameter values. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/996> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac