Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
software:singularity:caviness [2018-08-10 23:21] – [Common Singularity commands] anita | software:singularity:caviness [2024-08-27 17:51] (current) – anita | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======= Singularity on Caviness ====== | + | ======= |
===== Build a Singularity container ===== | ===== Build a Singularity container ===== | ||
Line 58: | Line 58: | ||
Singularity tensorflow.simg: | Singularity tensorflow.simg: | ||
+ | usage: tensorboard [-h] [--logdir PATH] [--host ADDR] [--port PORT] | ||
+ | | ||
+ | [--db URI] [--inspect] [--tag TAG] [--event_file PATH] | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
- | USAGE: /usr/local/bin/ | + | TensorBoard is a suite of web applications for inspectinng and understanding |
- | + | your TensorFlow runs and graphs. https://github.com/tensorflow/ | |
- | Try --helpfull to get a list of all flags. | + | |
Singularity tensorflow.simg: | Singularity tensorflow.simg: | ||
Cpus_allowed_list: | Cpus_allowed_list: | ||
- | Singularity tensorflow.simg: | + | Singularity tensorflow.simg: |
+ | exit | ||
+ | [traine@r00n45 ~]$ | ||
</ | </ | ||
Line 72: | Line 82: | ||
=== Locale error === | === Locale error === | ||
- | If you experience the error below after starting a particular container, then it is likely due your current locale not being supported in this particular container' | + | If you experience the error below after starting a particular |
<code bash> | <code bash> | ||
+ | [traine@r00n45 ~]$ vpkg_require singularity | ||
+ | Adding package `singularity/ | ||
[traine@r00n45 ~]$ singularity shell tensorflow.simg | [traine@r00n45 ~]$ singularity shell tensorflow.simg | ||
Singularity: | Singularity: | ||
Line 105: | Line 117: | ||
</ | </ | ||
- | Of course in this particular case, checking | + | Of course in this particular case, the locale |
<code bash> | <code bash> | ||
+ | [traine@r00n45 ~]$ vpkg_require singularity | ||
+ | Adding package `singularity/ | ||
[tainne@r00n45 ~]$ LANG=C.UTF-8 singularity shell tensorflow.simg | [tainne@r00n45 ~]$ LANG=C.UTF-8 singularity shell tensorflow.simg | ||
Singularity: | Singularity: | ||
Line 125: | Line 139: | ||
your TensorFlow runs and graphs. https:// | your TensorFlow runs and graphs. https:// | ||
- | optional arguments: | + | [[ lots of additional information displayed |
- | -h, --help | + | |
- | --logdir PATH | + | |
- | TensorFlow event files that it can display. | + | |
- | TensorBoard will recursively walk the directory | + | |
- | structure rooted at logdir, looking for .*tfevents.* | + | |
- | files. You may also pass a comma separated list of log | + | |
- | directories, | + | |
- | directory. You can also assign names to individual log | + | |
- | directories by putting a colon between the name and | + | |
- | the path, as in: `tensorboard | + | |
- | --logdir=name1:/ | + | |
- | --host ADDR What host to listen to. Defaults to serving on all | + | |
- | interfaces. Other commonly used values are 127.0.0.1 | + | |
- | (localhost) and :: (for IPv6). | + | |
- | --port PORT Port to serve TensorBoard on (default: 6006) | + | |
- | --purge_orphaned_data BOOL | + | |
- | Whether to purge data that may have been orphaned due | + | |
- | to TensorBoard restarts. Setting | + | |
- | --purge_orphaned_data=False can be used to debug data | + | |
- | disappearance. (default: True) | + | |
- | --reload_interval SECONDS | + | |
- | How often the backend should load more data, in | + | |
- | seconds. Set to 0 to load just once at startup and a | + | |
- | negative number to never reload at all. (default: 5.0) | + | |
- | --db URI | + | |
- | --inspect | + | |
- | useful when no data is shown on TensorBoard, | + | |
- | data shown looks weird. Example usage: `tensorboard | + | |
- | --inspect --logdir mylogdir --tag loss` See | + | |
- | tensorflow/ | + | |
- | more info. | + | |
- | --tag TAG tag to query for; used with --inspect | + | |
- | --event_file PATH The particular event file to query for. Only used if | + | |
- | --inspect is present and --logdir is not specified. | + | |
- | --path_prefix PATH An optional, relative prefix to the path, e.g. | + | |
- | "/ | + | |
- | being located at localhost: | + | |
- | under default settings. A leading slash is required | + | |
- | when specifying the path_prefix, | + | |
- | slashes can be omitted. The path_prefix can be | + | |
- | leveraged for path based routing of an elb when the | + | |
- | website base_url is not available e.g. | + | |
- | " | + | |
- | --window_title TEXT | + | |
- | --max_reload_threads COUNT | + | |
- | The max number of threads that TensorBoard can use to | + | |
- | reload runs. Not relevant for db mode. Each thread | + | |
- | reloads one run at a time. | + | |
- | --samples_per_plugin SAMPLES_PER_PLUGIN | + | |
- | An optional comma separated list of | + | |
- | plugin_name=num_samples pairs to explicitly specify | + | |
- | how many samples to keep per tag for that plugin. For | + | |
- | unspecified plugins, TensorBoard randomly downsamples | + | |
- | logged summaries to reasonable values to prevent out- | + | |
- | of-memory errors for long running jobs. This flag | + | |
- | allows fine control over that downsampling. Note that | + | |
- | 0 means keep all samples of that type. For instance | + | |
- | " | + | |
- | images. Most users should not need to set this flag. | + | |
- | + | ||
- | profile plugin: | + | |
- | --master_tpu_unsecure_channel ADDR | + | |
- | IP address of " | + | |
- | trace data through tpu profiler analysis grpc. The | + | |
- | grpc channel is not secured. | + | |
- | + | ||
- | debugger plugin: | + | |
- | --debugger_data_server_grpc_port PORT | + | |
- | The port at which the non-interactive debugger data | + | |
- | server should receive debugging data via gRPC from one | + | |
- | or more debugger-enabled TensorFlow runtimes. No | + | |
- | debugger plugin or debugger data server will be | + | |
- | started if this flag is not provided. This flag | + | |
- | differs from the `--debugger_port` flag in that it | + | |
- | starts a non-interactive mode. It is for use with the | + | |
- | " | + | |
- | flag is mutually exclusive with `--debugger_port`. | + | |
- | --debugger_port PORT The port at which the interactive debugger data server | + | |
- | (to be started by the debugger plugin) should receive | + | |
- | debugging data via gRPC from one or more debugger- | + | |
- | enabled TensorFlow runtimes. No debugger plugin or | + | |
- | debugger data server will be started if this flag is | + | |
- | not provided. This flag differs from the | + | |
- | `--debugger_data_server_grpc_port` flag in that it | + | |
- | starts an interactive mode that allows user to pause | + | |
- | at selected nodes inside a TensorFlow Graph or between | + | |
- | Session.runs. It is for use with the interactive | + | |
- | Debugger Dashboard. This flag is mutually exclusive | + | |
- | with `--debugger_data_server_grpc_port`. | + | |
- | Singularity tensorflow.simg: | + | |
+ | Singularity tensorflow.simg: | ||
+ | exit | ||
+ | [traine@r00n45 ~]$ | ||
</ | </ | ||
- | |||
==== Common Singularity commands ==== | ==== Common Singularity commands ==== |