#2586: new cGH field cctk_patch
Reporter: Roland Haas
Status: open
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component: Cactus
Comment (by Roland Haas):
Note that to find out the total number of patches \(maps\) one still has to call the aliased functon `GetMaps`. Not sure if there is a legit use for that information though \(there is also not official way to find out the total number of components \[not MPI ranks\]\). Also note that the assumption `cctk_patch == 0` → Cartesian patch is most likely not true for eg the 6 patch cubed sphere system \(which has no Cartesian block in the center\). The function to query this would be `MultiPatch_MapIsCartesian` in the `Coordinates` thorn \(which only requires knowledge of `cctk_patch` and of course calls it `map`\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2586/new-cgh-field-cct…
#2586: new cGH field cctk_patch
Reporter: Roland Haas
Status: open
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component: Cactus
Comment (by Roland Haas):
Please apply.
Requests:
* document `cctk_patch` in the UsersGuide
* in the UsersGuide replace all use of “patch” meaning “disjoint grid patch” by “component” to avoid using “patch” for 2 different things \(at least in the docs. Carpet still uses “patch” for “component” eg in CarpetIOHDF5’s checkpoint file handling code\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2586/new-cgh-field-cct…
#2586: new cGH field cctk_patch
Reporter: Roland Haas
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: minor
Component: Cactus
Cactus currently does not contain a easy way to find out which patch \(“map”\) one is on for multipatch \(Llama\) simulations, instead requiring the use of the aliased function `GetMap` provided by `Carpet`.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2586/new-cgh-field-cct…
#2483: Simfactory job parameters are not consistent
Reporter: Steven R. Brandt
Status: new
Milestone:
Version:
Type: bug
Priority: major
Component: SimFactory
Comment (by Roland Haas):
Not sure if `--total-threads` is more useful since that is not a quantity people normally think about. If one takes a look at what the `mpirun`/ `srun` / `aprun` etc commands actually use: “processes” \(= MPI ranks\) and “allocated \(logical ie the thing the OS counts is /proc/cpuinfo\) cpus per process”. Ie they start `n` processes which are then free to spread out on `t` threads each \(or not, if they only need more memory\).
So a more useful new option might be `--ranks` or even `--mpi-ranks`.
“cores” or “nodes” may be what the queuing system allocates usually though the `mpirun` like options are more directly understandable to users and the queuing system options are derived from them \(since each queuing system is set up slightly differently, even if they use eg SLURM\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2483/simfactory-job-pa…
#2585: The website does not have citations recommendations for codes in the canuda suite
Reporter: Gabriele Bozzola
Status: new
Milestone:
Version: development version
Type: bug
Priority: minor
Component: EinsteinToolkit website
Comment (by Roland Haas):
For the Canuda thorns I am not sure if any requested / suggested citations were added at the time the thorns were included. The Proca repo’s `README.md` in the repo main directory says:
If you use these thorns as part of your research, we would be grateful if you could [cite our work](https://bitbucket.org/canuda/proca/src/master/manifest/canuda_proca.b…. [https://bitbucket.org/canuda/proca/src/master/manifest/canuda\_proca.bib](h…
This might be something to check with the Canuda authors. The bibtex file lists only two entries, not sure which one \(if any\) the authors would prefer \(and if they would like something that can be updated easily on their own\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2585/the-website-does-…