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

Logging/diagnostics support #4

Open
blackwer opened this issue Jan 11, 2022 · 1 comment
Open

Logging/diagnostics support #4

blackwer opened this issue Jan 11, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@blackwer
Copy link
Member

Class has literally zero reporting facilities. Use spdlog or other logging to report status if needed.

@blackwer blackwer added the enhancement New feature or request label Jan 11, 2022
@blackwer blackwer changed the title Logging support Logging/diagnostics support Feb 16, 2022
@blackwer
Copy link
Member Author

See #32 for notes about useful diagnostic info.

a diagnostic output flag option that sends summary to stdout about: how many boxes used, max tree depth, total # func queries used, time taken, threads used, etc.
another diagnostic flag that dumps (to file or stdout) a list of the coords and vals of the func queries. Then someone could read this file and plot it to show the box structure and where baobzi struggled.
robustness (gracefully reporting that max-depth was reached, and not to trust the func eval in the following box regions...) when function appears to have a singularity.
you might want to look at SGJ's hcubature on github - the interface not the inner workings, and the interface for adaptive integration in matlab (quad2d, integral2) eg some of its reporting and failure handling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant