Describe the bug
Trying to resume a previous MCMC fit that used Gaia-Hipparcos, Relative Astrometry, and RV. After initializing a new a MCMC sampler (with the path to the previous hdf5 file passed through the keyword "prev_result_filename") the sampler fails to save the the result (with results.save_results) and gives the below error.
FileNotFoundError: [Errno 2] No such file or directory: 'thisisprettyhackysorrylmao'
Expected behavior
When creating a new MCMC sampler, according to the orbitize! docs, if a filename to an HDF5 containing a .Results object is passed to prev_result_filename, the MCM will restart from where it left off. After running the MCMC sampler for the specified number of burn-in steps and posterior samples, the results should be saved to an HDF5 named "Hip21547_RERUN_results.hdf5". and then print a message saying the results were saved there to that filename.
Screenshots
Desktop (please complete the following information):
OS: Rocky Linux release 8.9 (Green Obsidian)
orbitize! Version3.0.0
Additional context
@wbalmer has been helping me out.
Describe the bug Trying to resume a previous MCMC fit that used Gaia-Hipparcos, Relative Astrometry, and RV. After initializing a new a MCMC sampler (with the path to the previous hdf5 file passed through the keyword "prev_result_filename") the sampler fails to save the the result (with results.save_results) and gives the below error.
FileNotFoundError: [Errno 2] No such file or directory: 'thisisprettyhackysorrylmao'
To Reproduce 1: Click on this GitHub gist
Expected behavior When creating a new MCMC sampler, according to the orbitize! docs, if a filename to an HDF5 containing a .Results object is passed to prev_result_filename, the MCM will restart from where it left off. After running the MCMC sampler for the specified number of burn-in steps and posterior samples, the results should be saved to an HDF5 named "Hip21547_RERUN_results.hdf5". and then print a message saying the results were saved there to that filename.
Screenshots
Desktop (please complete the following information):
Additional context @wbalmer has been helping me out.