Trac October 2021

trac@lists.einsteintoolkit.org

1 participants
83 discussions

#2571: runtime failure due to useing character*8 in DECLARE_CCTK_ARGUMENTS_CHECKED macro
by Roland Haas 21 Oct '21

21 Oct '21

#2571: runtime failure due to useing character*8 in DECLARE_CCTK_ARGUMENTS_CHECKED macro Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: Cactus Comment (by Roland Haas): Something like this would work: ```fortran type inaccessible integer :: dummy end type type(inaccessible), intent(IN):: alp integer, parameter :: cctki_use_alp = kind(alp%dummy) ``` Trying to access it via eg `foo = alp` produces an error: > `Error: Cannot convert TYPE(inaccessible) to INTEGER(4) at (1)` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2571/runtime-failure-d…

1 0

#2571: runtime failure due to useing character*8 in DECLARE_CCTK_ARGUMENTS_CHECKED macro
by Roland Haas 21 Oct '21

21 Oct '21

#2571: runtime failure due to useing character*8 in DECLARE_CCTK_ARGUMENTS_CHECKED macro Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: Cactus Comment (by Roland Haas): Interesting. A `logical*8` would still be viable \(there is no bounds check for it\). I’d rather risk cases of grid scalars not being found \(read only at least, write access is caught due to `INTENT(IN)`\) than having lots of “unused actual argument” warnings. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2571/runtime-failure-d…

1 0

#2487: *_evolution_method = "LeanBSSNMoL" in Lean does nothing
by Roland Haas 21 Oct '21

21 Oct '21

#2487: *_evolution_method = "LeanBSSNMoL" in Lean does nothing Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Is there anything else that needs to be done for this ticket or can it be closed? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2487/_evolution_method…

1 0

#2565: compiling PETSc included in the ET fails if "python" executable is missing
by Roland Haas 21 Oct '21

21 Oct '21

#2565: compiling PETSc included in the ET fails if "python" executable is missing Reporter: Roland Haas Status: wontfix Milestone: Version: development version Type: bug Priority: major Component: Changes (by Roland Haas): status: wontfix (was new) Comment (by Roland Haas): There is nothing wrong with expecting "python" to exist. In fact there not being a "python" is wrong. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2565/compiling-petsc-i…

1 0

#2565: compiling PETSc included in the ET fails if "python" executable is missing
by Roland Haas 21 Oct '21

21 Oct '21

#2565: compiling PETSc included in the ET fails if "python" executable is missing Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: Comment (by Roland Haas): Updated packages to install as of git hash [0f6594f](https://github.com/nds-org/jupyter-et/commits/0f6594f3705cf559d13b… "CactusTutorial.ipynb: ask for Python3 rather than Python2" of [jupyter-et](https://github.com/nds-org/jupyter-et) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2565/compiling-petsc-i…

1 0

#2566: check for -traditional in FPP's behaviour
by Roland Haas 21 Oct '21

21 Oct '21

#2566: check for -traditional in FPP's behaviour Reporter: Status: wontfix Milestone: Version: development version Type: enhancement Priority: major Component: Changes (by Roland Haas): status: wontfix (was new) Comment (by Roland Haas): Actually Cactus itself contains such a check in `src/include/cctk_Types.h`: ``` /* Determine whether we have a traditional or an ANSI cpp. */ #ifdef FCODE /* The empty comment in the definition of CCTK_ANSI_FPP will either turn into nothing or into white space. There must not be any add spaces around this empty comment. A traditional cpp will turn it into nothing, an ANSI cpp will turn it into white space. Depending on this, CCTK_ANSI_FPP will either turn into a single separate token (which lead to the value 0), or into two separate tokens (which lead to the value 1). This is magic. */ #define CCTKi_FPP_A #define CCTKi_FPP_B 1 #define CCTKi_FPP_ACCTKi_FPP_B 0 #define CCTK_ANSI_FPP CCTKi_FPP_A/**/CCTKi_FPP_B #endif ``` so really it should support both. Namely if code fails if `FPP` is not traditional then that could should be changed so that it works both with and without traditional. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2566/check-for-traditi…

1 0

#2538: Inclusion of kuibit
by Roland Haas 21 Oct '21

21 Oct '21

#2538: Inclusion of kuibit Reporter: Gabriele Bozzola Status: open Milestone: ET_2021_11 Version: development version Type: enhancement Priority: major Component: Comment (by Roland Haas): Yosef will try and review starting Sunday \([http://lists.einsteintoolkit.org/pipermail/users/2021-October/008279.html](http://lists.einsteintoolkit.org/pipermail/users/2021-October/008279.html)\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2538/inclusion-of-kuib…

1 0

#2549: inlcude FLRWSolver in ET
by Roland Haas 21 Oct '21

21 Oct '21

#2549: inlcude FLRWSolver in ET Reporter: Roland Haas Status: new Milestone: ET_2021_11 Version: development version Type: enhancement Priority: major Component: Comment (by Roland Haas): Has there been any progress on this? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…

1 0

#2551: include RePriMand in the ET
by Roland Haas 21 Oct '21

21 Oct '21

#2551: include RePriMand in the ET Reporter: Roland Haas Status: new Milestone: ET_2021_11 Version: development version Type: enhancement Priority: major Component: Comment (by Roland Haas): No progress reviewing this yet. Should have time this week. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2551/include-reprimand…

1 0

#2565: compiling PETSc included in the ET fails if "python" executable is missing
by Roland Haas 21 Oct '21

21 Oct '21

#2565: compiling PETSc included in the ET fails if "python" executable is missing Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: Comment (by Roland Haas): I suggest we close this and make sure that users install one of “python-is-python\[23\]” in our list of packages we provide for Debian and related distributions. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2565/compiling-petsc-i…

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac October 2021