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

Report progress for refinement and merging #368

Open
GoogleCodeExporter opened this issue May 4, 2015 · 0 comments
Open

Report progress for refinement and merging #368

GoogleCodeExporter opened this issue May 4, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

When running Synoptic on large logs, there's no way of gauging how long model 
inference might take (30 seconds? 5 hours?). It would be very useful for large 
experiments to have some (even very approximate) progress notification.

For refinement, adding an approximate progress indicator could simply involve 
recording the number of invariant violations when refinement first starts 
(initialViolations) and occasionally reporting:
"Refinement approximately (currentNumViolations / initialViolations * 100)% 
complete"

For coarsening, we could start by computing or approximating the number of 
merges that will be attempted (mergesToAttempt). We could compute it exactly by 
counting the number of nodes of each event type in the partition graph and 
calculating the number of permutations for each, or we could approximate it by 
calculating the permutations of something like (numTotalNodes / numEventTypes), 
which simplifies the problem by assuming nodes are equally distributed among 
event types. Either way, we could then occasionally report (attemptedMerges / 
mergesToAttempt).

Original issue reported on code.google.com by [email protected] on 12 Mar 2014 at 4:26

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