This should be randomly generated. However, we have to be able to link different records from a user to each other.
Date
We go for a granularity of one day. This is fine-grained enough for our simulation but should be coarse enough so that we can’t identify single payments.
Balance start of day
The user balance at the start of day
Balance end of day
The user balance at the end of day
Balance max day
The maximum balance of that user throughout the day
Balance min day
The minimum balance of that user throughout the day
Total flow out
The total amount that has been paid by the user during that day
Total flow in
The total amount that has been been received by the user during that day
The data should contain the following columns:
| Key | Value |
| - | - |
| User id | This should be randomly generated. However, we have to be able to link different records from a user to each other.|
| Date | We go for a granularity of one day. This is fine-grained enough for our simulation but should be coarse enough so that we can’t identify single payments. |
| Balance start of day | The user balance at the start of day |
| Balance end of day | The user balance at the end of day |
| Balance max day | The maximum balance of that user throughout the day |
| Balance min day | The minimum balance of that user throughout the day |
| Total flow out | The total amount that has been paid by the user during that day |
| Total flow in | The total amount that has been been received by the user during that day |
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The data should contain the following columns: