yt

In this blogpost, I walk through the annoying bits about loading unknown data into yt.

tl;dr: kaitai struct is awesome. File formats can be pretty annoying – especially when you figure them out through weird combinations of reverse-engineering, hand-me-down code and trial-and-error. What we’ve ended up with in yt is a bunch of data formats where the process of conducting the IO is all mixed up with the description of that IO.

Welcome to part 3 of a series on how yt deals with data and the ways that helps and hinders things! This time, I am going to describe what “chunks” of data (YTDataChunk) in yt are, and a few characteristics of them that wouldn’t be obvious from the previous blog posts.

SIDE NOTE: I intended for this blog post to be a bit shorter than it turned out, and for it to cover some things it … didn’t! So it looks like there’ll be a part three in the series.

The first post in a deep dive into yt frontends, chunking, and why and how they might be refactored.