Skip to content

Commit fff9224

Browse files
Merge pull request #71 from Blockchain-Technology-Lab/docs_update
Docs update
2 parents 832c9c5 + 9e6944a commit fff9224

File tree

3 files changed

+33
-35
lines changed

3 files changed

+33
-35
lines changed

README.md

-2
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,6 @@ The tool is actively maintained by the following developers:
8585
- [Dimitris Karakostas](https://github.com/dimkarakostas)
8686
- [Christina Ovezik](https://github.com/LadyChristina)
8787

88-
*Note*: When opening a Pull Request, you must request a review from at least *2*
89-
people in the above list.
9088

9189
## License
9290

config.yaml

+20-19
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,26 @@ analyze_flags:
3535
exclude_below_fees: false
3636
exclude_below_usd_cent: true
3737

38+
# The snapshots for which an analysis should be performed.
39+
# Each snapshot is a string of the form YYYY-MM-DD.
40+
# If granularity is also set, then the analysis will run on the timeframe of the two farthest snapshots.
41+
snapshot_dates:
42+
- "2010"
43+
- "2023"
44+
45+
# The granularity for the analysis when two dates are provided in the --snapshot_dates argument (which are then interpreted as start and end dates).
46+
# It can be one of: "day", "week", "month", "year", or empty. If empty, then only the snapshots for the given dates will be analyzed.
47+
granularity: "month"
48+
49+
input_directories: # Paths to directories that contain raw input data
50+
- ./input
51+
52+
# Paths to directories of snapshot db files; either absolute or relative from run.py.
53+
# The first path will be used to write newly created dbs and the output of runs
54+
output_directories:
55+
- ./output
56+
57+
3858
# Plot flags
3959
plot_parameters:
4060
plot: true
@@ -75,22 +95,3 @@ plot_parameters:
7595
exclude_contract_addresses:
7696
- true
7797
- false
78-
79-
# The snapshots for which an analysis should be performed.
80-
# Each snapshot is a string of the form YYYY-MM-DD.
81-
# If granularity is also set, then the analysis will run on the timeframe of the two farthest snapshots.
82-
snapshot_dates:
83-
- "2010"
84-
- "2023"
85-
86-
# The granularity for the analysis when two dates are provided in the --snapshot_dates argument (which are then interpreted as start and end dates).
87-
# It can be one of: "day", "week", "month", "year", or empty. If empty, then only the snapshots for the given dates will be analyzed.
88-
granularity: "month"
89-
90-
# Paths to directories of snapshot db files; either absolute or relative from run.py.
91-
# The first path will be used to write newly created dbs and the output of runs
92-
output_directories:
93-
- ./output
94-
95-
input_directories: # Paths to directories that contain raw input data
96-
- ./input

docs/setup.md

+13-14
Original file line numberDiff line numberDiff line change
@@ -24,45 +24,46 @@ To run the tool simply do:
2424
python run.py
2525

2626
The execution is controlled and parameterized by the configuration file
27-
`config.yml` as follows.
27+
`config.yaml` as follows:
2828

29-
`metrics` defines the metrics that should be computed in the analysis. By
30-
default all supported metrics are included here (to add support for a new metric
29+
`metrics` defines the metrics that will be computed in the analysis. By
30+
default, [all supported metrics](https://blockchain-technology-lab.github.io/tokenomics-decentralization/metrics) are included here (to add support for a new metric
3131
see the [conributions
3232
page](https://blockchain-technology-lab.github.io/tokenomics-decentralization/contribute/)).
3333

34-
`ledgers` defines the ledgers that should be analyzed. By default, all supported
34+
`ledgers` defines the ledgers that will be analyzed. By default, all supported
3535
ledgers are included here (to add support for a new ledger see the [conributions
3636
page](https://blockchain-technology-lab.github.io/tokenomics-decentralization/contribute/)).
3737

38-
`execution_flags` defines various flags that control the data handling:
38+
`execution_flags` defines various flags that control the data handling (all set to false by default):
3939

40-
* `force_map_addresses`: the address helper data from the directory
40+
* `force_map_addresses`: if set to true, the address helper data from the directory
4141
`mapping_information` is re-computed; you should set this flag to true if the
4242
data has been updated since the last execution for the given ledger
43-
* `force_map_balances`: the balance data of the ledger's addresses is
43+
* `force_map_balances`: is set to true, the balance data of the ledger's addresses is
4444
recomputed; you should set this flag to true if the data has been updated
4545
since the last execution for the given ledger
46-
* `force_analyze`: the computation of a metric is recomputed; you should set
46+
* `force_analyze`: if set to true, the computation of a metric is recomputed; you should set
4747
this flag to true if any type of data has been updated since the last
4848
execution for the given ledger
4949

5050
`analyze_flags` defines various analysis-related flags:
5151

5252
* `clustering`: a boolean that determines whether addresses will be clustered into entities
53-
(as defined in the mapping information). If set to False, no clustering takes
53+
(as defined in the mapping information). If set to false, no clustering takes
5454
place and the addresses are treated as distinct entities.
55-
* `top_limit_type`: a string of two values (`absolute` or `percentage`) that
55+
* `top_limit_type`: a string that can take one of two values (`absolute` or `percentage`) that
5656
enables applying a threshold on the addresses that will be considered
5757
* `top_limit_value`: the value of the top limit that should be applied; if 0,
5858
then no limit is used (regardless of the value of `top_limit_type`); if the
5959
type is `absolute`, then the `top_limit_value` should be an integer (e.g., if
6060
set to 100, then only the 100 wealthiest entities/addresses will be considered
6161
in the analysis); if the type is `percentage` the the `top_limit_value` should
62-
be an integer (e.g., if set to 0.50, then only the top 50% of wealthiest
62+
be a value between 0 and 1 (e.g., if set to 0.50, then only the top 50% of wealthiest
6363
entities/addresses will be considered)
6464
* `exclude_contract_addresses`: a boolean value that enables the exclusion of
6565
contract addresses from the analysis
66+
* `exclude_below_fees`: a boolean value that enables the exclusion of addresses, the balance of which at the analyzed point in time was less than the average transaction fee
6667
* `exclude_below_usd_cent`: a boolean value that enables the exclusion of
6768
addresses, the balance of which at the analyzed point in time was less than
6869
$0.01 (based on the historical price information in the directory
@@ -88,6 +89,4 @@ contain the mapping information and analyzed data. The first entry in the output
8889
directories is also used to store the output files of the analysis and the
8990
plots.
9091

91-
Finally, `plot_parameters` contains various parameters that control the type and
92-
data that will be produced as plots.
93-
...
92+
Finally, `plot_parameters` contains various parameters that control whether plots will be produced for the results and for which configurations.

0 commit comments

Comments
 (0)