The csv file which shows votes per state over time, last few days.
Csv
http://s000.tinyupload.com/?file_id=14566999163598825215
Python script
Issue:
Csv file has the vote share columns which is used to calc each candidates votes. The vote share columns only have a precision of 3 decimal places. This leads to vote shaving, needs to be at least 7 decimal places of precision.
Take 2,690,400
Votes share .493 for Trump (1,326,367 votes) Vote share .502 for biden (1,350,581 votes)
Now change Trump vote share to .492 and leave biden unchanged. Happens all over the place and by bigger margins.
Now Trump has 1,323,676 votes loosing 2,690 votes.
How can any data enginneer use only 3 digit precision for calcs like this unless you want rounding errors to hide vote shaving and use it as cover as a oversight or "glitch".
This manipulation and large voter dumps only showing up in key battkeground states and a few others.
Does anyone have any time series data by precinct?
This data being used by all media outlets is bunk.
why are they using percentages instead of counting and providing the exact number of votes? this is so fucked up. wtf kinda coding is this?
You're thinking like a coder wanting accurate data, not a coder wanting malleable data.
Exactly, I don't get it either.
No reason to do this unless you are trying to hide vote shaving, normalizing and hiding the change through rounding errors.
I would fire any IT developer or db engineer who only used 3 digit precision to calc numbers like this and thought it msde sense.
Seems like they were using float16s to save memory. You know, energy saving, green vote counting using the percent methodology that anyone with a 4th grade education wouldn't use unless they were trying to act like Richard Pryor in Superman III.
Common core coding
Yes
Yes, why would you store data like this, would never be accurate. Hence why on TV you would see Trump loose votes in realtime. All news media using same edison feed.
We need to foia or sue edison for raw data.
Yeah there are some Twitter threads about this.
The data was intended for visualization not serious analysis.
Yeah but even for visualization it is really flawed. Also the archive videos out there showing vote flipping and votes switching between Trump and biden are seen in this feed caused by rounding errors that never recover.
That is the odd piece to all of this. Being used to cover vite shaving in the real datasets.
Vote share is calculated from the number of votes.... not the other way around.
Also, stop obsessing over the data from Edison Research. It isn't the official data.
Edison Research collects data themselves from multiple sources, bypassing the Secretary of State(s).
They aren't the authoritative source.
Yes. The Secretary of State publishes it.
I can easily find it for my state.
No, it’s done by each state, separately.
Edison Research is a VENDOR to the Misleadia, not an official agency.
Yes, but why create a datastream so bad as to cause vote shaving etc.
I think part of the plan to bide time to cover for the vote shaving and to allow more fake ballets to be added to the system.
Mass manipulation of everyone to easily control their narrative during the counting.
Agreed. I want the official feed data but can't find it.
This Edison feed data rounding errors match exactly to the live video feeds people have been archiving.
Why would the feeds shiw this as well, vote losses in huge chunks. Seens suspect to all hell.
My secretary of state publishes unofficial data as the votes are compiled. But until it is certified, it’s not official.
Straight out of office space, and we all know how that movie ends
Had an Edison surveyor come by the ballot place I was watching on Election Day, they had a sketchy vibe. Now I know why.
If they're using the remainder after the percentage calculation (I can't understand how anyone thought this is a way to tabulate votes ... wouldn't this raise a lot of suspicion??? Did anyone ever frigging review this???), then a count of the ballots should confirm their shenanigans. They'd have to make sure that they forged enough ballots to boost one candidate trailing in the dataset and destroy the others for the other candidate leading in the dataset.
That assumes they even fixed the ballots. They're probably operating under the assumption that nobody is going to count the ballots.
I highly doubt they did this accurately.
Yeah, download the csv to see for yourself. Others here see same thing in json feed as well. County detail is good, lots if details but the timeseries data is jacked up like this.
I don't understand why they would do this to the realtime feed.
Are you getting the impression that you're the smartest one in the room because the room has gotten dumber.
When I looked at the actual Edison data I had this same sudden uncomfortable realization. There are people on the site saying the same but mentioning "granularity", maybe they know but are using that word in an attempt to keep the obfuscation going and hide their embarrassment.
My take is Edison releases data only precise enough to drive news screen bar graph widgets but the news people go on to calculate (x*0.xxx decimal) trash vote numbers for extra eye candy. The news people do the trash math so Edison sees them put vote totals that aren't accurate on the screen and says "well what the fuck" while smiling. Fuck Edison. Ask me even 20 years ago whether news networks would some day put trash-numbers on the screen and not care and I would have said NO WAY.
Modern technology: with massively more speed and capability than ever before, deliver an inferior product at greater cost.