#2553: Cactus' link command used CPPFLAGS and CXXFLAGS
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component: Cactus
Cactus link line in make.configuration looks like this right now:
```
$(LD) $(CREATEEXE)$(OPTIONSEP)"$(call TRANSFORM_DIRS,$@)" $(CPPFLAGS) $(CXXFLAGS) $(LDFLAGS) $(EXTRAFLAGS) "$(call TRANSFORM_DIRS,$(TOP)/datestamp.o)" $(BEGIN_WHOLE_ARCHIVE_FLAGS) $(CACTUSLIBLINKLINE) $(END_WHOLE_ARCHIVE_FLAGS) $(GENERAL_LIBRARIES)
```
ie it passed `$(CPPFLAGS)` and `$(CXXFLAGS)` to `$(LD)`. While we do normally set `LD` to the same as `CXX` this is not always correct, eg if one would like to use `g++` for C\+\+ files but link with `nvcc`.
Neither one of these options is required or should be there since `$(LD)` does not compile anything at all. Any subset of options from `$(CPPFLAGS)` or `$(CXXFLAGS)` that may be needed \(eg `-fopenmp` should be set in `$(LDFLAGS)`\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2553/cactus-link-comma…
#2549: inlcude FLRWSolver in ET
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component:
Comment (by Pierre Mourier):
Hi, I am a postdoc at the Max Planck Institute for gravitational Physics in Hannover. Before this I did my PhD on inhomogeneous cosmology and the impact of structure formation in the late Universe on the large-scale dynamics, and this is still part of my research interests. As such, I am currently using the ET and the FLRWSolver thorn for some simple cosmological setups and planning to use them in the near future for more involved cosmological simulations. I think that it would be very useful for such applications of the ET to have it include FLRWSolver in future releases.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…
#2549: inlcude FLRWSolver in ET
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component:
Comment (by Michele Grasso):
Hi, I am Michele, a PhD student at the Center for Theoretical Physics in Warsaw and ET user. I believe that having the FLRWSolver thorn included in the ET would be extremely useful for all the users interested in cosmology. The thorn has already a place among the main codes for general-relativistic simulations of cosmological structure formation \(see arXiv:2003.08014\). I've used the FLRWSolver in my research on relativistic light propagation and observables extrapolation, see arXiv:2107.06306, and I plan to use the thorn in my future works.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…
#2549: inlcude FLRWSolver in ET
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component:
Comment (by Theo Anton):
Hi - I’m planning to use FLRWSolver in my research \(I’m a PhD student at Queen Mary University of London working on testing GR/modified gravity in cosmology\), so having FLRWSolver included in the ET would be really useful to me
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…
#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: Cactus
Changes (by Roland Haas):
assignee: Steven R. Brandt (was )
responsible: [] (was )
component: Cactus (was )
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2552/version-option-in…
#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…