TFA says "After 1,000 fast charges, the battery should retain more than 90 percent of its original state of charge, the company said."
I can't really judge whether 1000 charges is a reasonable target for a car, though i think that 1000 fast charges is reasonable. It should probably be able to push to 5000 slow charges and 500 fast charges, which should fit a lot of use-cases.
If you get 400km per charge using 88% of the battery (98% -> 10%), that's 400,000km (258,000 miles) before you're down to 90%, at which point you have likely worn out an awful lot of other things with the car.
Admitting that I have the luxury of an urban, low-driving lifestyle: I'm 50. That battery would literally last the rest of my driving life and have room to spare.
Understanding battery degredation takes a lot of nuance. If you do nothing but charge and discharge quickly at some given temperature, you degrade to 90% in 1,000 cycles.
But the battery also degrades over time, the hotter it is the more, the higher the SOC the more. So you have to add on that calendar degradation, to that 10% loss from just charging.
Total degradation in practice will vary a lot, based on users charging and storage practices. Most of the time in practice it seems some fault will brick a battery before it degrades too much in total capacity.
The battery in my PHEV (Chrysler Pacifica) showed no appreciable degradation in eight years (and >100k miles) before being replaced under recall for a manufacturing fault last year.
>I can't really judge whether 1000 charges is a reasonable target for a car
I mean, if "charges" is "full charge" and the battery pack does even 200 miles of range then that'd be 200,000 miles right? And more like 250-300+ miles seems like a spreading target as energy density ticks upwards.
Honestly that's more than I've ever put on any single individual car or truck I've owned, and well into the point where I'd be expecting to put real money into engine and other work for an ICE. Sure more is better but if a battery pack can go 200k-300k miles keeping 90% range that doesn't feel unreasonable at all for non-commercial usage. Taxis and so on with much higher utilization may find value in alternative options of course.
1000 charges 10-80% for a passenger car at 300-400 km per charge is 300 000 - 400 000 km of fast charge driving. I'd say it's perfectly fine for most people?
The point is that most charges do not have to be fast charges. The usual case is to charge slowly when parked at a "Destination Charger" or overnight at home. Electricity supply is almost everywhere.
You have to change the mentality of "I only get gas when I travel out of my way to the gas station, so the gas refill has to be fast". EVs just do not work like that, and overnight charging is far more convenient that having to go get gas.
Well, you stopped hearing about it, not because it stopped being used, but because its support became mainstream for a very long time. Google strongly recommends using zram on all devices, even on devices with a lot of RAM since like Android 10?
I'll add to your comment that it isn't a bug of MCP itself. MCP doesn't specify what the LLM sees. It's a bug of the MCP client.
In my toy chatbot, I implement MCP as pseudo-python for the LLM, dropping typing info, and giving the tool infos as abruptly as possible, just a line - function_name(mandatory arg1 name, mandatory arg2 name): Description
(I don't recommend doing that, it's largely obsolete, my point is simply that you feed the LLM whatever you want, MCP doesn't mandate anything. tbh it doesn't even mandate that it feeds into a LLM, hence the MCP CLIs)
Since GCC is lacking such an essential optimization, you should consider have one of your junior interviewee contribute this basic optimization mainline.
You can make frequency inertia with solar (even without batteries if you accept running with a constant reserve so with reduced efficiency). Spain showed that there is a learning curve, that's for sure, but their issue was a "simple" oscillation problem that can be fixed by adjusting frequency-follow rate and grid-disconnect rules. It wasn't like a peak of energy consumption or loss of energy production that only a rotating mass could compensate.
80% accuracy could mean 0 false negatives and 20% false positives.
My point is that accuracy is a terrible metric here and sensitivity, specificity tell us much more relevant information to the task at hand. In that formulation, a specificity < 1 is going to have false positives and it isn't fair to those students to have to prove their innocence.
That's more like the false positive rate and false negative rate.
If we're being literal, accuracy is (number correct guesses) / (total number of guesses). Maybe the folks at turnitin don't actually mean 'accuracy', but if they're selling an AI/ML product they should at least know their metrics.
It depends on their test dataset. If the test set was written 80% by AI and 20% by humans, a tool that labels every essay as AI-written would have a reported accuracy of 80%. That's why other metrics such as specificity and sensitivity (among many others) are commonly reported as well.
Just speaking in general here -- I don't know what specific phrasing TurnItIn uses.
The promise (not saying that it works) is probably that 20% of people who cheated will not get caught. Not that 20% of the work marked as AI is actually written by humans.
I suppose 80% means you don't give them a 0 mark because the software says it's AI, you only do so if you have other evidence reinforcing the possibility.
you're missing out on the false positives though; catching 80% of cheaters might be acceptable but 20% false positives (not the same thing as 20% of the class) would not be acceptable. AI generated content and plagarism are completely different detection problems.
Is there a survey of SoTA of what can be achieved with CSI sensing you would recommend?
What is available on the low level? Are researchers using SDR, or there are common wifi chips that properly report CSI? Do most people feed in CSI of literally every packet, or is it sampled?
Now many people use https://ps.zpj.io/ which supports some hardware including SDRs, but I must discourage using it, especially for research, as it's not free software and has a restrictive license. I used https://feitcsi.kuskosoft.com/ which uses a slightly modified iwlwifi driver, since iwlwifi needs to compute CSI anyway. There are free software alternatives for SDR CSI extraction as well; it's not hard to build an OFDM chain with GNUradio and extract CSI, although this might require a slightly more in-depth understanding of how wifi works.
> networks don't care as long as they get their cut.
Pretty clear this is the case, almost all of it could be stopped overnight with a simple whitelist to people you know and a blocklist of countries and regions where you’ll never ever need to take a call from.
...and perfectly legal services too, e.g. joinmassive.com, brightdata, etc.
(they're used for gathering listing data from e-commerce sites, job boards, etc.)
They do this so they are harder to track & block. If they were sending over Wifi then they have to hide the IP, so they have to use VPNs, which are often blocked, etc. But with their solution they have a standard SIM on the standard cellular network, so it's nearly indistinquishable from a regular cellphone.
I can't really judge whether 1000 charges is a reasonable target for a car, though i think that 1000 fast charges is reasonable. It should probably be able to push to 5000 slow charges and 500 fast charges, which should fit a lot of use-cases.
reply