dragontamer

joined 1 year ago
MODERATOR OF
[–] [email protected] 6 points 16 hours ago* (last edited 16 hours ago)

The #1 pain point for pollsters is the prediction of the election demographics.

Polls and statistics are such that a general simple random sample has too little power / weak error bounds (I'm talking like +/-10%, nearly useless).

The easiest way to improve your error bounds is to make assumptions about the electorate makeup. IE: if you know the election will be 50% male and 50% female, you can poll 50 men and 50 women (rather than 100 random people, which might end up as 60 men and 40 women due to randomness).

Lather rinse repeat for other groupings (Latino, Asians, black, 18Y olds, 55Y olds, Rural, Urban, etc. etc.) and you get the gist of how this all works.

Alas: the male / female vote this year is completely worked because abortion is on the ballot. All pollsters know this. Their numbers are crap because the methodology is crap this year. It's impossible to predict women turnout.

[–] [email protected] 10 points 18 hours ago* (last edited 18 hours ago)

20+ out of 34 Senate for Democrats and narrow lead in the house.

That'd normally be exceptionally good news for the Democrats nominee. So I'm with the big theory that something funky is going on with the polls.

We are about to see the most split ticket voters of all time (Vote Democrat for Senate and House.... But vote for Trump in the Presidency), or people have been lying to pollsters somehow.... On a mass scale.

And I don't believe that split ticket voters exist in this election.

[–] [email protected] 2 points 18 hours ago

I'll be happy enough if its "just" Elon who loses out.

[–] [email protected] 3 points 1 day ago

Pascal programmers are confused.

[–] [email protected] 11 points 2 days ago

American voting game is one of turnout.

For Republicans, they are in the minority. But their will to vote is much higher. Pandering to his own supporters encourages the get out the vote effort in ways that Democrats are simply unable to do.

[–] [email protected] 34 points 3 days ago* (last edited 3 days ago) (3 children)

Puerto Rico has no electoral votes. But everyone born in Puerto Rico is a US Citizen.

Meaning Puerto Ricans who are currently living stateside (ex: studying at a university and staying enough months of the year to qualify for residency) can vote.


Similarly, a.... Californian.... who is living in Puerto Rico has no electoral votes. Because USA assigns votes by land.

Every Puerto Rican is a USA citizen who has the right to vote. As long as they're living in the correct area (ie: inside the 50 fully accepted states).

[–] [email protected] 22 points 4 days ago (2 children)

Haitian migrants were legal btw.

Puerto Ricans likely remember the more racist times decades ago. And secondly, they are a much larger group than Haitians. So this is a much bigger mistake than the Haitian thing a few weeks ago..

No offense to any Haitians around here. Just talking about sizes and demographics. It's awful that we have a candidate who is so openly racist. But I'm happy that they're showing their colors while we can still defeat them at the ballot box.

[–] [email protected] 19 points 4 days ago

The endorsements come from the writers, not from leadership.

If a conservative owner owns a liberal set of writers, muzzling your writers and stopping endorsements is to the conservatives advantage.

[–] [email protected] 24 points 4 days ago* (last edited 4 days ago) (2 children)

Florida also has the Abortion ban on its ballots, so Women are likely going to vote in huge numbers.

Kinda sad that the Presidential election is riding on the coattails of other issues, but that's the nature of today's politics.

Florida is considered solidly red though. But all elections in the USA are a turnout issue.

[–] [email protected] 23 points 4 days ago* (last edited 4 days ago) (1 children)

So yeah. LA Times, Washington Post and now Gannett conglomerate all made the same decision at roughly the same time.

This was preplanned.

I don't think this media takeover strategy is going to go as they hope. This makes the Democrats cause more real and heightens the stakes.

[–] [email protected] 12 points 4 days ago* (last edited 4 days ago)

Oil futures were down. Not actual oil.

An oil future in WTI makes you legally obligated to pickup the oil in West Texas or along its pipe network (most common pickup point is Arkansas IIRC).

So let's say you bought an oil future for $0 at $0 a barrel. And now 10,000 barrels of oil are waiting for pickup. And let's say you are a New York speculator and not actually someone with storage.

How do you get rid of the contract before you are penalized? Well, you sell it at -$10. But the guy who bought it for -$10 was also a New York speculator who thought the price couldn't go any lower.

By the end of the day, the speculators were selling the contract for -$40 a barrel, because the penalty for missing the pickup date is very heavy.

Eventually, some trucker 'Bought' the contract at -$40 and made free money as the trucker just had to go there and pick up the oil.

[–] [email protected] 2 points 4 days ago* (last edited 4 days ago)

J Lo and Bad Bunny?

At least I hope they helped. The Latino vote is stubbornly in the middle right now. Encouraging their vote looks like it'd help....

 

Despite all the doom scrolling, Harris has a comfortable lead in the electoral college right now.

The time for vibing is over. It's too late to change anyone's opinions (especially because national level events like debates are over). Harris will finish her Media Blitz soon (including a Fox News showing) while Trump retreats into his shell hoping no one notices how damn stupid his mouth is.

This is the time for doing. The focus should be on voter drives and other get out the vote pushes. It's mid October, and the October surprises are against Trump and in our favor.

It's not the lead we wanted but it's a lead nonetheless. Don't talk yourself out of believing this lead because of a bad poll or two.

 

Just working on my recent electronics project and I needed two temperature sensors for it. This time around I didn't feel like making a full PCB from KiCAD and wanted to keep things simple with a 1/2 size solderable breadboard.

As usual, I'm using an AVR DD (this time: a curiosity nano devboard) for simplicity. (I expect to need the 32768 Hz clock crystal, so a PCB with said clock would be nice. Otherwise, the DIP package is available). The overall circuit is pretty simple, but the topic of discussion today is the MCP970X series temperature sensor.

https://www.microchip.com/en-us/product/mcp9701a

At this point I do recommend people to read the documentation.

The gist is that you simply apply 3.1V to 5.5V between Vdd and Gnd. Vout will have some amount of startup time, and eventually output 400mV + (Temperature-in-C * 19.5mV). For example, my room temperature is ~24C right now and the voltage output is ~920mV.

(There's clearly errors in my ADC but I'm saving that for later... this device is supposed to be outputting 876mV given the room's temperature)


With a ~6uA expected current, this device is power-efficient enough to run from most MCU pins. AVR DD's 50mA-per-pin is overkill, but more importantly, a through-hole design like mine seemingly has substantial inductance on all wires.

The datasheets claim a startup time of 0.8ms. Alas, when I soldered on the MCP9701 and turned on the GPIO-pin, it took over 20ms (!!!) before the oscillating signal finally calmed down and settled upon the room temperature reading.

To counteract this parasitic inductance, I've added a 10kOhm resistor and a 10nF capacitor out of my through-hole kit. (E12 resistor kit and E6 capacitor kit). With 220us of startup time now on the GPIO pin and with only 500uA max current going to Vdd... there is no more "ringing" anymore and life is good!

EDIT: I should probably note that my goal was to return to 0.8ms startup time, like the documents suggest. 10kOhm was chosen as 500uA (5V) to 250uA (after charging to 2.5V) is a magnitude more current than I need and is a decent starting point. 10nF was chosen to pair-up with this to give me startup time in the 100us range but not over 800us (I don't want to be "slowed down" by the charging capacitor, so I want the Vdd charge to be faster than 800us claimed startup time). It should be noted that a 5V over 1000us curve was claimed as a 800us startup in the MCP970x documents if you read all the graphs.


Moving forward, my last task is that of calibration. The on-board ADC of the AVR DD is apparently quite accurate, but the Vref of the microcontroller is +/-4% (!!). With a +/- 2% accuracy of the temperature sensor, there is some calibration I should do.

The ADC errors + Vref errors are expected to just be linear. The temperature-sensor's error is quadratic however. In both cases, I don't want to overcomplicate things, so I'm planning on just adding a constant-offset to the mV reading to shift it to the correct spot.


All in all: pretty standard Analog-to-digital conversion issues here. But I figured it'd be a good discussion topic for beginners.

 

Modern AVR has a wide variety of Timers (TCA, TCB most commonly, but TCD, TCE, and TCF are uncommon and specific to particular AVR chips).

This can make choosing a AVR DD vs AVR EA vs AVR EB vs AVR DA a difficult choice, especially if you're trying to use timers to their greatest extent possible.

This blogpost covers a basic idea of what the different timers offer.


The blogpost is short enough. I feel like what I can add is to highlight the difference between:

  • Timers -- A background count++, a comparator of count vs some pre-configured values, and then likely an output pin that changes based off of these configurations. Consider this an MCU output. Almost everything listed can be used as a timer.

  • Counters -- Counter functionality is an MCU input. Many protocols, such as Servos, PWM, pulse-train decoding requires a variety of pulse-frequency-modulation, pulse-counting, or wide variety of other kinds of common tasks. "TCB" may be called a "Timer", but its really more of a counter-focused device which can more easily measure frequencies (for pulse-frequency-modulation). TCA and a few others can do some basic counting tasks, but usually not as well as TCB.

The other discussions in the blog are easy enough to understand IMO. This is all AVR specific, but some of the best material online are highly specialized articles like this, so I still feel like sharing.

 

1.5 c Microcontroller alert.

Very low-end, but 38kHz support is explicitly called out in its product manual. This means that this tiny uC is ideal for TV remote control (or other IR-blasters).

I wouldn't recommend anyone use this chip unless you were some kind of professional saving pennies. Typical $1 uCs are far easier to work with and have exponentially more power (even $1 8-bit uCs). Still, its an interesting thought experiment for what a 1.5 cent uC could be used to implement....

 

This blogger booted an F1C100s from scratch, even though they made a mistake buying 16MBit instead of 16MByte of Flash. (Requiring to be booted off of USB-bootloader / Allwinner's FEL Protocol instead of Flash).

So a few mistakes were made, but its still a custom booting Linux + blogpost that explains the steps.

 

What really interests me about this design is the ~~buck~~ Boost-converter

So this ~~buck~~ boost-converter is 100% core-independent. The Analog Comparator, TimerD, CCL, and Event-System are all active while the AVR DB sleeps, meaning that the microcontroller can run this simple ~~buck~~ boost-converter without any cost to CPU time.

An incredible design that demonstrates the flexibility of AVR DB's combined peripherals.

 

Hacker News discussion here: https://news.ycombinator.com/item?id=40560300

 

A random article talking about I2C on the NuttX RTOS.

I haven't heard of NuttX before, but the supported platforms (https://nuttx.apache.org/docs/latest/platforms/index.html) is quite impressive, including several chips I'm interested in. There's a number of 8-bit processors (albeit larger ones) on the list, though I'd assume this NuttX OS is best served on a microprocessor??

12
submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]
 

TL;DR: Prius and Prius Prime have a flaw where the rear doors may get water-leak (possibly from a car wash?) and randomly open even while driving. Toyota has issued a large scale recall as well as a stop-selling order to all dealerships.

That basically covers all 5th Gen Prius and Prius Prime vehicles. So until this door issue is fixed, no one is buying that vehicle.

 

Edited the "I" for less confusion. The blogpost's title is "I made a...", but "I" (Dragontamer) didn't do this. I just found this blogpost and though it was relevant for this sublemmy.

 

I've preferred Pixel phones for the last few years but I've heard that Pixel 6/7 had 5G connection problems (Pixel 8 apparently has a better modem, but I think I'd rather stick to a Qualcomm design for now).

So onto looking for my next phone.

I haven't considered a Samsung smartphone in years because I hated their TouchWiz stuff. But apparently they got rid of that like 8 years ago and have had multiple versions of updates. Can anyone comment on how good "One UI" is compared to stock Android? How much bloatware does it feel like? And what kind of customizations did Samsung do to the UI exactly?

I'm also looking at Asus Zenfone 11, but I figure the "mainstream" choice today is Samsung, so I'll also have to seriously consider Samsung phones.

view more: next ›