Documentation overhaul

Vegeta's documentation today is OK, but it can be substantially improved. This issue is meant to track ideas and needs for better documentation.

examples/ directory

All common (or not so common) recipes and examples ought to be captured in an appropriately named file in the examples/ directory, be they CLI or library related.

The README should be reduc

I can't find any other explanation or formulas for results like median, average, min/max, req/sec in documentation, readme or web page. On the documentation page I tried basic scenario to search result/s and get no relevant page.

I found this question on stackoverflow, so I'm not only one who didn't understand it
https://stackoverflow.com/questions/39665250/locust-result-summary-how-to-underst

For each Job, it adds plots about density, cumulative mean, and so on. But two files are named BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--density.png and BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--facetDensity.png, with the -- instead of single. Like some iteration variable is empty (since later there are names with -Default-
![image](https://user-images.github

Describe the bug
When running mnist_blackbox.py, problem occurs while training substitue model.

I realized that after epoch #0, the training log([INFO ~~~) didn't show up. So I made a small change in cleverhans/train.py(below picture) to catch exception and got above result

!

I stumbled across <interaction> and ts_interaction_server, but I'm not sure what the use case is or how it is supposed to be used.

Has anyone used this recently and can add some documentation? Or explain to me how this works and I'll write something.

/cc @nniclausse

Hi, I'm looking around for test my linux based machine whit docker but don't see the 'how to' anywhere, someone know how to run the official test suite?

http://www.phoronix-test-suite.com/documentation/

thanks in advance,

As far as I understand according to #228 the preparation code output should be stripped of any and all <script> tags, yet it only strips the first script tag it finds. This is due to String.prototype.replace() stopping after the first match unless a RegExp with the global flag is used.

However d

Hi. It can make sense having a structure like this (base on phpunit) to add phpbench in complex structure:

tests/src/module/a/controller/AControllerTest.php
tests/src/module/a/controller/BControllerTest.php
tests/src/module/a/controller/CControllerTest.php

to:
tests/src/module/a/controller/AControllerBench.php
tests/src/module/a/controller/AControllerTest.php
tests/src/module/a/con

For different use cases, like bencheeorg/benchee_html#10 it'd be great to have statistics about statistics - what I'd call "meta statistics" - although there's probably some better real statistics name for this :)

What should be in there (that I know of so far):

• job size (how many jobs are in there)
• minimum of run times over all jobs
• maximum of run times over all jobs

This should be

It would be good to have some (at least 3-5) tutorials that teach new users what LIKWID can do and how to use it properly. From my experience as a user and FOSS developer, tutorials like deal.ii's are good thing to have. In that case we have first 5 that has to be read in a sequence by users, and then things start to branch off by t

Hi there,

I'm trying to figure out what the numbers in parentheses outputted for each stat value in the table mean.

Looking at the code it seems like its happening over here : https://github.com/ionelmc/pytest-benchmark/blob/2ed70632a38909ced0935c010b6696679a28c412/src/pytest_benchmark/table.py#L39

I'm not sure what pos/total means and what I should gleam from those values in the parent

ZSTD expanded their range of compression levels to include negative integers. The current "max" (-5) pushes it into LZ4 territory. I would make a pull request, but I'm not sure how many additional levels you want to test by default.

The changes in #65 need to be documented.

This might be a detail but I believe it's preferable to use the term "Fabric" rather than "Hyperledger".
While the full name of the technology is "Hyperledger Fabric" the first part comes from the foundation that owns the project and has such naming convention for all of its inventions - "Hyperledger Calliper", "Hyperledger Sawtooth", "Hyperledger Aries" etc.
Using name "Fabric" would not only

Specifically, Mocha seems to perform lots of operations like Array#includes and Array#indexOf on frozen arrays while setting up its environment and executing its tests.

It would be good to have this pattern reflected in the WTB.

Ref. https://docs.google.com/document/d/1X6zO5F_Zojizn2dmo_ftaOWsY8NltPHUhudBbUzMxnc/edit.