logboard
Monitor and Compare Logs on Browser/Terminal.
Description
Inspired by tensorboard, grip and notable, all of which serve light-weight GUI by
- only using static files (e.g., markdown files without DB);
- single command (e.g.,
tensorboard --logdir logs/andgrip README.md).
Why not tensorboard?
I also use tensorboard in addition to this tool.
But currently tensorboard doesn't support comparing different configurations
for each log (e.g., git-hash of the code, learning rate, training strategy).
logboard is a kind of extra plugin to tensorboard
(but you need to run in different terminal, unfortunately).
I expect this kind of feature will be included in tensorboard in the future.
Installation
pip install logboard
Usage
Browser (logboard --logdir logs/)
$ cd examples
$ cat logs/20190310_093252.724597/args
{
"loglevel": "info",
"gpu": 0,
"seed": 0,
"class_ids": [
1
],
"lr": 0.001,
"timestamp": "2019-03-10T09:32:52.724597",
"out": "/home/wkentaro/logboard/examples/logs/20190310_093252.724597",
"hostname": "computer1",
"githash": "b48ce48"
}
# similar to tensorboard --logdir logs/
$ logboard --logdir logs/ --filter out timestamp loglevel gpu seed 'lr .*' '.*main/loss.*(max)' '.*loss_.*'
Terminal (logtable --logdir logs/)
$ cd examples
$ logtable --logdir logs --filter out timestamp loglevel gpu seed 'lr .*' '.*main/loss.*(max)' '.*loss_.*'
* Log directory: logs
╒════╤════════════════════════╤═════════╤═════════════╤════════════════╤═══════════════════╤═════════════╤═══════════╤════════════╤═══════╤══════════════╤═══════════════╕
│ │ log_dir │ epoch │ iteration │ elapsed_time │ updated_at │ class_ids │ githash │ hostname │ lr │ main/ │ validation/ │
│ │ │ │ │ │ │ │ │ │ │ loss (min) │ main/ │
│ │ │ │ │ │ │ │ │ │ │ │ loss (min) │
╞════╪════════════════════════╪═════════╪═════════════╪════════════════╪═══════════════════╪═════════════╪═══════════╪════════════╪═══════╪══════════════╪═══════════════╡
│ 0 │ 20190310_093252.724597 │ 1 │ 1740 │ 1:47:02 │ 88 days, 14:24:22 │ [1] │ b48ce48 │ computer1 │ 0.001 │ 0.0088 │ 0.18 │
│ │ │ │ │ │ │ │ │ │ │ (1, 1580) │ (0, 880) │
├────┼────────────────────────┼─────────┼─────────────┼────────────────┼───────────────────┼─────────────┼───────────┼────────────┼───────┼──────────────┼───────────────┤
│ 1 │ 20190310_093829.691289 │ 1 │ 1720 │ 1:45:37 │ 88 days, 14:24:22 │ [1] │ f766b97 │ computer2 │ 0.001 │ 0.012 │ 0.19 │
│ │ │ │ │ │ │ │ │ │ │ (1, 1620) │ (0, 440) │
╘════╧════════════════════════╧═════════╧═════════════╧════════════════╧═══════════════════╧═════════════╧═══════════╧════════════╧═══════╧══════════════╧═══════════════╛
Metadata
Release files for logboard 0.5.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| logboard-0.5.11.tar.gz | 10.6 kB | Without provenance | Details for logboard-0.5.11.tar.gz |
Release files / logboard-0.5.11.tar.gz
| Download URL | logboard-0.5.11.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5e17a62fa7459626b4bdf69913a63264d9972603abc99b80b1a5d882e751f42
|
|
BLAKE2b-256 checksum How to use checksums |
0069f8598920b304a3bbbfb5ca4d70640109e69b14f414fa8e437d13bf21b959
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.8.0 tqdm/4.31.1 CPython/3.7.4
|
Security for logboard 0.5.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.