-
Notifications
You must be signed in to change notification settings - Fork 9
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 LB specification at startup (from file) #984
Labels
Comments
@cz4rs Please prioritize this as it is needed in the EMPIRE application for the 1.0.0 release to help application developers who are using VT |
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
- allow printing LB specification during startup - update documentation with new option - make documentation consisten with usage info - remove --vt_lb_file option and rely only on --vt_lb_file_name
cz4rs
added a commit
that referenced
this issue
Aug 13, 2020
- allow printing LB specification during startup - make documentation consistent with usage info - remove --vt_lb_file option and rely only on --vt_lb_file_name
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
…printing - improve naming and description of the option - improve printing code - use colors when printing specification - use map for storing spec entries (to have them sorted)
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
…printing - improve naming and description of the option - improve printing code - use colors when printing specification - use map for storing spec entries (to have them sorted)
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
…printing - improve naming and description of the option - improve printing code - use colors when printing specification - use map for storing spec entries (to have them sorted)
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
- allow printing LB specification during startup - make documentation consistent with usage info - remove --vt_lb_file option and rely only on --vt_lb_file_name
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
…printing - improve naming and description of the option - improve printing code - use colors when printing specification - use map for storing spec entries (to have them sorted)
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
…printing - improve naming and description of the option - improve printing code - use colors when printing specification - use map for storing spec entries (to have them sorted)
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
cz4rs
added a commit
that referenced
this issue
Aug 14, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Needs to be Done?
Currently, VT prints by default in the header what the LB options are, including if the LB is using a specification file.
However, it's impossible to know if VT parsed the file correctly and what VT is planning to do from what it read in the specification file.
Add a new opt-in option that prints at startup the LB specification as parsed in human-readable format.
Doc link: https://darma-tasking.github.io/docs/html/lb-manager.html#lb-specification-file
The text was updated successfully, but these errors were encountered: