search

lwang-astro / PeTar

PeTar is a high-performance N-body code for modelling the evolution of star clusters and tidal streams, including the effect of galactic potential, dynamics of binary and hierarchical system, single and binary stellar evolution.
MIT License
71 stars 19 forks source link

Bad Termination Error #22

Closed JoRdAnB421 closed 2 years ago

JoRdAnB421 commented 2 years ago

When running, I occasionally receive a BAD TERMINATION error, pictured below. Is this the large step warning mentioned in the ReadMe (my runs are using stellar evolution) or a result of some other error? And is the best solution to simply restart with fewer cpu cores?

image

Thanks for your help

JoRdAnB421 commented 2 years ago

I have tried restarting the run from the previous snapshot with fewer cpu's and it will sometimes proceed for a few more steps before it crashes again with the same errors.

lwang-astro commented 2 years ago

Hi, this problem happens when the newest FDPS (v7.1) is used. Could you try to use the old version of FDPS v7.0?

JoRdAnB421 commented 2 years ago

Hi, so I have tried to use the FDPS v7.0 and I have still received the same error.

In order to use the older version I simply cloned the FDPS directory and then use git checkout 6fedb4b which is the id for the v7.0 commit is this an appropriate way to select the older version for use? I am not aware of another way to clone an older version of a github repo.

Thanks

lwang-astro commented 2 years ago

In FDPS directory, you can git checkout v7.0. If the version is successfully switched. When you run petar, the output log will show the FDPS version v7.0 inside the FDPS logo.

JoRdAnB421 commented 2 years ago

I can confirm that this worked. Thanks a lot!

JoRdAnB421 commented 2 years ago

Hello again,

I have run into a similar error now when running the petar.find.dt tool, though it has an exit code 11 rather than the 6 I was getting before. image I am using the v7.0 FDPS package as you can see: image

lwang-astro commented 2 years ago

There is no useful error message from your log. Can you successfully run a test sample without petar.finddt? If the test run is fine. Then your option for petar.find.dt may not be correct.