Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #439: Job Chaining
by Einstein Toolkit 23 May '11

23 May '11

#439: Job Chaining ---------------------------+------------------------------------------------ Reporter: barry.wardell | Owner: mthomas Type: defect | Status: new Priority: blocker | Milestone: Component: SimFactory | Version: Keywords: job chaining | ---------------------------+------------------------------------------------ Currently job chaining only works with the first chained job. Subsequent chained jobs are incorrectly set to depend on the current active restart rather than the last queued restart. The attached patch fixes the problem, although I'm not sure if it's the correct approach. It just looks for the largest restart ID (without checking if that restart is in the queue) and sets the new job to depend on that. What is the 'correct' behavior in this situation? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/439> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

Re: [ET Trac] [Einstein Toolkit] #437: Correct autoconfiguration of restrict keyword; add support for builtin_expect
by Einstein Toolkit 23 May '11

23 May '11

#437: Correct autoconfiguration of restrict keyword; add support for builtin_expect -----------------------------------------------------+---------------------- Reporter: Erik Schnetter <schnetter@…> | Owner: Type: defect | Status: review Priority: minor | Milestone: Component: Cactus | Version: Resolution: | Keywords: -----------------------------------------------------+---------------------- Changes (by eschnett): * status: new => review -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/437#comment:2> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

Re: [ET Trac] [Einstein Toolkit] #437: Correct autoconfiguration of restrict keyword; add support for builtin_expect
by Einstein Toolkit 23 May '11

23 May '11

#437: Correct autoconfiguration of restrict keyword; add support for builtin_expect -----------------------------------------------------+---------------------- Reporter: Erik Schnetter <schnetter@…> | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Resolution: | Keywords: -----------------------------------------------------+---------------------- Changes (by eschnett): * reporter: anonymous => Erik Schnetter <schnetter@…> -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/437#comment:1> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #437: Correct autoconfiguration of restrict keyword; add support for builtin_expect
by Einstein Toolkit 23 May '11

23 May '11

#437: Correct autoconfiguration of restrict keyword; add support for builtin_expect -----------------------+---------------------------------------------------- Reporter: anonymous | Type: defect Status: new | Priority: minor Milestone: | Component: Cactus Version: | Keywords: -----------------------+---------------------------------------------------- While experimenting with several different compilers on Hopper, I noticed that some compilers do not support all the ways in which the "restrict" keyword can be used. I updated our autoconf macro to test more cases. I now also think it is not worthwhile to require the compiler to support the array syntax for function arguments, i.e. the syntax void foo (double A[restrict]); which (essentially) declares a pointer A using array syntax. One can instead use the syntax void foo (double *restrict const A); which is identical in almost all respects. The PGI compiler does not seem to support the array syntax, and disabling support for the restrict keyword does not seem to be worth the cost. I also add support for the gcc built-in function "builtin_expect", which tells the compiler the value that an expression is most likely to have, allowing compile-time optimisations based on this heuristic, and maybe avoiding branch penalties at run time. I also enabled the (currently commented out) definitions for attribute(hot) and attribute(cold), which tell the compiler that a function is either executed very often, or very rarely. This can also influence the optimiser. I attach a patch. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/437> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #328: TRAC frequently logs users out
by Einstein Toolkit 19 May '11

19 May '11

#328: TRAC frequently logs users out ----------------------------------+----------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- There seems to be some mechanism which is automatically logging users out of TRAC. This means that they end up posting as "anonymous" because they don't realise they are logged out. Probably there is a session cookie which expires or something. To avoid this, we could either try to change the logout (I would be happy if the automatic logout was just disabled completely), or make it much more obvious when you are not logged in. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/328> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #385: No link to wiki
by Einstein Toolkit 18 May '11

18 May '11

#385: No link to wiki -------------------------------------+-------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- There is no (obvious) link to the wiki on the Einstein Toolkit web site. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/385> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #348: https://docs.einsteintoolkit.org/ does not redirect to the docs page
by Einstein Toolkit 18 May '11

18 May '11

#348: https://docs.einsteintoolkit.org/ does not redirect to the docs page -------------------------------------+-------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: docs | -------------------------------------+-------------------------------------- When I go to https://docs.einsteintoolkit.org/ it takes me to the list of CCT wikis. Based on the hostname, it should redirect to the correct page automatically. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/348> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #433: GetComponents to report updated components
by Einstein Toolkit 11 May '11

11 May '11

#433: GetComponents to report updated components ---------------------------------------+------------------------------------ Reporter: baiotti@… | Owner: eric9 Type: enhancement | Status: new Priority: optional | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------------------+------------------------------------ I think it would be useful if "GetCompontents --update" reported which components and which files have been actually updated (they are usually a few, if one updates periodically). This can be achieved with the --verbose option, but then the output is larger than needed, I think. The current version (with the --version option) outputs, for example: Updating module: LSUThorns/SummationByParts from repository: https://svn.cct.lsu.edu/repos/numrel/LSUThorns/SummationByParts/trunk located in: ./arrangements Executing: svn update --non-interactive In: ./arrangements/LSUThorns/SummationByParts U src/call_derivs2.c Updated to revision 127. I think that even without the --verbose option the lines Updating module: LSUThorns/SummationByParts U src/call_derivs2.c Updated to revision 127. should be output, while the lines from repository: https://svn.cct.lsu.edu/repos/numrel/LSUThorns/SummationByParts/trunk located in: ./arrangements Executing: svn update --non-interactive In: ./arrangements/LSUThorns/SummationByParts report information that is not usually needed (not to speak of the initial long ,info. stuff) and therefore should be output only if the --verbose option is invoked. In brief, I would like the output of GetComponents --update to be like Updating module: LSUThorns/SummationByParts U src/call_derivs2.c Updated to revision 127. Cheers, Luca -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/433> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #432: SummationByParts: typo in arguments of deriv2_mixed call.
by Einstein Toolkit 11 May '11

11 May '11

#432: SummationByParts: typo in arguments of deriv2_mixed call. ------------------------------------------+--------------------------------- Reporter: eloisa.bentivegna@… | Type: defect Status: new | Priority: major Milestone: | Component: EinsteinToolkit thorn Version: | Keywords: ------------------------------------------+--------------------------------- On line 85 of call_derivs2.c, the call CCTK_FNAME(deriv2_mixed)(&cctkGH_,&dir1,&dir2,var,&ni,&nk,&nk,dvar2,&table_handle); should be CCTK_FNAME(deriv2_mixed)(&cctkGH_,&dir1,&dir2,var,&ni,&nj,&nk,dvar2,&table_handle); -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/432> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #375: RotatingSymmetry*: Improve performance
by Einstein Toolkit 08 May '11

08 May '11

#375: RotatingSymmetry*: Improve performance -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- The attached patches depend on the new Slab API provided by ticket #374: Use the new Slab API to set up the communication schedule only once (per regridding), which saves some communication time when applying symmetries. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/375> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac