Replies: 1 comment 4 replies
-
emcee with the phoebe backend is inherently computationally expensive. My best advice is to spend the time to ensure that your initializing distributions are as optimized as possible first and that your phase sampling is as coarse as is appropriate for your data/science. If you have access to external high-performance compute resources, that is also very helpful in allowing to multiprocess on more processors. Besides that, there are a few considerations in your setup that you can take to ensure that each forward model is as efficient as possible. These two tutorials (hopefully we'll merge them sometime in the future) cover the most common areas where you can gain performance: Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
Hi, when I try to use phoebe. Emcee to fit with my lightcurve, about 18000 points in this lightcurve. In this case, how can I do not change my computer and speed-up run_solver. I already set
phoebe.multiprocessing_on() phoebe.multiprocessing_set_nprocs(16)
to try to speed-up. but not fortunately, this step also need to spend a few days time to complete, So I want to ask for your help to search one method to speed-upb.add_dataset('lc', times=time, fluxes=flux, sigmas=flux_err, passband='TESS:T', ld_mode='manual', pblum_mode='dataset-scaled', dataset='lc01') b.set_value('ld_mode_bol', component='primary', value='manual') b.set_value('ld_mode_bol', component='secondary', value='manual') b.run_compute(model='tess_observation')
Beta Was this translation helpful? Give feedback.
All reactions