in chatting with @Swarali-glitch , i found a small bug where the initial guess for the dm parameter was being always set to 0.0, even if you supply a non-zero guess through the --dm option or if you supplied an existing fitburst JSON file to use as the initial guess. this bug ultimately led to suboptimal fitting of the scattering timescale (if you set --fit scattering_timescale), which is the trickier parameter to measure due to the non-smoothly-varying function used to model the effect.
i also added a few more options that allows the user to change the initial guesses of all possible parameters, if desired.
in chatting with @Swarali-glitch , i found a small bug where the initial guess for the
dmparameter was being always set to 0.0, even if you supply a non-zero guess through the--dmoption or if you supplied an existingfitburstJSON file to use as the initial guess. this bug ultimately led to suboptimal fitting of the scattering timescale (if you set--fit scattering_timescale), which is the trickier parameter to measure due to the non-smoothly-varying function used to model the effect.i also added a few more options that allows the user to change the initial guesses of all possible parameters, if desired.