Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #1733: Certificate on jenkins web server has expired
by Einstein Toolkit 26 Jan '15

26 Jan '15

#1733: Certificate on jenkins web server has expired -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Server Infrastructure | Version: development version Keywords: | -----------------------------------+---------------------------------------- The certificate on https://build.barrywardell.net has expired. There were problems with the renewal process at StartSSL. We are aware of the issue and are looking into a solution. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1733> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1694: try using fast fowards when accepting pull requests
by Einstein Toolkit 26 Jan '15

26 Jan '15

#1694: try using fast fowards when accepting pull requests -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: optional | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- For small single change pull requests have a full git merge in the history can be annoying since it clutter the history view (it uses up two lines, it may show connecting both branches existing at the same time even if there are no commits on master during that time). We could try and instead find out if bitbucket can be made to allow fast forwards in the pull request merge (https://bitbucket.org/site/master/issue/6106/forced-non-fast-forward- merge-of-pull). Currently apparently bitbucket uses --no-ff ie it disallows fast forwards. We could even think about forcing fast forwards only (https://bitbucket.org/site/master/issue/9589/force-fast-forward-only- merges-on-pull). This does however not work so well for big "feature" branches that are brought back into master and where a fast forward may fail and/or require extensive rebasing of the feature branch. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1694> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #1741: PAPI defines global functions and variables without PAPI_ prefix
by Einstein Toolkit 22 Jan '15

22 Jan '15

#1741: PAPI defines global functions and variables without PAPI_ prefix -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: PAPI | -----------------------------------+---------------------------------------- In its stats.c source file (which gets compiled into the thorn), PAPI defines several globally visible symbols, eg: {{{ void outinfo(const char *const function) ... int num_threads; }}} which are not prefixed with the thorn name so possibly conflict with other thorns. According to the Cactus user guide http://einsteintoolkit.org/documentation/UsersGuide/UsersGuidech9.html#x13-… users are suggested to prefix them by the thorn name (or put into a C++ namespace) to avoid conflicts. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1741> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1740: GRHydro ReconstructPolytype.F90 passes wrong arguments to SimplePPM(M)_1d
by Einstein Toolkit 21 Jan '15

21 Jan '15

#1740: GRHydro ReconstructPolytype.F90 passes wrong arguments to SimplePPM(M)_1d -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: knarf Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: GRHydro | -----------------------------------+---------------------------------------- Zach Etienne found (last year on August already) that > In GRHydro_ReconstructPoly.F90, notice that after gzz in the SimplePPM_1d() > and SimplePPM_1dM() function calls, psi4 is passed. However, if you look at > the SimplePPM_1d() and SimplePPM_1dM() routines (within GRHydro_PPM.F90), > you will find that psi4 is not a variable in the function call list, and > beta^i should come after gzz, for flux_direction i. Pull request https://bitbucket.org/einsteintoolkit/einsteinevolve/pull- request/6/fix-usage-of-psi4-in-polytype/diff fixes this. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1740> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1663: VisIT CarpetHDF5 plugin pseudocolor error
by Einstein Toolkit 20 Jan '15

20 Jan '15

#1663: VisIT CarpetHDF5 plugin pseudocolor error ---------------------------------------+------------------------------------ Reporter: bruno.giacomazzo@… | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Other | Version: development version Keywords: visit | ---------------------------------------+------------------------------------ This problem has been present since the CarpetHDF5 plugin for VisIt became part of the standard VisIt distribution and it is still present in the current version of VisIt (2.8). When Pseudocolor is used in log scale and Centering is set to Original or Nodal, not all the values of the plotted quantity are shown (in particular lower values are not plotted at all). This does not happen if one sets Centering to Zonal, which instead shows the correct values. I have attached a couple of images showing the problem (they show hydrobase::rho for a BNS run). I do not know what may be causing it, but it may cause serious errors when analyzing data with VisIt (since one may miss some of the information on the low value regions). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1663> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1635: hwloc requires a certain minimum version, but does not check for it
by Einstein Toolkit 20 Jan '15

20 Jan '15

#1635: hwloc requires a certain minimum version, but does not check for it --------------------+------------------------------------------------------- Reporter: knarf | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2014_11 Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- Currently, hwloc's configuration.sh searched for any hwloc library and uses it. However, it requires a pretty new version within some of its own files, which leads to build failure on, e.g. Debian stable systems. The attached patch uses pkg-config to get the version of the installed hwloc library and if that version is older than 1.6 (educated guess, but see http://lists.einsteintoolkit.org/pipermail/users/2013-February/002860.html), builds the bundled version even if another version is installed (but too old). Note that this is done (intentionally) only if no library was specified, and the script was looking for it by itself. This allows users to specify something which will not be overwritten by this mechanism. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1635> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 14

[Einstein Toolkit] #1704: redirect stdout and stderr of all processes if requested (also of the root process)
by Einstein Toolkit 19 Jan '15

19 Jan '15

#1704: redirect stdout and stderr of all processes if requested (also of the root process) -------------------------+-------------------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Currently Cactus only redirects, when asked, stdout and stderr to files for processes other than the root process. The patch lets Cactus also write stdout and stderr for the root process. https://bitbucket.org/cactuscode/cactus/pull-request/2/redirect-stdout- and-stderr-of-all/diff -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1704> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #1738: Update requirements documentation for Cactus
by Einstein Toolkit 16 Jan '15

16 Jan '15

#1738: Update requirements documentation for Cactus ---------------------------+------------------------------------------------ Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: documentation | ---------------------------+------------------------------------------------ The Cactus User Guide has a section "Required software" which lists the software needed for Cactus. I think this should list the various language versions which are needed. For example, we could say (if this is the case) that Cactus requires C99 and C++98 or later. The page probably also should be updated to replace SVN with Git. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1738> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1702: AEILocalInterp and LocalInterp should output scheduled function name in error messages
by Einstein Toolkit 15 Jan '15

15 Jan '15

#1702: AEILocalInterp and LocalInterp should output scheduled function name in error messages ----------------------------------------------------------------+----------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: AEILocalInterl LocalInterp CarpetInterp PUGHInterp | ----------------------------------------------------------------+----------- the local interpolation routines abort if an interpolation cannot be performed since the interpolation coordinates lie outside of the patch of data they are given eg. {{{ WARNING level 1 in thorn AEILocalInterp processor 0 (line 1109 of arrangements/AEIThorns/AEILocalInterp/src/Lagrange-tensor- product/../template.c): -> CCTK_InterpLocalUniform(): interpolation point is either outside the grid, or inside but too close to the grid boundary! (this may be caused by a global interpolation with driver::ghost_size too small) 0-origin interpolation point number pt=54181 of N_interp_points=54182 interpolation point (x,y,z)=(45.3992,15.5856,2.93915e-15) grid x_min(delta_x)x_max = -0.198(0.066)1.584 grid y_min(delta_y)y_max = -0.198(0.066)1.518 grid z_min(delta_z)z_max = -0.198(0.066)1.452 }}} However, if there are mutliple thorns that may call the interpolator it is no always clear which caller was active when the error occured (eg it may be the apparent horizon finder or the puncture tracker). It would be nice if the interpolators were to report the currently executing scheduled routine's name via CCTK_ScheduleQueryCurrentFunction. That routine currently takes cctkGH as an argument but does not actually use it. Thus, given the possible benefit, it would be acceptable I think to call the routine with a NULL pointer (and a comment that this is strictly not valid). An alternative, which may be nicer, would be to have the driver add an entry "cctkGH" to the table passed to {{{CCTK_InterpLocalUniform}}} in its {{{param_table_handle}}}. The local interpolator can then savely use this pointer if provided and (with an appropriate loud warning) fall back to passing NULL if it is not found (and stop the fallback once the flesh routine actually uses cctkGH). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1702> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1728: Remove CACHE_SIZE etc. from configure
by Einstein Toolkit 15 Jan '15

15 Jan '15

#1728: Remove CACHE_SIZE etc. from configure -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Configure cannot reliably detect CACHE_SIZE since this may be different on build nodes and compute nodes. Thorn hwloc provides a reliable, portable run-time solution. CACHE_SIZE is not currently used either. I suggest to remove it from configure. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1728> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac