#2654: PR for ADMAnalysis Trace function with incorrect interface
Reporter: Samuel Cupp
Status: resolved
Milestone:
Version: development version
Type: bug
Priority: minor
Component: EinsteinToolkit thorn
Changes (by Roland Haas):
status: resolved (was new)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2654/pr-for-admanalysi…
#2175: Test "Single, stable neutron star" example
Reporter: Roland Haas
Status: open
Milestone: ET_2022_11
Version: development version
Type: task
Priority: major
Component: EinsteinToolkit website
Comment (by Leung, Lisa Jing):
Ran and uploaded result on 10/26/2022 with latest update, maximum density plot looks consistent with 5/12/2022 result
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stabl…
#2659: ExternalLibrary auto-detection fails on M1 macs using homebrew
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: bug
Priority: major
Component:
With @{6350afe6fe5ff37523587456} I just dug down a bit into compilation failures using HomeBrew on macOS M1.
There were three errors reported at CST stage by ExternalLibraries;
```
CST error 1:
-> Configuration script for thorn LIBJPEG returned exit code 77
(no error message)
CST error 2:
-> Configuration script for thorn OPENSSL returned exit code 2
(no error message)
CST error 3:
-> Configuration script for thorn ZLIB returned exit code 1
(no error message)
```
which turn out to be compilation failures, at least in LIBJPEG’s case. Now libjpeg should not even be attempted to be compiled since the tutorial instructions \(which were followed\) contain `brew install jpeg` and indeed `jpeg` was installed.
It turns out that HomeBrew moved from `/usr/local` to `/opt/homebrew` so that the rather limited set of locations checked by many ExternalLibraries no longer match. `pkg-config` is not help here either it seems.
Part of this is already broken on x86 macs where HomeBrew does not install `OpenSSL` and `zlib` into `/usr/local` but only into its own `Cellar` hierarchy so that the installed copies are being ignored already on x86 macs \(verified on my own x86 macOS VM\).
With this we can no longer claim macOS support using homebrew. If similar issues occur using macports then we can no longer claim any macOS support.
Fixes would involve finding out why pkg-config fails and also why compilation attempts fail. Looking at the log files for libjpeg it tried using `gcc` \(ie Apple’s clang-in-disguise\) instead of the correct `gcc-12` from homebrew. This, unsurprisingly failed. Similarly for OpenSSL \(fails due to lack of support of `-fopenmp`\) and similar for zlib.
This will need a M1 owner to step forward as a volunteer to help fix this.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2659/externallibrary-a…
#2658: change cGroup centeringtable into flat list of integers
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component:
Currently, and for mostly historical reason, since it started out as a tag, `centeringtable` is a handle making its use less convenient than may be desired. For the most part this data is used by the driver, since user codes normally “know” what centering their grid functions have. However it may also be used by non-driver infrastructure thorns.
Also it may be good to define a default centering Cactus wide instead of letting the driver define its defaults so that non-driver infrastructure thorns can be provided with a centering value that matches what the driver uses if none is provided.
A more convenient data structure would be just a `const int *` similar to e.g. `cGroupDynamicData.lsh`. This would require that `CCTK_GroupCenteringTableI` uses a calling syntax similar to `CCTK_GroupbboxGI` ie
```
int CCTK_GroupCenteringTableGI(const cGH *cctkGH, int size, int *centeringtable, int groupindex);
```
which copies the data into a user supplied buffer to support C and Fortran callers.
While in the flesh all centering code is still considered experimental \(and intentionally not documented yet\) so can be changed.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2658/change-cgroup-cen…
#2176: Test "Binary neutron star" example
Reporter: Roland Haas
Status: open
Milestone: ET_2022_11
Version: development version
Type: task
Priority: major
Component: EinsteinToolkit website
Comment (by Bing-Jyun Tsao):
```
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 126665
max locked memory (kbytes, -l) 65536
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 126665
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
```
Here is the output with `ulimit -a`. You are correct, this is actually ran on a computer that is shared among our group members.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutr…
#2176: Test "Binary neutron star" example
Reporter: Roland Haas
Status: open
Milestone: ET_2022_11
Version: development version
Type: task
Priority: major
Component: EinsteinToolkit website
Comment (by Roland Haas):
On the local machine \(with the failure\), what is the output of `ulimit -a`? “local” here means all local file systems, not anything \(eg $HOME\) mounted via NFS? \(trying to understand what may be going on\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutr…