Hello,
On round 57, as I banned an account for 50 shares of plagiarism and even if it was too late to be updated on dvccountdown the correct numbers (received amount) must be now 132.4 shares instead of 182.4 or 1359517 DVC per share instead of 986842.
Regards,
Flam.
PS: @develCuy Ok thanks.
On round 57, as I banned an account for 50 shares of plagiarism and even if it was too late to be updated on dvccountdown the correct numbers (received amount) must be now 132.4 shares instead of 182.4 or 1359517 DVC per share instead of 986842.
Regards,
Flam.
PS: @develCuy Ok thanks.
Are you saying this correction made it into the receiver files but is not shown on DVC Countdown?
Thanks for taking care of that
DVC Countdown will always show the best estimate. This is how it works:
DVC Countdown runs the marketing and account.py files daily, and makes a best guess until the end of round. The real end of round happens when Unthinkingbit runs the official version and updates the charity github (https://github.com/Unthinkingbit/charity/tree/master). When I see that it's been updated, I'll remove my guesstimate files and pull the official csvs. This usually happens when the countdown for the "Current Submission Round" has hit zero and I need to start the next round's files. Until that git pull happens, it could be showing incorrect data for the "Round in Progress".
It's a bit difficult to get the timing right, since UTB doesn't have a strict schedule on when the git is updated.
So, if you see something wrong with a round that has supposedly closed, contact UTB with the issue, and if he hasn't already run the files, he'll be able to fix it before it goes to press.
HB