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

Verbose and quiet output flags #41

Open
gully opened this issue Jan 21, 2016 · 3 comments
Open

Verbose and quiet output flags #41

gully opened this issue Jan 21, 2016 · 3 comments

Comments

@gully
Copy link
Collaborator

gully commented Jan 21, 2016

The problem: The code prints lots of info to standard out. Some users might want more or less info, or different info.

Suggested solution: Provide a flag for verbose or quite output. The default can be the existing setup, or whatever is deemed optimal.

@gully gully mentioned this issue Mar 11, 2016
7 tasks
@gully
Copy link
Collaborator Author

gully commented Mar 11, 2016

I experimented with custom terminal output, namely aligning the sample positions and printing accept/reject in a single line. Looks like this:

screen shot 2016-03-11 at 1 15 19 pm

@iancze
Copy link
Collaborator

iancze commented Mar 15, 2016

It is true that the current sampling routines are a bit verbose for a default option.

I like your idea to provide a verbose flag with the output you've demonstrated. I could see how this might be helpful to quickly identify if the tuning of the MH jumps is on the right track or not.

@gully
Copy link
Collaborator Author

gully commented Mar 30, 2016

I liked that blog post a lot! So yeah, a good default would be no output 🔇, and then users could toggle a flag if they really had to see what was going on. Of course the log.log file could have some of this information too. In either case, a sane formatting scheme will help sort out the significant digits from the insignificant ones.

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

No branches or pull requests

2 participants