Skip to content
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

Reduce memory and disk-space usage of HypoFitResult #827

Open
thehrh opened this issue Sep 26, 2024 · 0 comments
Open

Reduce memory and disk-space usage of HypoFitResult #827

thehrh opened this issue Sep 26, 2024 · 0 comments

Comments

@thehrh
Copy link
Contributor

thehrh commented Sep 26, 2024

  • an analyser making use of

    def fit_recursively(
    is unable to switch off recording and storing of fit/minimiser history, best-fit asimov template, detailed metric maps

  • depending on nature of analysis, this can give rise to huge memory footprint, and, if no manual purging is done before storing, may take up unnecessary disk space

  • unfortunately, there is little documentation explaining the design choices behind the HypoFitResult class and its integration into the fitting functions (e.g., it's not obvious to me that the deserialisation mechanism should require all attributes in _state_attrs to be present)

  • setting blindness > 0 suppresses storing fit_history, but would have other unintended side effects for an analyser only interested in reducing analysis resource usage

  • introduce a parameter to the call to fit_recursively which will force the fit to omit the most detailed information?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant