Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2531: remove non piraha parser from Flesh
by William Gabella 02 Feb '22

02 Feb '22

#2531: remove non piraha parser from Flesh Reporter: Roland Haas Status: new Milestone: Version: development version Type: enhancement Priority: trivial Component: Comment (by William Gabella): Took this ticket for the Hack-a-thon, 2 Feb 2022. Removing all the local routines, etc, related to the “old way” of parsing the file, and of course keeping the “new way,” with cctk\_PirahaParser function. This is in Cactus/repos/flesh/src/util/ParseFile.c , as Roland mentions above. Re-compiling with $from the Cactus folder$ ``` ./simfactory/bin/sim build -j2 --thornlist ../einsteintoolkit.th ``` and watching for the “COMPILING … ParseFile.c” to go by. And running HelloWorld first, as ``` ./simfactory/bin/sim create-run helloworld \ --parfile arrangements/CactusExamples/HelloWorld/par/HelloWorld.par ``` If that is not broke, then finally the testsuite with ``` make sim-testsuite ``` Format for the teststuite is “make <config name>-testsuite. It gave a set of defaults and I chose them all; testing exe/cactus\_sim . -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2531/remove-non-piraha…

1 0

#2332: piraha does not allow variable expansion in ActiveThorns
by Steven R. Brandt 02 Feb '22

02 Feb '22

#2332: piraha does not allow variable expansion in ActiveThorns Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): [https://bitbucket.org/cactuscode/cactus/pull-requests/137/generate-a-good-e… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2332/piraha-does-not-a…

1 0

#2070: shallow checkouts do not work with branches
by Steven R. Brandt 02 Feb '22

02 Feb '22

#2070: shallow checkouts do not work with branches Reporter: Roland Haas Status: resolved Milestone: Version: development version Type: bug Priority: minor Component: GetComponents Changes (by Steven R. Brandt): status: resolved (was open) Currently using both --shallow and a branch (rather than master) fails since GetComponents wants to first clone the full repo then switch to the requested branch which fails with a shallow clone. However newer versions of git (>=1.7) support a "-b" (branch) option for clone and that one works fine even with shallow clones. My recollection is that we could not use this method initially since there were clusters around that only offered git 1.6 (queenbee likely). This is no longer the case and all clusters in simfactory offer at least git 1.7. This pull request: https://github.com/gridaphobe/CRL/pull/6/files both fixes the problem and simplifies the code. **Keyword:** Comment (by Steven R. Brandt): Now git clone combines the use of --depth 1, --branch, and --single-branch -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2070/shallow-checkouts…

1 0

#2469: None of the thorns in WVUThorns_Diagnostics have documentation
by Leonardo Werneck 02 Feb '22

02 Feb '22

#2469: None of the thorns in WVUThorns_Diagnostics have documentation Reporter: Roland Haas Status: new Milestone: ET_2021_05 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Leonardo Werneck): This can be a medium project for the ET Hackaton. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2469/none-of-the-thorn…

1 0

#2592: TOV_ET tutorial Segfaults when compiling
by Roland Haas 31 Jan '22

31 Jan '22

#2592: TOV_ET tutorial Segfaults when compiling Reporter: Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory Comment (by Roland Haas): Continuation of: [http://lists.einsteintoolkit.org/pipermail/users/2022-January/008381.html](… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-s…

1 0

#2592: TOV_ET tutorial Segfaults when compiling
by Roland Haas 31 Jan '22

31 Jan '22

#2592: TOV_ET tutorial Segfaults when compiling Reporter: Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} says \(in [trac@einsteintoolkit.org](mailto:trac@einsteintoolkit.org) [http://lists.einsteintoolkit.org/pipermail/trac/2022-January/015930.html](h…): > I will try and find a Windows 10 machine. > > --Steve ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-s…

1 0

#2592: TOV_ET tutorial Segfaults when compiling
by Anonymous 31 Jan '22

31 Jan '22

#2592: TOV_ET tutorial Segfaults when compiling Reporter: Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory I'm using a wsl machine mounted in windows 10 and i can't seem to make the tutorial work. It always segfaults after a definite time (time 112.000), i tried allocating more memory but it doesn't seem to resolve the issue, also i checked that the sim doesn't take any large amounts of RAM. It used to work on win 11 but i rolled back to win 10 but it doesn't anymore. I completely reinstalled my wsl machine when i got back on win 10. Either way i'm reporting the backtrace ``` 1. CarpetLib::signal_handler(int) [/home/sam/simulations/tov_ET/SIMFACTORY/exe/cactus_sim(_ZN9CarpetLib14signal_handlerEi+0xb3) [0x56013afdf833]] 2. /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7fbef30cd210] 3. /home/sam/anaconda3/lib/libgfortran.so.4(+0xf3c73) [0x7fbef3522c73] 4. /home/sam/anaconda3/lib/libgfortran.so.4(+0xf429e) [0x7fbef352329e] 5. /home/sam/anaconda3/lib/libgfortran.so.4(+0xf2900) [0x7fbef3521900] 6. /home/sam/simulations/tov_ET/SIMFACTORY/exe/cactus_sim(prim2conpolytype_+0x3f6) [0x56013b464e06] 7. /home/sam/simulations/tov_ET/SIMFACTORY/exe/cactus_sim(+0xb9e28f) [0x56013b46628f] 8. /home/sam/anaconda3/lib/libgomp.so.1(GOMP_parallel+0x42) [0x7fbef329ce22] 9. /home/sam/simulations/tov_ET/SIMFACTORY/exe/cactus_sim(prim2conservativepolytype_+0x54f) [0x56013b472fef] ``` attachment: Immagine.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-s…

2 1

#2256: transfer ET wiki from mediawiki to bitbucket wiki (markdown)
by Roland Haas 27 Jan '22

27 Jan '22

#2256: transfer ET wiki from mediawiki to bitbucket wiki (markdown) Reporter: Roland Haas Status: open Milestone: Version: Type: task Priority: minor Component: EinsteinToolkit website Comment (by Roland Haas): Both GitHub and Bitbucket have options to let the wiki be editable by anyone with an account which may increase contributions by non-maintainers who typically do not have accounts on the ET mediawiki wiki and for whom getting an account may be a barrier $it requires email to [maintainers@einsteintoolkit.org](mailto:maintainers@einsteintoolkit.org) and that one waits until @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} or @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} create the account for them$. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2256/transfer-et-wiki-…

1 0

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server
by Gabriele Bozzola 26 Jan '22

26 Jan '22

#2577: CactusTutorial.ipynb contains code only suitable or tutorial server Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit Virtual Machine Comment (by Gabriele Bozzola): Thank you very much for your taking the time to type the reasoning behind what is being done. It all makes sense. My comment comes from putting myself in the shoes of a new user, so the use I had in mind for the notebook is “document to describe the first steps to someone that wants to try out the code”. For this use case, I think that the notebook $primarily the visualization section$ obfuscates some points by adding complexity. For instance, when I tell people how to make a visualization of timeseries with `kuibit`, I tell them “cd into the directory of your data, and run `plot_timeseries.py --variable "rho" --reduction "maximum"”`, but this is what we have $in the PR at least$: ```shell %%bash # See comment before export PYTHONUSERBASE="$HOME/Cactus" # Here we define a bash variable that contains the path where # the simulation data lives. We do so to keep this tutorial general. # Normally you would just input the path or you would run the # script directly from the data directory. datadir=$(dirname $(./simfactory/bin/sim get-output-dir tov_ET)) # Plot a timeseries with the maximum of the density ./utils/Analysis/kuibit/examples/bins/plot_timeseries.py --datadir $datadir \ --variable "rho" --reduction "maximum" --outdir $datadir from IPython.display import Image # datadir is the top-level directory that contains that data for # a given simulation. In the first cell of this notebook we define # get_datadir() as a helper function to find the path. datadir = get_datadir() Image(filename=os.path.join(datadir, "rho_maximum.png")) ``` It may be to clean up so that most of the complexity is hidden somewhere else, but I still think that these cells are not really describing how I would _really_ use this code. For example, I would never want to mention PYTHONUSERBASE, and the more comments we put the explain why that is unnecessary in practice, the more we bury important information. That said, once again, the main problem is with the visualization section, so maybe we can find a better way to handle that? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2577/cactustutorialipy…

1 0

#2590: Uninitialized variable in Perl code
by Steven R. Brandt 26 Jan '22

26 Jan '22

#2590: Uninitialized variable in Perl code Reporter: Erik Schnetter Status: new Milestone: Version: development version Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): [https://bitbucket.org/cactuscode/cactus/pull-requests/136/sometimes-syntax-… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2590/uninitialized-var…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac