Currently both collections utilize the information from fit_entry as specified in kariba_model.py; however, the fit_entry info is written in different formats in all_fits and best_fits; furthermore some of the fit_entries attributes are written weighted/unweighted when viewed as a best_fit or respectively all_fits members. Introduce a fit_entry object that would handle the interaction between all_fits, best_fits and each model properties.
Currently both collections utilize the information from fit_entry as specified in kariba_model.py; however, the fit_entry info is written in different formats in all_fits and best_fits; furthermore some of the fit_entries attributes are written weighted/unweighted when viewed as a best_fit or respectively all_fits members. Introduce a fit_entry object that would handle the interaction between all_fits, best_fits and each model properties.