Regarding "a propensity to hold grudges" and "easily move on, forget, not hold grudges": I find this to be the case. I can easily hold a grudge, because it's like the grudge is a post-it-note stuck to the front of my book-of-knowledge. This means I can readily recall the grudge, and that I can also easily forget/move-on from the grudge (just remove the note).
Continuing with the post-it-note analogy, the note can only hold a small amount of information, and so the grudge will be recorded as something simple like "fuck ___, they're an arrogant twat". So then the situation arises where you're talking to someone else and they ask "what do you think about ___?"; and so you answer "I can't stand them, they're so arrogant"; to which they respond "oh really, how so?"; and you can't give an answer, because it wasn't written on the note.
I think this ties in with memories not making you feel the relevant emotions, because the emotion you felt was also just saved as a "fact". I have found though that if I step through all the facts of an "event" and consider each "moment" along the way, that I can often generate the relevant emotion. So say I was remembering an argument, I can remember various facts about the argument and that I was angry about it, but I can't feel that anger. But if I walk through the moments, like `they said this, which made me think that, to which I rightly responded with...`, then eventually I'll start to feel angry just like I would have.
For an analogy on how I think memories are stored differently: then for non-aphantasiacs, I reckon their brain must save `memory.zip`, which contains `video, audio, smells, emotions, etc`. For a person like myself with aphantasia however, it's like I asked ChatGPT for a summary of `memory.zip`, and then I only saved the summary.
Saying that though, I do wonder about the connection between "fact based memories" and aphantasia's lack of mental imagery. Because if >50% of the usefulness of `memory.zip` is from the video, but you can't "see" the video because you aphantasia — then has your brain decided/learned to not bother saving `memory.zip` and instead just save the summary, or are all components of `memory.zip` also corrupt/unplayable?
Just to elaborate on the "fast-facts"/post-it-note point I made: it seems there's actually a lot of "facts" ("conclusions") stored in a readily available manor in my brain. All the references/data that lead to these conclusions are stored in some deeper "archive" section though, and aren't readily available.
I guess you could compare them as if they are API's to different LLM's, and my "consciousness" is the web-browser. So it's like;
- `fast_facts.llm` is a micro model with good breadth and fast response times, but it has little depth. So it's API can be fetch'd without worrying about it blocking the main-thread/browser.
- `all_data.llm` is a full size model, but it's slow to respond, and "costs" more to run. So in the browser, it is only lazily-loaded (ie, not always used), and it has to be called async style because you have to wait for the results to slowly "stream in".
And stream they do, because back to my example conversation where someone asks "how are they arrogant?" — whilst I likely wouldn't immediately remember any examples (unless they happened very recently), at that point the request to `all_data.llm` would have been sent, and so after some umm's and ahh's, I might have an answer. Or I might just say "I can't remember off the top of my head, but also ..." start talking about something else, and then after 30 seconds I will drop the classic "but actually, i just remembered, ...".
I don't think the article is referring to that sort of issue, which sounds fundamental to the task at hand (calculations etc). To me it's about making the code flexible with regards to future changes/requirements/adaptions/etc. I guess you could consider Y2K as an example of this issue, because the problem with 6 digit date codes wasn't with their practicality at handling dates in the 80's/90's, but about dates that "spanned" beyond 991231, ie 000101.
> I think a lot of it boils down to load profile and power delivery
You said the right words but with the wrong meaning! On Gigabyte mobo you want to increase the "CPU Vcore Loadline Calibration" and the "PWM Phase Control" settings, [see screenshot here](https://forum.level1techs.com/t/ddr4-ram-load-line-calibrati...).
When I first got my Ryzen 3900X cpu and X570 mobo in 2019, I had many issues for a long time (freezes at idle, not waking from sleep, bios loops, etc). Eventually I found that bumping up those settings to ~High (maybe even Extreme) was what was required, and things worked for 2 years or so until I got a 5950X on clearance last year.
I slotted that in to the same mobo and it worked fine, but when I was looking at HWMon etc, I noticed some strange things with the power/voltage. After some mucking about and theorising with ChatGPT (it's way quicker than googling for uncommon problems), it became apparent that the ~High LLC/power settings I was still using were no good. ChatGPT explained that my 3900X was probably a bit "crude" in relative quality, and so it needed the "stronger" power settings to keep itself in order. Then when I've swapped to 5950X, it happens to be more "refined" and thus doesn't need to be "manhandled" — and in fact, didn't like being manhandled at all!
Chrome and Firefox use FFmpeg libraries to decode media, so it's in more places than you might think! (But also, ChatGPT said it's not used in Android browser apps because they would use Android's "native" media stack).
Joining videos together sounds easy, but there's tons of ways it can go wrong! You've got time bases to consider, start offsets, frame/overscan crops, fps differences (constant vs variable), etc. And even though your videos might both be h264, one might be encoded with B frames and open GOP, and the other not, and that might cause playback issues in certain circumstances. Similarly, both could be AAC audio, but one is 48kHz sample rate, the other 44.1kHz.
Someone else mentioned Lossless-Cut program, which is pretty good. It has a merge feature that has a compatibility checker ability that can detect a few issues. But I find transcoding the separate videos to MPEG-TS before joining them can get around many problems. If you fire up a RAM-Disk, it's a fast task.
Meanwhile I do 50% of my internet-ing in private mode and get annoyed when I change between apps the wrong way and loose my 4 tabs lol. I think this particular issue happens because firefox-android must get told by android-OS to free up RAM as it's now a background-app.
But there's another private-tab-killer, and it happens when the screen times-out automatically or manually (eg, when you push the power button). I don't have a passcode or anything, so when I push the power button to power the screen on, it shows the simple "swipe to unlock" screen. The problem is that FF leaves a "private browsing" notification — and FYI, if you click on any notification on my lock screen, it will unlock and go to straight to that app — so of course I see that notification and think "shit yer, here's a shortcut" and click it, to which it unlocks the phone and opens FF, but it wipes all my private browsing tabs in the process!!! But if you unlock it by swiping, then your tabs will survive...
Actually, as I'm typing this, I think it might wipe ALL tabs, but that's not so bad for regular tabs (as you have history, cookies, etc), but it can still ruin your "state" of a search/scroll/etc.
Edit2: I'm also just realising that the way it wipes tabs when I click the notification sounds just like the first issue I mentioned (which I presume is android-OS garbage collecting the memory held by "background" apps). I have a POCO phone that runs Xiaomi HyperOS, and if it's running a non-standard lock-screen "app" by default (because I'm using the default whatever with settings that suit me), then perhaps that's why clicking a notification counts as "changing apps"?! (or perhaps even the default android lock screen counts as its own app?) But this idea seems strange because it would imply that the "swipe to unlock" feature is not part of the "lock screen app"...?
Everyone except you has approached this discussion with the intent of using the solar power to drive the car, but they should actually be thinking of using it to power the cars electrical system, and thus negating the need for the alternator.
A current gen 2.5L petrol Camry has a 12v 80A alternator. That 80amps likely covers driving at night in the rain (ie headlights on, window wipers going, HVAC fan blowing, etc). Normal daytime driving would be much less demanding, say 50A load, thus 600W power. Then you have to factor in the alternators inefficiencies, which could raise that demand to 1kW.
Next consider what the engine is having to generate whilst cruising, which could be 20kW for the Camry. In this scenario, that 1kW of alternator load is responsible for 5% of the engines load. So ditching the alternator would give 5% fuel efficiency increase on this Camry. A smaller car that only needs 12kW to cruise would see an 8% improvement (8% of a low consumption value though), whilst a much bigger car that needs 50kW to cruise would only see a 2% gain (but that's 2% of a high consumption value).
So if "solar body panels" could generate 500W like people have already guessed in this thread, then that would be close to offsetting the normal day-time electrical load. In this scenario it's probably a good idea to power the vehicles electrical system from a lithium battery, which wouldn't mind the gradual draw-down, because that could then be offset by parking the car in the sun (and possibly even by regenerative braking). Then there could still be an isolated lead-acid battery that is purely for starting the engine (because that needs high cranking amps), and that could be DC to DC charged from the vehicle circuit.
That 12v 80A alternator can generate almost 1kW at max effort. So even if you drive all night in the rain, that's still less than 1/5th of the energy in a Tesla or BYD vehicle battery. So this alternator-less car could get away with a much smaller battery, and it might even be smaller in area than the cars boot!
Continuing with the post-it-note analogy, the note can only hold a small amount of information, and so the grudge will be recorded as something simple like "fuck ___, they're an arrogant twat". So then the situation arises where you're talking to someone else and they ask "what do you think about ___?"; and so you answer "I can't stand them, they're so arrogant"; to which they respond "oh really, how so?"; and you can't give an answer, because it wasn't written on the note.
I think this ties in with memories not making you feel the relevant emotions, because the emotion you felt was also just saved as a "fact". I have found though that if I step through all the facts of an "event" and consider each "moment" along the way, that I can often generate the relevant emotion. So say I was remembering an argument, I can remember various facts about the argument and that I was angry about it, but I can't feel that anger. But if I walk through the moments, like `they said this, which made me think that, to which I rightly responded with...`, then eventually I'll start to feel angry just like I would have.
For an analogy on how I think memories are stored differently: then for non-aphantasiacs, I reckon their brain must save `memory.zip`, which contains `video, audio, smells, emotions, etc`. For a person like myself with aphantasia however, it's like I asked ChatGPT for a summary of `memory.zip`, and then I only saved the summary.
Saying that though, I do wonder about the connection between "fact based memories" and aphantasia's lack of mental imagery. Because if >50% of the usefulness of `memory.zip` is from the video, but you can't "see" the video because you aphantasia — then has your brain decided/learned to not bother saving `memory.zip` and instead just save the summary, or are all components of `memory.zip` also corrupt/unplayable?