A hierarchy of data cleanliness/readiness for training ML systems on: https://towardsdatascience.com/ready-set-ai-preparing-nhs-medical-imaging-data-for-the-future-8e85ed5a2824
Includes an interesting argument for centralising data sharing/cleaning at the NHS level.
miniblog.
Related Posts
After seeing yet another YAML dialect for controlling systems, I think we need a hierarchy of YAML dialect expressiveness.
(1) Has its own variable binding system.
(2) Supports if statements.
(3) Supports loops.
(4) Supports function definition.
2 seems to be the most common, but I've seen all of 1-3. Does level 4 exist in the wild yet?
After seeing yet another YAML dialect for controlling systems, I think we need a hierarchy of YAML dialect expressiveness.
(1) Has its own variable binding system.
(2) Supports if statements.
(3) Supports loops.
(4) Supports function definition.
I've added some new keybindings to deadgrep.el, so I split the shortcut tables into two categories: https://github.com/Wilfred/deadgrep#keybindings
I've done this purely by intuition. Are there good rules or heuristics for deciding when more hierarchy is needed in information, I wonder?