whiw

I've read the docs but I haven't tried it yet. I like the idea of storing n-dimensional data in an n-dimensional table, and I like the separation between the data ('cube') and the views and rules. I like that the rules operate on slices of the data rather than individual cells.

This occupies the space between traditional spreadsheets (simple UI but limited to 2-d) python (multi-dimensional data, and python or tensors (multi-dimensional data, but coding required).

I feel that the current data input is a bit cumbersome. There's a lot to type to enter just one cell value, and multi-dimensional tables contain a lot of cells. A more succinct alternative for data entry could be something like python/numpy multi-dimensional tables: [[[a, b, c], [d, e, f]], [[g, h, i], [j, k, l]]].

Data entry from a view grid (to a 2-d slice of the 'cube') would be more familiar, like a spreadsheet.

A data import feature (from csv, etc) would be useful too.

'Cube' has 3d connotations: 'ngrid' or 'ndata' could be less confusing.

I didn't see any functions like sum or product (or most other spreadsheet functions) to operate on data slices. I'm guessing that this is still proof of concept at the moment.

I do hope this goes further.

If we had a display with n (n>3) pixel colours, say (red, green, cyan, blue) for example, we could display more of the colour space. Shopping list: 4 colour channel display, 4 channel GPU, 4 channel software. Why isn't this a thing already?

I'd be concerned about clay heave (where clay shrinks/expands depending on moisture content, which likely varies over the year). If the posts at each end of a panel move out of plane there will be a twisting moment on the panel, and glass doesn't like being bent.

I meant lead carbonate, not lead oxide.

I am not a chemist, so take this with a pinch of salt: wouldn't lead chromate + sodium bicarbonate make lead carbonate, a white precipitate? Sodium bicarbonate is likely in your kitchen cupboard already.

Presumably from tidal forces, from the differential of the gravity field in the presence of nearby massive objects (like the sun, or jupiter).

That seems a somewhat callous disregard for the fish, blinded and swimming around with itchy eyes from burned out retina.

If the laser is powerfull enough to kill sea-lice then how does it avoid blinding the fish or giving them retina burn?

> Printf isn't re-entrant, and they are calling it from multiple threads.

This! Simple schedulers generally only allow system calls (such as printf) from the main thread. If you really want to 'print' from a child thread then send a message to the main thread, asking that it prints the message contents on on behalf of the child thread.

The transformer secondary was maxing out at 4A, 36V. The primary current will be much lower, probably about (40V/240V)*4A, ie about 0.67A.

Paisley pattern. Oh, somebody beat me to it.

This looks useful, I wish I'd found it a month ago. One suggestion: could we have a more printer-friendly version (ie, without large patches of colour and without large patches of black)?

I imagine that it would be more difficult to gain entry to an upper floor (at the top of a narrow staircase so single-file attackers) and a sturdy door with a couple of guards outside, than it would be to gain entry to rooms on the same level. Perhaps the women were tucked away on the upper floors, in relative safety.

> Galactic spectra, which JWST started to send back in earnest at the end of last year, are useful for two reasons.

> First, they let astronomers nail down the galaxy’s age. The infrared light JWST collects is reddened, or redshifted, meaning that as it traverses the cosmos, its wavelengths are stretched by the expansion of space. The extent of that redshift lets astronomers determine a galaxy’s distance, and therefore when it originally emitted its light.

Won't a photon climbing out of a huge gravity well have a huge redshift, thus confounding estimates of distance from us and estimated age?

> (I came up with this one): use a little firewall rule that prevents any IDN from resolving. That's a one line UDP rule and it stops cold dead any IDN homograph attack. Basically searching any UDP packet for the "xn--" string.

I couldn't see how to do this in Windows Firewall. Which OS/firewall/rule are you using?