Skip to main content

Module notes

Module notes 

Source
Expand description

What datui noticed about a dataset while doing what it was already doing.

A note never costs a request or a scan of its own: every one here is read off the footers the schema and the row count already needed. Notes are never alarming — no pop-up, no error styling — and every one says what it is based on, so “in 1 of 3 files” is never mistaken for a claim about files datui has not looked at.

A note is one sentence and the line it rests on. Review after review found false or empty statements here, and every one of them was in prose that went beyond the sentence: a denominator over the wrong population, an explanatory line that contradicted the note above it, a type named by a word two types share. What is left is what can be checked: one claim per note, and one function deciding the only ratio any of them states.

Structs§

Note
One thing datui noticed.

Functions§

from_dataset
What the footers said, as notes. Empty when every file agrees, which is the common case and the one where there is nothing to say.
from_the_open
What the open itself has to say, before a footer has been read.
left_out_note
Rows a filter or sort leaves out, because the column it names is not read from the files those rows came from.
map_caches
The cache-*.arrow files map() wrote beside a Hugging Face cache’s splits, which the read left out: their columns are the mapping’s, not the split’s.
merged
Every note the panel shows — what the open did, what the footers said, then what the view leaves out — with the one fact the first two both report said once.
no_header
The files a read of several passed over because they hold no header: empty, blank, or nothing but NUL padding.
some_names
names, the first few of them, joined, and an ellipsis for the rest.