Trac June 2023

trac@lists.einsteintoolkit.org

1 participants
81 discussions

#2740: broken links in the Tutorial for New Users webpage
by Bruno Giacomazzo 09 Jun '23

09 Jun '23

#2740: broken links in the Tutorial for New Users webpage Reporter: Bruno Giacomazzo Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit website The link to the Github repository in “Download the tutorial” \([https://github.com/einsteintoolkit/jupyter-et](https://github.com/einsteintoolkit/jupyter-et)\) and the one to the read only version of the CactusTutorial.ipynb notebook \([https://github.com/einsteintoolkit/jupyter-et/blob/master/tutorial-server/notebooks/CactusTutorial.ipynb](https://github.com/einsteintoolkit/jupyter-et/blob/master/tutorial-server/notebooks/CactusTutorial.ipynb)\) do not work anymore. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2740/broken-links-in-t…

1 0

#2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no"
by Vikram Manikantan 09 Jun '23

09 Jun '23

#2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no" Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Vikram Manikantan): Hello @{5bae587b96242d2e2b6110a4} , I implemented the changes in schedule.ccl in IlllinoisGRMHD as suggested, but it is still producing NaNs. See the output log of the simulation below. Please also see my above comment about replacing the SetTmunu group versus appending to the scheduler. Let me know what is the correct approach. Thanks. ![](https://bitbucket.org/repo/8zBLME5/images/3545285135-ILGRMHD_error.png) ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2497/illinoisgrmhd-is-…

1 0

#2723: No boundary conditions registered for variables in group LEANBSSNMOL
by Samuel Cupp 08 Jun '23

08 Jun '23

#2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: open Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Samuel Cupp): Looking more closely at the thorn, I feel its important to point out that it doesn’t have any READ or WRITE declarations. This means that no one has updated it to use the PreSync features. So even if you resolve the boundary warnings, it won’t really benefit you because the READ/WRITE declarations aren’t there yet. I’m sure the maintainers of Lean would be appreciative if you added them. However, if you don’t have the time to add those to the schedule.ccl, then none of the `presync_mode` settings can actually be used. I do think I have found the source of the issue, though. The issue is that the PreSync feature isn’t being informed of what the BCs are. The old boundary thorn uses `Boundary_SelectGroupForBC` to control how BCs are applied, while PreSync depends on the driver function `Driver_SelectGroupForBC`. At some point, I had suggested that this call be added to the `Boundary_SelectGroupForBC` as well for the sake of old thorns, but that doesn’t seem to have happened. I did a pretty ugly edit real quick by duplicating the boundary f’n calls with driver calls. This runs until it hits an error because PreSync tries to apply boundary conditions on something that isn’t valid in the interior \(and nothing is valid anywhere because of paragraph 1\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-condi…

1 0

#2739: change ADMMacros::spatial_order to GRHydro::sources_spatial_order in Hydro_RNSID example parfiles
by Roland Haas 08 Jun '23

08 Jun '23

#2739: change ADMMacros::spatial_order to GRHydro::sources_spatial_order in Hydro_RNSID example parfiles Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2739/change-admmacros-…

1 0

#2739: change ADMMacros::spatial_order to GRHydro::sources_spatial_order in Hydro_RNSID example parfiles
by Roland Haas 08 Jun '23

08 Jun '23

#2739: change ADMMacros::spatial_order to GRHydro::sources_spatial_order in Hydro_RNSID example parfiles Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests/17]… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2739/change-admmacros-…

1 0

#2739: change ADMMacros::spatial_order to GRHydro::sources_spatial_order in Hydro_RNSID example parfiles
by Roland Haas 08 Jun '23

08 Jun '23

#2739: change ADMMacros::spatial_order to GRHydro::sources_spatial_order in Hydro_RNSID example parfiles Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn @{557058:3bd8b315-5aeb-4783-8a43-0585fee09596} reported [https://lists.einsteintoolkit.org/pipermail/users/2023-June/008942.html](ht… that the example parameter files still contains use of `ADMMacros::spatial_order` which `GRHydro` no longer uses and has been replaced in `GRHydro` by `GRHydro::sources_spatial_order`. Since ADMMacros is deprecated these should be removed from the par files. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2739/change-admmacros-…

1 0

#2738: Caunda/Proca and Canuda/Scalar test faiilures after commits that "remove parameter eta_beta_dynamic"
by Roland Haas 08 Jun '23

08 Jun '23

#2738: Caunda/Proca and Canuda/Scalar test faiilures after commits that "remove parameter eta_beta_dynamic" Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:65c5f18c-c3ad-4126-bb2b-be0e766b31ef} @{557058:a2800088-fc6e-4fbe-9a1e-663271f736bd} some more details. The Einstein Toolkit tests still all pass in test run 682 on [https://einsteintoolkit.github.io/tests/](https://einsteintoolkit.github.io… then first fail in run 683 [https://einsteintoolkit.github.io/tests/build\_683.html](https://einsteinto… . The HTML page shows a list of changes that happened to the full ET repositories since the last run \(ie from 682 to 683\). Most of them are for nrpytutorial so unlikely to affect anything in Canuda or Lean\_public. The last recorded change though in LeanBSSLMoL and reports on the changes in git commits [0faaf83](https://bitbucket.org/einsteintoolkit/tickets/commits/0faaf83)..[7… of lean\_public \(you can see them using `git log 0faaf83..7457e18` in your checkout\): > updated submodules > Submodule repos/lean\_public [0faaf83](https://bitbucket.org/einsteintoolkit/tickets/commits/0faaf83)..[7…: > > LeanBSSNMoL: remove parameter eta\_beta\_dynamic from test parameter files > NPScalars \[schedule.ccl\]: fix scheduling of CalcNPScalars > LeanBSSNMoL: remove unused parameters eta\_beta\_dynamic and moving\_eta\_transition > LeanBSSNMoL \[schedule.ccl\]: remove sync call in LeanBSSN\_adm2bssn > LeanBSSNMoL \[schedule.ccl\]: make sure that ApplyBCs at CCTK\_INITIAL is only called after Boundary\_SelectGroupForBC are set ‌ The HTML page contains links to the log files for each failing test in the “Failed Tests and Changes” table. Eg. [https://github.com/EinsteinToolkit/tests/blob/gh-pages/records/version\_683… for the failing “teukolsky” test in NPScalars. The teukolsky test seems to run without error message and then fails due to too large differences \(see the diff link in the table that shows the diff file that the Cactus test system produces: [https://github.com/EinsteinToolkit/tests/blob/gh-pages/records/version\_683… \) The others seem to fail with a parameter file error \(visible in their log files\): ``` [1mWARNING[L1,P0] (Cactus):[0m Major error in parameter file '/home/runner/simulations/TestJob01_temp_2/output-0000/arrangements/Scalar/TwoPunctures_BBHSF/test/SF_twopuncturesID_test.par' line 166: Parameter 'LeanBSSNMoL::eta_beta_dynamic' not found [1mWARNING level 0 from host fv-az357-438.xjukslrwoije1kgjy1zwota3vf.cx.internal.cloudapp.net process 0 in thorn Cactus, file /home/runner/work/tests/tests/master/configs/sim/build/Cactus/main/ProcessParameterDatabase.c:201: ->[0m CCTKi_SetParameterSetMask: 1 major error in parameter file WARNING[L1,P0] (Cactus): Major error in parameter file '/home/runner/simulations/TestJob01_temp_2/output-0000/arrangements/Scalar/TwoPunctures_BBHSF/test/SF_twopuncturesID_test.par' line 166: Parameter 'LeanBSSNMoL::eta_beta_dynamic' not found WARNING level 0 from host fv-az357-438.xjukslrwoije1kgjy1zwota3vf.cx.internal.cloudapp.net process 0 in thorn Cactus, file /home/runner/work/tests/tests/master/configs/sim/build/Cactus/main/ProcessParameterDatabase.c:201: -> CCTKi_SetParameterSetMask: 1 major error in parameter file WARNING[L1,P1] (Cactus): Major error in parameter file '/home/runner/simulations/TestJob01_temp_2/output-0000/arrangements/Scalar/TwoPunctures_BBHSF/test/SF_twopuncturesID_test.par' line 166: Parameter 'LeanBSSNMoL::eta_beta_dynamic' not found WARNING level 0 from host fv-az357-438.xjukslrwoije1kgjy1zwota3vf.cx.internal.cloudapp.net process 1 in thorn Cactus, file /home/runner/work/tests/tests/master/configs/sim/build/Cactus/main/ProcessParameterDatabase.c:201: -> CCTKi_SetParameterSetMask: 1 major error in parameter file -------------------------------------------------------------------------- MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD with errorcode 1. ``` which, if one scrolls to the right, refers to a parameter `LeanBSSNMoL::eta_beta_dynamic`which is not found. “major” since it should be fixed before the next release and no know workaround \(to make the tests pass\) exists. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2738/caunda-proca-and-…

1 0

#2738: Caunda/Proca and Canuda/Scalar test faiilures after commits that "remove parameter eta_beta_dynamic"
by Roland Haas 08 Jun '23

08 Jun '23

#2738: Caunda/Proca and Canuda/Scalar test faiilures after commits that "remove parameter eta_beta_dynamic" Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Hello all, not sure if this is already internally tracked by Canuda, but the commits that "remove parameter eta\_beta\_dynamic" seem to have made tests fail. See [https://einsteintoolkit.github.io/tests/build\_683.html](https://einsteinto… where it lists commit 12 and the failed tests. Unfortunately the ET test system had been offline for a bit \(due to GitHub removing python2 from the system\) and the change was not visible in the test results right away and so that report contains many \(unrelated\) changes. What I would guess are the relevant changes are: > updated submodules > Submodule repos/lean\_public 0faaf83..7457e18: > > LeanBSSNMoL: remove parameter eta\_beta\_dynamic from test parameter files > > NPScalars \[schedule.ccl\]: fix scheduling of CalcNPScalars > > LeanBSSNMoL: remove unused parameters eta\_beta\_dynamic and moving\_eta\_transition > > LeanBSSNMoL \[schedule.ccl\]: remove sync call in LeanBSSN\_adm2bssn > > LeanBSSNMoL \[schedule.ccl\]: make sure that ApplyBCs at CCTK\_INITIAL is only called after Boundary\_SelectGroupForBC are set ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2738/caunda-proca-and-…

1 0

#2723: No boundary conditions registered for variables in group LEANBSSNMOL
by Vikram Manikantan 07 Jun '23

07 Jun '23

#2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: open Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Vikram Manikantan): status: open (was resolved) Comment (by Vikram Manikantan): From latest comment. The issue is still present even with the suggested fixes, so I am reopening this ticket. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-condi…

1 0

#2723: No boundary conditions registered for variables in group LEANBSSNMOL
by Vikram Manikantan 07 Jun '23

07 Jun '23

#2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: resolved Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Vikram Manikantan): @{557058:65c5f18c-c3ad-4126-bb2b-be0e766b31ef} @{557058:088051f9-5b94-4b5e-bfbe-71137030b9c1} Thanks for your replies. Even after using the updated master branch, the issue is still persistent. I even double checked that the changes in schedule.ccl have been made. Is this issue a concern? I am reopening this ticket. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-condi…

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac June 2023