Trac May 2012

trac@lists.einsteintoolkit.org

2 participants
239 discussions

[Einstein Toolkit] #902: carpetioascii with compact_format writes wrong set of columns
by Einstein Toolkit 11 Oct '12

11 Oct '12

#902: carpetioascii with compact_format writes wrong set of columns ---------------------------+------------------------------------------------ Reporter: rhaas | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: carpetioascii | ---------------------------+------------------------------------------------ For 0d output (in my case systemstatistics data) I get: {{{ # SYSTEMSTATISTICS::PROCESS_MEMORY_MB (systemstatistics::process_memory_mb) # # column format: 1:it 2:ix 3:time 4:x 5:data # data columns: 5:maxrss_mb 6:majflt_mb 7:arena_mb 8:ordblks_mb 9:hblks_mb 10:hblkhd_mb 11:uordblks_mb 12:fordblks_mb 13:keepcost_mb 14:swap_used_mb 3840 0 5.76 4956 23 628 0 0 651 -1189 1818 17 0 4096 0 6.144 5100 23 726 0 0 651 -1188 1915 21 0 }}} Note that the headers claim 14 columns but counting them, there are only 13 columns. From the look of it the "x" column is absent (since 4956 makes sense for being MB of memory used and 5.76 is clearly the time) -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/902> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #720: check at runtime that all REQUIREd and OPTIONAL thorns and capabilities are active
by Einstein Toolkit 19 Sep '12

19 Sep '12

#720: check at runtime that all REQUIREd and OPTIONAL thorns and capabilities are active -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- This is an offshot of a discussion on the Cactus developers mailing list: http://cactuscode.org/pipermail/developers/2011-November/006258.html On 6 Jan 2012 12:54:13 -0500 eschnett said: > What is currently missing is the mechanism that checks that all thorns > providing required capabilities are activated. If they are not, code > in inactive thorns is called -- this is fine as long as no Cactus > infrastructure is used (parameters, scheduled routines, grid > functions, etc.). > > Yes, we should implement the respective checks; yes, we should > automatically activate thorns required for capabilities (and maybe > some others as well?); yes, we should then output this thorn list to > the screen (done anyway) and into a file. > > By the way, Cactus already determines which thorns need to be > activated automatically as a service to the user in the error message > that complains about missing thorns. The idea seems to be to document all thorns whose code is executed in the parameter file. Ian's original need might be served by an "OPTIONAL" statement in configuration.ccl (http://einsteintoolkit.org/documentation/UsersGuide/UsersGuidech12.html#x17…) and some #ifdefs, maybe. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/720> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #929: GRHydro_test_tov_ppm_ML fails intermittently
by Einstein Toolkit 19 Sep '12

19 Sep '12

#929: GRHydro_test_tov_ppm_ML fails intermittently -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: GRHydro | -----------------------------------+---------------------------------------- The test GRHydro_test_tov_ppm_ML sometimes fails on Datura. This seems to be nondeterministic. The most recent occurrence of this (http://git.barrywardell.net/EinsteinToolkitTestResults.git/blob/0fed62edfcc…) is due to differences in the constraints and vel[0]_norm1.xg very close to the tolerance. This does not happen every time. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/929> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #762: support git-svn repositories
by Einstein Toolkit 17 Sep '12

17 Sep '12

#762: support git-svn repositories ---------------------------+------------------------------------------------ Reporter: rhaas | Owner: eric9 Type: enhancement | Status: new Priority: optional | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ I have a number of svn repositories that are each wrapped within a git-svn checkout (to more easily handle local modifications). It would be nice to have GetComponents handle these for me in the same way it already handles svn and git repositories. With git-svn checkouts are {{{git svn clone URL DIR}}}, updates are {{{git svn rebase}}}, diff is {{{git diff remotes/git-svn}}} and local changes have to be stashed the way they are with git. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/762> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #832: ExternalLibraries/zlib gives bad error message if "patch" is not available
by Einstein Toolkit 16 Sep '12

16 Sep '12

#832: ExternalLibraries/zlib gives bad error message if "patch" is not available -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- The PATCH variable is used in the zlib configuration script but there is no check that it has been set. It is also not declared in the configuration.ccl as being used. Should all environment variables used in the script be declared? PATCH is usually set by autoconf, unless it is unavailable, in which case it is not set. Replacing $PATCH with ${PATCH?} would be enough to give a sensible error message. I don't know if there are versions of bash that would not understand this. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/832> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #895: PITTNullCode does not work with Devel AEILocalInterp
by Einstein Toolkit 13 Sep '12

13 Sep '12

#895: PITTNullCode does not work with Devel AEILocalInterp ---------------------------------+------------------------------------------ Reporter: yosef@… | Type: defect Status: new | Priority: major Milestone: | Component: EinsteinToolkit thorn Version: | Keywords: CCE complex interpolation ---------------------------------+------------------------------------------ The CCE testsuite fails in the development version of ET. The interpolation calls in NullNews fail with the error WARNING[L1,P0] (AEILocalInterp): CCTK_InterpLocalUniform(): input datatype 111 not supported! (0-origin) input #in=0 The interpolation call is for a variable of type CCTK_VARIABLE_COMPLEX. The call works with the Maxwell version of AEILocalInterp -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/895> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #745: the flesh allows two implemantion of the same interface to have different default values for restricted parameters
by Einstein Toolkit 05 Sep '12

05 Sep '12

#745: the flesh allows two implemantion of the same interface to have different default values for restricted parameters --------------------+------------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | --------------------+------------------------------------------------------- since the flesh creates paramters for all compiled in (rather than activated) thorns initially, this affects the default value that a thorn sees. Thorns seem to be initialized (and thus their parameter structures being created) in alphabetical order, which means that the thorn alphabetically '''last''' (How, I have no idea, the parameter handling logic seems a bit of a mess) will determine the default parameter value. Attached is a parameter file to demonstrate this with Carpet and PUGH who both declare parameters periodic and periodic_[xyz] but differ in their defaults. To demonstrate, create an executable with only Carpet compiled in and run the parameter file. Then look at the paramters in the checkpoint it creates eg. {{{ h5dump -r -d /Parameters\ and\ Global\ Attributes/All\ Parameters output/checkpoint.chkpt.it_0.h5 | grep periodic }}} Do the same with an executable that contains both PUGH and Carpet. Notice that parameter values are now PUGH's defaults. This can actually cause a runs to abort when recovering from a checkpoint when one switches from an executable with PUGH compiled in to one that does not. (Beyond the fact that some thorn might actually use it's parameters rather than the Carpet/PUGH pair where happily Carpet ignores these parameters and PUGH who actually used them gets to set the default). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/745> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

[Einstein Toolkit] #669: Rewrite users of deprecated HDF5 C++ API
by Einstein Toolkit 04 Sep '12

04 Sep '12

#669: Rewrite users of deprecated HDF5 C++ API ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: task | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | ----------------------+----------------------------------------------------- The C++ API for HDF5 is decprecated. We should examine which code uses it, and rewrite it to use the C API instead. This would allow us to use more system-provided HDF5 installations. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/669> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

[Einstein Toolkit] #788: Produce movie about history of Einstein Toolkit
by Einstein Toolkit 17 Aug '12

17 Aug '12

#788: Produce movie about history of Einstein Toolkit ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: task | Status: new Priority: optional | Milestone: Component: Other | Version: Keywords: | ----------------------+----------------------------------------------------- Do this <https://www.youtube.com/watch?v=ZEAlhVOZ8qQ> for the Einstein Toolkit. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/788> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #934: Cannot check out ET release
by Einstein Toolkit 15 Aug '12

15 Aug '12

#934: Cannot check out ET release ---------------------------+------------------------------------------------ Reporter: eschnett | Owner: eric9 Type: defect | Status: new Priority: blocker | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ When I try to check out the release branch of the ET, GetComponents fails for all git repositories, and only for these. It appears that these repositories are checked out, but are on their master branch, and GetComponents cannot switch to the release branch. These repositories are then renamed, e.g. to "CRL.branch.failed". The error messages (taken from crl.log) are: {{{ May 29 11:05:08 2012: Could not checkout EinsteinExact/doc, unable to switch to branch ET_2012_05. Any existing symlinks to EinsteinExact/doc will be broken May 29 11:08:05 2012: Could not checkout KrancNumericalTools/GenericFD, unable to switch to branch ET_2012_05. Any existing symlinks to KrancNumericalTools/GenericFD will be broken May 29 11:08:11 2012: Could not checkout McLachlan/doc, unable to switch to branch ET_2012_05. Any existing symlinks to McLachlan/doc will be broken May 29 11:09:47 2012: Could not checkout GetComponents, unable to switch to branch ET_2012_05. Any existing symlinks to GetComponents will be broken May 29 11:09:47 2012: 4 errors occurred during update from thornlist(s): http://svn.einsteintoolkit.org/manifest/branches/ET_2012_05/einsteintoolkit… }}} This is on Mac OSX. I am using git version 1.7.10.2. I obtain GetComponents via {{{ wget --no-check-certificate https://github.com/gridaphobe/CRL/raw/ET_2012_05/GetComponents }}} and run it as {{{ ./GetComponents -a http://svn.einsteintoolkit.org/manifest/branches/ET_2012_05/einsteintoolkit… }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/934> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 12

← Newer
1
...
7
8
9
10
11
12
13
...
24
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac May 2012