Tim Zaman

Should be straightforward using the work done in https://github.com/NVIDIA/DIGITS/pull/1009 Requires #4, automatic node and edge placement because the .lua does not have visual (x,y) coordinate system information.

Should be straightforward using the work done in https://github.com/NVIDIA/DIGITS/pull/1009 Requires #4, automatic node and edge placement because the .prototxt does not have visual (x,y) coordinate system information.

See title.

The layers and their args should preferably be formatted to `.json`. ## Listing Caffe Layers - Through python and https://github.com/BVLC/caffe/pull/2930 (from https://github.com/caffe2/caffe2/issues/42#issuecomment-243251598); Example `.json` output: https://github.com/TimZaman/dagstudio/blob/master/tests/caffe-all-layers.json ## Listing Caffe args...

(Dynamically) Retrieve Torch Layers and their arguments

2

Listing torch layers is pretty easy by listing the contents of `nn` for example. Any recommendations on getting the arguments of the constructor of the layers?

[asas] Although this cyclical behavior is supported since #1, this ^ isn't pretty.

Time sync of radiant/dire teams upon reset not stable.

10

Ex (0.3.2): ``` ValueError: dota_time discrepancy in depleting initial worldstate queue. at reset (/root/dotaservice/dotaservice/dotaservice.py:439) at request_handler (/root/.local/lib/python3.7/site-packages/grpclib/server.py:327) ```

[Bug]: Infiniband bytes overreported by 4x

8

### Bug description A bandwidth test between nodes A and B reveals a speed of 52Gb/s, while Netdata reveals an excess of 200Gb/s. See https://github.com/prometheus/node_exporter/issues/573 - prometheus exporter made the...

If a core is masked through affinity, it will be correctly skipped by the process, and in the stdout it will be correctly identified as skipped. However, the csv output...