#2621: keep running into nan ,need help
Reporter: Artectek
Status: new
Milestone: ET_2022_05
Version: ET_2022_05
Type: bug
Priority: minor
Component: EinsteinToolkit thorn
Changes (by Artectek):
I try to run a double neutron star sim,using a cold eos table,but i keep running into nan for months,the par file and the output and err file are in the attachments.please give me some hints on where could be going wrong,I really have no clue.
there are other sim i used,but the result are the same,usually it started normal,everything looks fine,the center density the stable,the rotation looks ok,but later on,just when the matter from two stars started to interact with each other,something always happen,either
nan on the start of the interaction,or nan in the process of [merge. At](http://merge.at) first i thought maybe it became a blackhole,but the i checked the center density,it did not show signs of continue increase,often it just running normally and nan just happened.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2621/keep-running-into…
#2621: keep running into nan ,need help
Reporter: Artectek
Status: new
Milestone: ET_2022_05
Version: ET_2022_05
Type: bug
Priority: minor
Component: EinsteinToolkit thorn
Changes (by Artectek):
I try to run a double neutron star sim,using a cold eos table,but i keep running into nan for months,the par file and the output and err file are in the attachments.please give me some hints on where could be going wrong,I really have no clue
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2621/keep-running-into…
#2601: Add four more parameters for carpet
Reporter: Liwei Ji
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component: Carpet
Comment (by Liwei Ji):
Hi Roland, thanks. I will add the above test par to `Carpet/test`.
We are thinking about add support of mesh refinement to SphericalNR at some point. But not relatively soon. When that happens, we will update this part to make it also works with mesh refinement. Thanks for pointing it out.
In order to get the size of boundary points, I have tried with the par `granularity_boundary`. It is always `0`, even thought in the test par, we have set `CoordBase::boundary_size_x_lower = $boundary_size`. Should we set `granularity_boundary` explicitly in the par file or use `ghost_width[i]` instead for the moment?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…
#2601: Add four more parameters for carpet
Reporter: Liwei Ji
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component: Carpet
Comment (by Roland Haas):
Thank you. I think with those things should be good to go. With the addition of adding this parfile as a test case to Carpet. Shiftout is ok since without the shiftout the first boundary point is exactly on the boundary \(eg at -1.0\) and there are not `boundary_size` points _outside_ of the nominal domain \(but `boundary_size - 1`\). This is actually intentional since it helps with convergence to have the boundary point stay fixed.
Weren’t there plans at one point for SphericalNR to support / use mesh refinement on top of the spherical coordinates? In that case one would have to update this code it would seem.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…
#2601: Add four more parameters for carpet
Reporter: Liwei Ji
Status: new
Milestone:
Version: development version
Type: enhancement
Priority: major
Component: Carpet
Changes (by Roland Haas):
responsible: [] (was )
assignee: Roland Haas (was )
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-par…
#2620: WVUThorns/Baikal & BaikalVacuum need CoordGauge, Slicing info in interface.ccl to compile
Reporter: Bernard Kelly
Status: new
Milestone: ET_2022_05
Version: ET_2022_05
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Zach Etienne):
Thanks for the report @{557058:3bd8b315-5aeb-4783-8a43-0585fee09596} . Commit 7d3dc5ad080cbf12040adee51dc3baa44c477325 to WVUThorns applies the suggested patch and closes this ticket.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2620/wvuthorns-baikal-…
#2598: thornyflat - production run segmentation fault
Reporter: Maria
Status: new
Milestone:
Version: ET_2021_11
Type: bug
Priority: major
Component:
Comment (by Maria):
Yes, you’re right, with the 93 version of the compiler and openmpi, it does work. I raised the issue because I updated it to gcc11. We should get it to work with current software.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…
#2620: WVUThorns/Baikal & BaikalVacuum need CoordGauge, Slicing info in interface.ccl to compile
Reporter: Bernard Kelly
Status: new
Milestone: ET_2022_05
Version: ET_2022_05
Type: bug
Priority: major
Component: EinsteinToolkit thorn
The thorns Baikal & BaikalVacuum in WVUThorns both reference “Slicing.h” in src/RegisterSlicing.c. However, this header file is not found during compilation on my machines as it belongs to the thorn EinsteinBase/CoordGauge.
For compilation to succeed, Baikal \(and BaikalVacuum\) needs the following two additions to its interface.ccl:
inherits: CoordGauge
USES INCLUDE: Slicing.h
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2620/wvuthorns-baikal-…