#2552: VERSION option in configuration.ccl is overly restrictive in allowed characters
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component:
I have a file `configuration.ccl` like so:
```
# Configuration definitions for thorn CMake
PROVIDES CMake
{
SCRIPT src/detect.sh
LANG bash
VERSION 3.15.0
OPTIONS CMAKE_DIR CMAKE_INSTALL_DIR
}
```
and CST fails with:
```
CST error in /data/rhaas/postdoc/gr/cactus/CactusAMReX/arrangements/ExternalLibraries/CMake/configuration.ccl (at 7)
-> SYNTAX ERROR
HINT: ERROR ON LINE 7:
SCRIPT src/detect.sh
LANG bash
VERSION 3.15.0
^
| here
FOUND CHARACTER: '.'
EXPECTED CHARACTER(S): '-', '0' to '9', 'A' to 'Z', '\', '_', 'a' to 'z', '}'
```
ie the dot “.” is not allowed in version strings. Since these were modeled \(somewhat\) after Debian version numbers, here’s an example of one of those `2:3.6.19-1~bpo70+1+b1` and [https://manpages.debian.org/buster/dpkg-dev/deb-version.7.en.html](https://… for their definition \(upstream version could be any string, really\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2552/version-option-in…
#2551: include RePriMand in the ET
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component:
Comment (by Wolfgang Kastaun):
The public RePrimAnd repository contains a prototype for an external libraries thorn. It is located in the folder
`ET_interface/thorns/RePrimAnd`
The thorn already contains an archive of the library. It built successfully with the latest ET release \(Lorentz\). It depends on other external libraries: BOOST and GSL \(the latter is likely to be dropped in the future\). For the time being, it also requires the meson build system to be installed on the build host. This could be replaced by a make with moderate effort.
The only documentation of the thorn so far is a README file pointing to the repository, which links to the latest online documentation of the library.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2551/include-reprimand…
#2551: include RePriMand in the ET
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component:
RePrimAnd [https://github.com/wokast/RePrimAnd](https://github.com/wokast/RePrimAnd) implements and advanced con2prim scheme and EOS that could be used in the ET.
This will most likely be a multi-step process with first only the library and its C\+\+ interface being available followed eventually by a Cactus native interface and possible wrappers for existing codes that use `EOS_Omni`. There is also a design challenge in defining, once more, the set of primitives that ID thorns provide and con2prim must compute.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2551/include-reprimand…
#2534: Evolution of grid arrays with Mol no longer works
Reporter:
Status: new
Milestone:
Version: development version
Type: bug
Priority: major
Component: Carpet
Comment (by Roland Haas):
I see, that would require extra logic even if MoL was being ore accommodating about evolving arrays since you will have to query Carpet about the finest refinement level a given location is contained in anyway. `GLOBAL` routines are called every timestep \(same frequency as eg routines will execute on the finest timestep\). Anyway, I was just curious.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2534/evolution-of-grid…
#2534: Evolution of grid arrays with Mol no longer works
Reporter:
Status: new
Milestone:
Version: development version
Type: bug
Priority: major
Component: Carpet
Comment (by Yosef Zlochower):
To maintain accuracy for geodesics, I needed to evolve the geodesics at the same time as the underlying grid that they happen to be on.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2534/evolution-of-grid…
#2550: support compiling in Raspberry Pi 4
Reporter: Roland Haas
Status: resolved
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component:
Changes (by Roland Haas):
status: resolved (was open)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2550/support-compiling…
#2550: support compiling in Raspberry Pi 4
Reporter: Roland Haas
Status: open
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component:
Comment (by Erik Schnetter):
This looks good. Please apply.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2550/support-compiling…
#2550: support compiling in Raspberry Pi 4
Reporter: Roland Haas
Status: open
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component:
Changes (by Roland Haas):
status: open (was new)
Comment (by Roland Haas):
Please review.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2550/support-compiling…
#2550: support compiling in Raspberry Pi 4
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component:
The Pi4 \(and maybe 3 and 2 as well, I don’t own a 3 and compiling on my 2 is going to be painful\) use gnueabihf which the current known-architectures do not catch.
Pull request [https://bitbucket.org/cactuscode/cactus/pull-requests/125/support-raspberry… adds code to recognize and and also fixes some reliance on GNU awk \(or so it seems\) rather than eg mawk \(in raspbian minimal\).
With these I can compile ET\_2021\_05 and run both the 2 and 1 process testsuites without a single error.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2550/support-compiling…