hollandays

Also, the headline is sensationalist. The total cost per ticket the buyer pays is $2 per vehicle. I've been to state parks that charge more. Yeah, it adds up to millions for the seller, but they're not charging extortionate prices.

Now that we know this type of contract model works, and if people are bothered by the unexpected windfall, future contracts can be structured differently to taper off or something.

True, though I said investigate, not interrogate. In the context of the pre-bias example I was responding to, it's fine to integrate it into a search engine to assist with guiding you to sources of information, but it shouldn't manipulate the information by describing it to you, even if it also provided source links.

The inherent problem with chat bots is you can't investigate why they're telling you something. When I search Google, I'm critically evaluating the information, and it's frustrating when the results it gives are low-accuracy. If I ask a chat bot a question, what would I do with the answer if it might be wrong? There's no context for me to evaluate.

Are any of those examples successful open-source projects with both the computation and the GUI written in Python? I don't know of anything in any field like that.

I think you misunderstood me. The choice of tools for front and backend have to be independent. The only really successful projects implemented in one language are all in C++, and that's difficult for everyone to approach.

In my opinion, the next step is to figure out a good way to combine something like gnu octave with nice modern GUIs.

Old tools were inaccessible to use because there's nothing to look at with a text-based tool, and inaccessible for engineers to develop because programming was so arcane. Look at Berkeley spice written in C. It's a lot of old-school parsing and implementing matrix methods.

The new stuff that's more accessible to use is more accessible for a software engineer to develop, but it's arguably even less accessible to other engineers and scientists to add their contributions. This creates an issue where the tools remain as good-looking toys that never get any serious technical chops.

Splitting the implementation is the way to go, but neither side would be happy about the interface. There's also the issue of platform because good engineering tools only run locally.

I don't know what the answer is, but it's not Python. We already have python, and yet, there isn't an explosion of collaboration to make great tools for the physical sciences and engineering. It's too much of a compromise for both sides.

I was being nice about saying that most other commenters probably hadn't read to the end of the article by phrasing it as an opinion.

How is this article manipulative or related to ChatGPT?

The fact that the fair didn't wait for the hearing or sue the contestant comes across like they knew they didn't own it. But the fact that they had a "no exceptions" rule instead of structuring the auction so that they're the legal buyer of the animal and the winner buys the meat from them comes across like they're stupid.

To me, this is the most important claim in the lawsuit:

> From there, the goat was delivered to unnamed individuals at the fair “for slaughter/destruction” even though the warrant required them to hold the goat for a court hearing to determine its lawful owner, the lawsuit says.

There was a property dispute, and the court issued a warrant to recover the property and hold it until a court hearing to decide ownership, but the holders disobeyed the warrant and hid or destroyed the property.

This was my biggest complaint about college. There's no reason a bachelor's degree should take 4 years.

I forgot to say that the SRF is the bottom of the V in the plots.

People have preferred ways of dying. Dam flood vs nuclear radiation. Human driver vs robot. It's a legitimate trade-off between how much you value likeliness vs method. It's annoying that many people don't (or won't) separate those ideas.

You ask good questions so I'll give very short "answers" to get you started in your search for good explanations.

The tests are frequency sweeps, one frequency at a time over multiple frequencies. Linear models can be decomposed into individual sine waves via Laplace/Fourier transform, so it's valid as long as the model is valid. The input voltage looks like a DC (bias) voltage plus ripple (RF). The frequency response of some capacitors depends strongly on the DC bias (the trap). All capacitors flip to being inductive above the self-resonant frequency (SRF). Good test equipment is expensive, but there are options for hobbyists. A test like that can't predict the response for other inputs and conditions, so you need a model of the dynamics.

That's way too much background information for one article. YouTube is probably your best resource for learning enough to follow along. EEVBlog has a couple of videos on bypass capacitors.