Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2586: new cGH field cctk_patch
by Roland Haas 18 Jan '22

18 Jan '22

#2586: new cGH field cctk_patch Reporter: Roland Haas Status: new Milestone: Version: development version Type: enhancement Priority: minor Component: Cactus Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/cactuscode/cactus/pull-requests/135/cactus-new-cgh-fi… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2586/new-cgh-field-cct…

1 0

#2586: new cGH field cctk_patch
by Roland Haas 18 Jan '22

18 Jan '22

#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…

1 0

#2483: Simfactory job parameters are not consistent
by Roland Haas 18 Jan '22

18 Jan '22

#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…

1 0

#2585: The website does not have citations recommendations for codes in the canuda suite
by Roland Haas 12 Jan '22

12 Jan '22

#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-…

1 0

#2585: The website does not have citations recommendations for codes in the canuda suite
by Roland Haas 11 Jan '22

11 Jan '22

#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): Thank you for reporting these and providing fixes. It turns out that these steps are already on the ET release process page \(two items actually\): \* [https://docs.einsteintoolkit.org/et-docs/Release\_Process#create\_branches]… \* and earlier: > Update einsteintoolkit.bib \([https://bitbucket.org/einsteintoolkit/manifest/src/master/](https://bitbucket.org/einsteintoolkit/manifest/src/master/)\) with > > Requested and suggested citations for all thorns in thorn list \(_10 minutes_\). > Latest release info and DOI \(from Zenodo entry above\) so the issue is that steps were skipped \(or “thorns” was taken to really mean only “thorns” and not “ET components”\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2585/the-website-does-…

1 0

#2585: The website does not have citations recommendations for codes in the canuda suite
by Gabriele Bozzola 11 Jan '22

11 Jan '22

#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 Gabriele Bozzola): [https://bitbucket.org/einsteintoolkit/manifest/pull-requests/11/update-requ… fixes the key entry. [https://bitbucket.org/einsteintoolkit/www/pull-requests/11/contributers-con… fixes the typo. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2585/the-website-does-…

1 0

#2585: The website does not have citations recommendations for codes in the canuda suite
by Gabriele Bozzola 11 Jan '22

11 Jan '22

#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 [https://einsteintoolkit.org/citation.html](https://einsteintoolkit.org/cita… and [https://bitbucket.org/einsteintoolkit/manifest/raw/master/einsteintoolkit.b… do not have any information about codes like Lean/Proca/… \(the canuda collection\). Incidentally, I also noticed that the webpage says: “The primary way to cite the Einstein Toolkit is now by the DOI assigned to the current release [doi:10.5281/zenodo.4884780](https://doi.org/10.5281/zenodo.4884780) \(key: EinsteinToolkit:2021\_05\). This method cites the software and assigns credit to the many contributers over the years.” As you see, the key is outdated. I can fix this, but I reporting this here to ensure that this item to the checklist for a new release. Also, my dictionary underlines the word “contributers” as wrong. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2585/the-website-does-…

1 0

#1278: Handle inf and nan in parameter file parser
by Roland Haas 10 Jan '22

10 Jan '22

#1278: Handle inf and nan in parameter file parser Reporter: Erik Schnetter Status: resolved Milestone: Version: Type: bug Priority: minor Component: Cactus Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1278/handle-inf-and-na…

1 0

#1278: Handle inf and nan in parameter file parser
by Roland Haas 10 Jan '22

10 Jan '22

#1278: Handle inf and nan in parameter file parser Reporter: Erik Schnetter Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Comment (by Roland Haas): Sure. Steve pointed out \(offline communication\) that `expressions.par` in TestPar does indeed contain `nan` . Somehow `git log -G 'nan'` does not find it. Closing the ticket since it has already been fixed. ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1278/handle-inf-and-na…

1 0

#1278: Handle inf and nan in parameter file parser
by Steven R. Brandt 10 Jan '22

10 Jan '22

#1278: Handle inf and nan in parameter file parser Reporter: Erik Schnetter Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): So `TestPar.par` does contain a test with an `inf` and `call.cc` does check for `inf` and `nan`. The test passes. As near as I can tell, this ticket ought to be closed. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1278/handle-inf-and-na…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac