Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction
by Roland Haas 03 Nov '22

03 Nov '22

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction Reporter: Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Well. The parfiles are generated, or at least there are directories Baikal\_parfiles and BaikalVacuum\_parfiles which contains files of the same name bug different content than the files in he ET. Those are the ones I am concerned about. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2661/failure-to-regene…

1 0

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction
by Zach Etienne 03 Nov '22

03 Nov '22

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction Reporter: Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Zach Etienne): Indeed, running the Jupyter notebook that generates Baikal and BaikalVacuum will only create the core C codes. We don’t output other files because they are managed separately. In the future we’d like to have everything “generated” when the Baikal\* notebook is run. Please keep this ticket open until that day. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2661/failure-to-regene…

1 0

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction
by Anonymous 03 Nov '22

03 Nov '22

#2661: failure to regenerate Baikal and BaikalVacuum parfiles from README instruction Reporter: Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Following the instructions in the README file I am unable to reproduce the example parfiles provided for BaikalVaccum. Instead I get different files. Please provide instruction that let the files be reproduced. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2661/failure-to-regene…

1 0

#2176: Test "Binary neutron star" example
by Roland Haas 03 Nov '22

03 Nov '22

#2176: Test "Binary neutron star" example Reporter: Roland Haas Status: resolved Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutr…

1 0

#2598: thornyflat - production run segmentation fault
by Anuj Kankani 03 Nov '22

03 Nov '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: resolved Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Anuj Kankani): Thank, I think you gave me write access back in August so I should be good. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Roland Haas 03 Nov '22

03 Nov '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: resolved Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Roland Haas): There probably should be one. Right now it is only implied. Though I suspect I will have to first actually grant you write access to the repository. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Anuj Kankani 03 Nov '22

03 Nov '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: resolved Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Anuj Kankani): At the very end of [https://docs.einsteintoolkit.org/et-docs/Testsuite\_Machines](https://docs.… after the git commit command, there is no git push command. Is this a mistake or am I missing something? Just wanted to double check before pushing my results. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Roland Haas 03 Nov '22

03 Nov '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: resolved Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Roland Haas 03 Nov '22

03 Nov '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Roland Haas): Applied as git hash [c2214852](https://bitbucket.org/simfactory/simfactory2/commits/c221485284a6… "thornyflat: correct directories" of [simfactory2](https://bitbucket.org/simfactory/simfactory2) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2176: Test "Binary neutron star" example
by Bing-Jyun Tsao 02 Nov '22

02 Nov '22

#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): BNS gallery example \(bns-20221027\) is updated on the website. Notes on running BNS gallery example \(10-27\): - Gnuplot issue with epstopdf and convert: need to update gnuplot and allow read/write access with ImageMagick. - Add python script to plot Psi4 using quibit instead \(plot\_quibit.py in script.tar.gz\). - Compiling issue with LORENE: might not have the latest version of cmake, resolved by running on Expanse and Frontera. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutr…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac