robotsteve2

1. Uncertainty in the speed, direction, position.

2. Uncertainty in the model (e.g. influence of external bodies besides the sun and earth).

Kinematic motion models are exact but our knowledge of all the variables involved is not.

This is typical in other fields of engineering. Details and best methods for running advanced design tools, some of the most advanced engineering knowledge, etc, are not found online in a easily-digestible Stack Overflow format. This is the norm, software engineering/Stack Overflow are the exception.

This is just an ad for an RSS reader.

Might not be much of a production line. Very big, very slow, sensitive to weather conditions. What do you do about all the scattered light? The guy in the picture is wearing goggles, but people in the building who see the crucible (while looking out the window) won't be.

The world doesn't revolve around web development. It's not the only use case. Scientific Python is huge and benefits tremendously from the language being faster. If Python can be 1% faster, that's a significant force multiplier for scientific research and engineering analysis/design (in both academia and industry).

Any sort of hardware or software error seems much more likely. Computers are incredibly complex and approximations are used everywhere (in the design of the hardware, in the theory of operation). I don't think inference-based experiments or analysis on cosmic ray bit flips are appropriate.

You really need some kind of dedicated cosmic ray detector nearby as a control. If the flux of cosmic rays into the detector is orders of magnitude lower than the rate of bit errors you ascribe to cosmic rays, it's probably some hardware/software issue and not the cosmic rays.

> I’m happy enough to be putting books out in the world, making this community better, having a physical space, challenging myself, etc…as long as I don’t lose lots of money, that’s a win.

The author defines book store success as "not losing lots of money." I think readers should be cautious to interpret this as a traditional business success story, since the author clearly views the book store as a hobby project more than a business.

Their observations of nature and their ability to predict stuff should be consistent with ours.

They might not use the same mathematical tools or the same physical models, but they should make the same predictions. That is, we might not be able to understand their theory of gravity, but whatever their theory is, it has to be able to make predictions about orbits, black holes, etc.

I don't think we could assume much about the mathematical concepts they use beyond that.

Nobody knows, full stop. We can guess and conjecture about what should and should not be possible with respect to the origins of life, but really, we know very little. So it's not very meaningful.

We haven't observed abiogenesis and experiment/observation is the ultimate guide.

It's an important distinction. A lot of people would like to think electrons orbit the nucleus like planets orbit a star.

Spherical harmonics are a useful mathematical basis set for eigenfunctions of a Schrodinger equation describing a hydrogen atom like system.

There's nothing particularly special about them, and they fail to be a good basis set for solutions of other types of quantum systems. Conversely, they can be useful for non-quantum systems - any sort of wave equation in a sphere.

It's not an intrinsically quantum mechanical thing.

You'd have to also include plain English instructions on how to read the QR code, since the QR code format probably won't be around in the future either.

As for reading the instructions: they could probably still interpret modern English, similar to how professionals today can still interpret English from 500 years ago (with some effort).

Once you've got the waveforms as arrays, what do you need the ASCII rendering for?

Instead of diffing ASCII-rendered waveforms, save the arrays and diff the arrays (and then use any kind of numerical metric on the residual). Scientist programmers have all sorts of techniques for testing and debugging software that processes sampled signals.

You need more than a first approximation.

For #2: I tried it, downloaded the large file and installed. Then on launch, it couldn't find any JupyterLab install from my Conda environments, and it asked me to find it. I just uninstalled. I'm not sure what it wants or how it interacts with my many Conda envs and it's too much hassle to try and sort that out right now.

I use JupyterLab professionally and have never been able to get VSCode notebooks working at the same level. For example, simple bracket highlighting doesn't work in the VSCode notebooks I've tried. I want to like them, but they don't get the job done for me.

That didn't end up happening.