Paper: journals.plos.org/ploscompbiol...

Fair. Though, it still has a decent chance of turning out true!

Ye have little faith in mechanistic interpretability advancing by then, eh?

github.com/dollspace-ga... Doll made this tool to help three cueing readers learn phonics

We compromise and make pumpkin pie and pecan bars

We made a simple config system based on Pydantic Settings. My co worker Jesse made it and it’s been killer to use.

It’s very similar to github.com/marin-commun..., which I also recommend.

I’m not so sure. A Columbia physics grad student once told me his perspective on string theory. He thought that the community was wrong to seek to build even bigger particle accelerators, and that instead, they needed to come up with new ideas.

Not my area, but never say never!

The high level hypothesis posed by this package is that the @cloudnativegeo.org ecosystem functions as a new type of database, one whose components we get to pick and choose a la carte. If this is the case, and CNG is really a database, then I argue it ought to also have a decent SQL front-end.

Currently, this project is looking for early adopters and open source contributors. Together with tire kickers and drive by patches, I think xarray-sql could make scientific datasets way more accessible.
github.com/alxmrs/xarra...

Right now, this package will only work on a single node. I expect it to break at early challenges of scale, and yet – I'm hopeful this will soon rise to the complexity of geospatial or scientific datasets. It should be possible in theory to distribute on Ray clusters, and doing so is on the roadmap.

This library was designed to address the use case of joining tabular data with weather data, such as @earthmover.io's temporal-chunked copy of ERA5. That's the dream, anyway.

docs.earthmover.io/sample-data/...

Tuning the performance of queries requires a bit of skill with SQL, but ultimately will be a matter of data engineering (another case of the tyranny of the chunk).

element84.com/software-eng...

Currently, the library should “just work” with any Xarray dataset – i.e. datasets backed by @zarr.dev, IceChunk, NetCDF, Xee, TiTiler, etc. Once opened, the library lets you think of coordinates as primary keys and data_vars as columns as you filter, group by, and aggregate to your heart’s desire.

`xarray-sql` tries to make ndarrays in Xarray queryable with SQL by imagining them as tables. The closest parallel I've found to this is XVec, which brings table-like geospatial concepts to rasters in Xarray. This project aims to do the opposite, which is to treat rasters like rows in tables.