| Index: trunk/tools/wsor/editor_lifecycle/README.rst |
| — | — | @@ -43,7 +43,7 @@ |
| 44 | 44 | |
| 45 | 45 | 1. Fetch user rates using `ratesnobots.sql`:: |
| 46 | 46 | |
| 47 | | - mysql -BNe < ratesnobots.sql > rates.tsv |
| | 47 | + mysql -BN < ratesnobots.sql > rates.tsv |
| 48 | 48 | |
| 49 | 49 | Note: To be able to run this query, you must be able to access an internal |
| 50 | 50 | resource of the Wikimedia Foundation, see here for more information: |
| — | — | @@ -62,9 +62,12 @@ |
| 63 | 63 | |
| 64 | 64 | SELECT DISTINCT ug_user FROM user_groups where ug_group = "bot" |
| 65 | 65 | |
| 66 | | -2. Use `mkcohort` to make cohorts. This will create a file where each line is a |
| 67 | | - cohort, specified by the first two columns. Columns after the second are the |
| 68 | | - IDs of users. |
| | 66 | +2. Use `mkcohort` to define the cohorts. You can specify the temporal resolution |
| | 67 | + (yearly, daily, monthly) and other parameters such as minimum edit count and |
| | 68 | + minimum lifespan. This will create a tab-separated file where each line is a |
| | 69 | + cohort. The cohort specification (period, activity rate) is reported in the |
| | 70 | + first two columns. All columns after the first two (if any) represent IDs of |
| | 71 | + users. |
| 69 | 72 | |
| 70 | 73 | 3. Use `fetchrates` to fetch daily edit counts using the cohort data. See |
| 71 | 74 | `sge/rates.sh` if you want to run this query from within the toolserver. |