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

Update print/logging #155

Open
lcgraham opened this issue Mar 21, 2016 · 4 comments
Open

Update print/logging #155

lcgraham opened this issue Mar 21, 2016 · 4 comments
Assignees

Comments

@lcgraham
Copy link
Contributor

Remove print statements and create log files.
Add warning and options (verbosity) for log files. Use a logging module.
Updating warnings when certain algorithmic options occur, e.g., re-normalizing the probability measure because positive probability was assigned to an output event that was not approximated by a contour event. This can be detected at the point of constructing the io_ptr and we may want to generate a log-file containing the output cell(s) (e.g., as identified by point(s) in the output data space defining the cell(s)) that were not approximated either due to insufficient sampling or assigning support of the output density outside of the range of the operator. This is very useful information.

@lcgraham lcgraham modified the milestone: Release Version 2.0 Mar 22, 2016
@lcgraham lcgraham mentioned this issue May 17, 2016
@lcgraham lcgraham self-assigned this May 17, 2016
lcgraham added a commit to lcgraham/BET that referenced this issue May 17, 2016
@lcgraham lcgraham mentioned this issue May 17, 2016
@lcgraham
Copy link
Contributor Author

Serial logs work. There probably needs to be additional work done for logging with mpi4py

@smattis
Copy link
Contributor

smattis commented May 17, 2016

Maybe only log if comm.rank==0 ?

@lcgraham
Copy link
Contributor Author

Maybe, but there might be situations where you want to know what each processor is up to since they sometimes do different things. There are a couple of mpi logging implementations using mpi4py that I've linked above, but I don't think adding the mpi logging need to be taken care of immediately.

@lcgraham lcgraham reopened this Jun 7, 2016
@lcgraham lcgraham removed this from the Release Version 2.0 milestone Aug 9, 2016
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

2 participants