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

Print out settings when run #76

Closed
pipitone opened this issue Apr 11, 2016 · 8 comments
Closed

Print out settings when run #76

pipitone opened this issue Apr 11, 2016 · 8 comments

Comments

@pipitone
Copy link
Collaborator

I wonder if it might be helpful to have a tiny display of the actual settings used (just in case users don't realize what the defaults are, etc), e.g.

$ qbatch -w 1:00:00 commands.txt
Processors requested per job (--ppj): 8
      Processes run in parallel (-j): 1
               Commands per job (-c): 8
                       Walltime (-w): 1:00:00 
                       Other options: none

Thoughts?

@gdevenyi
Copy link
Member

Yes, that looks good, however maybe it should only do so under verbose?

pipitone added a commit that referenced this issue Apr 12, 2016
Only active in verbose mode. See issue #76
@gdevenyi
Copy link
Member

Followup here, I like the initial implementation, but should it be more verbose as to settings, and should those settings only be printed if relevant? i.e. in local mode, certain things suppressed?

@gdevenyi
Copy link
Member

gdevenyi commented Jun 9, 2016

If... we were to implement a config file, this could print out the internal config state.

@pipitone
Copy link
Collaborator Author

Sure... but I don't see how the config file has anything to do with this
because this issue is about displaying the configuration qbatch is in
(because of some base config plus command line options) when your jobs
were submitted, right?

@gdevenyi
Copy link
Member

Right, I was just thinking we could hijack the configparser saving features to print to screen, no custom formatting or such required, would also allow a copy-paste to save that config (if we go with that).

@pipitone
Copy link
Collaborator Author

Yeah, that's a nice benefit: config display that doubles as a usable
config file. As long as it doesn't get in the way of actually being
readable/meaningful for the humans. :-)

@gdevenyi
Copy link
Member

Looks like configparser config files are nice and readable:
http://effbot.org/librarybook/configparser.htm

@gdevenyi
Copy link
Member

Merged into #96

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