Ciro Santilli @cirosantilli 37

The generic tool recommendation question: unix.stackexchange.com/questions/7425/is-there-a-robust-command-line-tool-for-processing-csv-files

Simple example:output:

More verbose description:

Lots of features, but slow because written in Python. A faster version may be csvtools. Also some annoyances like obtuse header handing and missing features like grep + cut in one go: csvgrep and select column in csvkit.

A fast version of a somewhat subset of csvkit, written in C.

Build failed with undefined reference to pcre_config on Ubuntu 23.04: github.com/DavyLandman/csvtools/issues/18

Unfortunately it is lacking some basic options, like optional header + selecting column by index on csvgrep (though csvcut has it). The project seems kind of dead.

Also unclear if it allows to filter + print only selected columns.

Example: github.com/cirosantilli/cpp-cheat/blob/d18a11865ac105507d036f8f12a457ad9686a664/cuda/inc.cu

This is something worth investigating!

Bibliography:

Mostly on vintage electronics. Lots of focus on microwave, which he has worked a lot with.

Has been going wild with restoration and reverse engineering of the Apollo moon mission.

Anywhere north, including NE and NW: fenlands, i.e. marshes. Quite a few quarries as well. Extremely flat, very uniform, towns often have to be on top of small hills to escape the incessant flooding. Norfolk Coast AONB is beautiful if you take a train ride first, the beaches are very wide and many of them have few people if you avoid a few very busy spots.

East and SE: rolling hills towards Suffolk and the coast. Beautiful county, both Dedham Vale AONB and Suffolk Coast AONB.

South: first one of the hilliest nearby areas around Elmdon and Arkesden, then gently going down to the lush Lee River valley.

Southwest: larger and larger cities as you move towards London. From a train starting point, you can reach the Northen Chilterns, for some serious hills.

West: mostly flat farmland until you hit the River Great Ousse.

This is a term invented by Ciro Santilli, and refers to a loose set of uncommon Bitcoin inscription methods that involve inscribing one or a small number of payloads per Bitcoin transaction.

These methods are both inefficient and hard to detect and decode, partly because Bitcoin Core does not index spending transactions: bitcoin.stackexchange.com/questions/61794/bitcoin-rpc-how-to-find-the-transaction-that-spends-a-txo. This makes finding them all that more rewarding however.

On the other hand, they do have the advantage of not depending on any block size limits, as their individual transactions are very small.

Inscribing anything large would however take a very long time, as you'd have to wait until the previous payload chunk is confirmed before going to the next one. This alone makes the format impractical perhaps.

Known examples:

The laplace operator for Minkowski space.

Can be nicely written with Einstein notation as shown at: Section "d'Alembert operator in Einstein notation".

Given the function $\psi$:the operator can be written in Planck units as:often written without function arguments as:Note how this looks just like the Laplacian in Einstein notation, since the d'Alembert operator is just a generalization of the laplace operator to Minkowski space.

The rare ones. Notably present in peptidoglycan.