-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault when generating particles from prior #16
Comments
Hi Vatsal, It won't have anything to do with the seed - high numbers work fine. Is your code in a repository somewhere so I can run it myself?
|
Hi Brendon, Sure, I uploaded the code here : https://github.com/vatsalpanwar/OnlyRV Vatsal |
Ta. One problem is that the model needs the lookup tables (orbit shapes) to be Lookup::get_instance().load(); However there is still a segfault after fixing that. Not sure why. On Thu, Sep 22, 2016 at 9:55 PM, Vatsal Panwar [email protected]
Dr Brendon J. Brewer |
Thanks for running the code yourself. I made a modification in my repository to the MyModel.cpp (uncommented the part to check if the log likelihood is nan or inf), took the number of particles as 1, and tried to run it again. It still gives me segmentation fault for a few retries even for this case, before starting to run in the latest attempt. |
There is something wrong with the orbit files. Try running orbits.py to On Thu, Sep 22, 2016 at 10:54 PM, Vatsal Panwar [email protected]
Dr Brendon J. Brewer |
It started working for me for one particle. Will regenerate the orbits and run it again once I am done with this run. Thanks! |
Hi Brendon,
After having successfully built an RJObject model for modelling the radial velocities (using the model from gp_quasiperiodic_branch of eggplantbren/Exoplanet as a template adapted to run with DNest4), I keep getting a segmentation fault error when I execute main.cpp .
The problem persists even when I am using the suggested values for the OPTIONS file (as given in Brewer and Mackey 2016). I suspect it might be due to the unusually high value of seed being used for the random number generator. Can you please help me figure out how I might solve this?
Vatsal
The text was updated successfully, but these errors were encountered: