Trac August 2012

trac@lists.einsteintoolkit.org

1 participants
206 discussions

[Einstein Toolkit] #1022: GetComponents should recognise absolute path in --root
by Einstein Toolkit 08 Aug '12

08 Aug '12

#1022: GetComponents should recognise absolute path in --root ---------------------------+------------------------------------------------ Reporter: knarf | Owner: eric9 Type: defect | Status: new Priority: minor | Milestone: Component: GetComponents | Version: development version Keywords: | ---------------------------+------------------------------------------------ Currently GetComponents adds the current path to whatever is given in --root which then turns into something like: can't cd to /home/knarf/tmp//home/knarf/CactusLovelace/repos/EinsteinExact (wd is home/knarf/tmp/ and --root=/home/knarf was given). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1022> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #1018: Carpet should not require an MPI installation to work
by Einstein Toolkit 07 Aug '12

07 Aug '12

#1018: Carpet should not require an MPI installation to work -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: optional | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- Installing MPI could be a barrier to entry for new users, and PUGH is antiquated. There should be a way for new users to use Carpet for single- process runs without having to install MPI. There is a thorn NoMPI which provides a dummy MPI implementation which should be sufficient for Carpet to run. This thorn needs to be modified to fit in with the new MPI scheme. Specifically, it needs to provide an mpi.h file and the capability "MPI". -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1018> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #177: EXC_BAD_ACCESS in CarpetIOASCII
by Einstein Toolkit 06 Aug '12

06 Aug '12

#177: EXC_BAD_ACCESS in CarpetIOASCII --------------------+------------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | --------------------+------------------------------------------------------- I am trying to run a minimal parameter file for testing purposes (attached). Cactus gets as far as printing the iteration 0 info line and then appears to hang. When I run in a debugger, it reports: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 0x0000000100b858b7 in CarpetIOASCII::WriteASCII<0> (os=@0x7fff5fbfc5e0, gfdatas={<std::_Vector_base<const gdata *, std::allocator<const gdata *> >> = {_M_impl = {<allocator<const gdata *>> = {<__gnu_cxx::new_allocator<const gdata *>> = {<No data fields>}, <No data fields>}, _M_start = 0x109f0ea10, _M_finish = 0x109f0eab8, _M_end_of_storage = 0x109f0eab8}}, <No data fields>}, gfext=@0x7fff5fbfc960, vi=0, time=0, org=@0x7fff5fbfcafc, dirs=@0x7fff5fbfd150, rl=0, ml=0, m=0, c=0, tl=0, coord_time=0, coord_lower=@0x7fff5fbfc9d8, coord_upper=@0x7fff5fbfc9f0) at ioascii.cc:1378 1378 switch (vartype) { (gdb) bt #0 0x0000000100b858b7 in CarpetIOASCII::WriteASCII<0> (os=@0x7fff5fbfc5e0, gfdatas={<std::_Vector_base<const gdata *, std::allocator<const gdata *> >> = {_M_impl = {<allocator<const gdata *>> = {<__gnu_cxx::new_allocator<const gdata *>> = {<No data fields>}, <No data fields>}, _M_start = 0x109f0ea10, _M_finish = 0x109f0eab8, _M_end_of_storage = 0x109f0eab8}}, <No data fields>}, gfext=@0x7fff5fbfc960, vi=0, time=0, org=@0x7fff5fbfcafc, dirs=@0x7fff5fbfd150, rl=0, ml=0, m=0, c=0, tl=0, coord_time=0, coord_lower=@0x7fff5fbfc9d8, coord_upper=@0x7fff5fbfc9f0) at ioascii.cc:1378 #1 0x0000000100b5b7ee in CarpetIOASCII::IOASCII<0>::OutputDirection (cctkGH=0x109f073f0, vindex=0, alias={_M_dataplus = {<allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x10a06c1c8 "carpet::timing"}}, basefilename={_M_dataplus = {<allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x10a06ba68 "minimal/carpet::timing"}}, dirs=@0x7fff5fbfd150, is_new_file=true, truncate_file=true) at ioascii.cc:610 #2 0x0000000100b554c4 in CarpetIOASCII::IOASCII<0>::OutputVarAs (cctkGH=0x109f073f0, varname=0x10a06c170 "CARPET::physical_time_per_hour", alias=0x10a06be00 "carpet::timing") at ioascii.cc:480 #3 0x0000000100b57370 in CarpetIOASCII::IOASCII<0>::TriggerOutput (cctkGH=0x109f073f0, vindex=0) at ioascii.cc:359 #4 0x0000000100b542b7 in CarpetIOASCII::IOASCII<0>::OutputGH (cctkGH=0x109f073f0) at ioascii.cc:239 #5 0x000000010329a006 in Carpet::OutputGH (cctkGH=0x109f073f0) at OutputGH.cc:55 #6 0x0000000103293b25 in Carpet::OutputGH (where=0x104c70f3c "Initialise::CallAnalysis", cctkGH=0x109f073f0) at Initialise.cc:1382 #7 0x000000010328d432 in Carpet::CallAnalysis (cctkGH=0x109f073f0) at Initialise.cc:530 #8 0x00000001032892d4 in Carpet::Initialise (fc=0x7fff5fbfe2b0) at Initialise.cc:118 #9 0x000000010005806a in main (argc=4, argv=0x7fff5fbfe318) at flesh.cc:80 I do not see how this line "switch(vartype)" where vartype is declared on the stack, could lead to this error. This configuration has been rebuilt with -O0 (Intel compiler) and debugging enabled. This is with the current production (Git) version of Carpet running on Mac OS 10.6.5. The code is compiled as 64 bit. This parameter file has worked in the past, though with 32 bit on Mac OS 10.5. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/177> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #944: import outstanding Zelmani patches into ET trunk
by Einstein Toolkit 04 Aug '12

04 Aug '12

#944: import outstanding Zelmani patches into ET trunk -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: GRHydro | -----------------------------------+---------------------------------------- attached are all current outstanding differences between ET GRHydro and Zelmani GRHydro. I would like to flush them out into trunk. The only ones that do not work with current trunk are the Multirate ones (the last one) so those should be kept back until the MoL multirate issues are resolved. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/944> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac August 2012