Dr Frames Catherine White

@oxinabox.net

(She/her) PhD. Working on biology cell simulations. Engineering, ML, Constrained Optimization, Modelling, JuliaLang, AutoDiff, Programming This is my professional bsky.

It seems there is actually no great way to do open telemetry over GitHub actions. Solutions seem to be: Kinda broken: eg setup-opentelemetry Completely nuts: eg thoth Not opentelemetry: gha_buildevents Or only run in post, so can't be traceparent of stuff running in steps. Everything else.

I do not like been given 2+ page long reports generated by claude They violate the expectation that anything i am being asked to read took at least 2x as long to write as it will for me to read it. And documents that I can't trust not to be lying to me with a great deal of confidence hurt my brain

it's quiet amusing to me that LayeredLayouts.jl has 11 direct dependants (and 2 more indirect). Laying out DAGs is useful. Its why many languages implement smart heuristic algorithms for them. I did not implement a smart heuristic algorithms. I implemented the NP-Hard always optimal algorithm.

added to my startup.jl `ENV["JULIA_PKG_PRESERVE_TIERED_INSTALLED"] = "true"` so hopefully i can stop precompiling things constantly when making minor changes to dependencies a package that indirectly depends on hundreds of packages. Somethings always getting updated at that scale

Something I have been thinking about on and off is about the annotation of function primatives with properties, like nilpotent, associative, commutative, etc, then using (type) inference to infer this about functions built in them. Then using that for automatic parallelism and other optimisations.

I accidentally turned on AI completion in VS-Code yesterday. And I though "_fine_, I will finally try this thing" and I am really not liking having my tab completion lie to me? I just have to check it when it doesn't work, then look up the right way. When I could have just immediately looked it up

the amount of hatred i have for good tests that were marked "skip" because they are too slow that have bit rotted, is only exceeded by my hatred for good tests that were marked "skip" that are still good and would have caught bugs had they not been set to skip

the amount of hatred i have for good tests that were marked "skip" because they are too slow that have bit rotted, is only exceeded by my hatred for good tests that were marked "skip" that are still good and would have caught bugs had they not been set to skip

yes, I find i often in python I have modules that are really just one function (at least in their public API). Because it makes sense for all that to be in one file. Combined with explict imports and it makes quiet a complexity of import headers.

I wanted to see if I was part of the Anthropic settlement class: ✅ Book on LibGen before 2021 ✅ Book has ISBN ❎ were registered with the United States Copyright Office Alas, I am not. While my rights have obviously been violated, it is not in a way that is covered by this court case.

So we had a model incorporating thermodynamic constrains called a ThermoModel. And another model with enzyme constraints called a GeckoModel. (Gecko = Genome-scale model Enzyme Constraints, using Kinetics and Omics.) And we were making a model to combine them. Some kind of ThermoGecko.

I need to set julia to always run with bounds checks enabled. I have done this before. The big virtue is no more redoing precompilation between running normally and running tests. Since julia makes seperate compliation caches for the 3 different settings for bounds checks. +tests always have them on

Pretty happy with this for something I designed and printed all in one day, while doing other things. It snugly fits the brace on the back of mirrors. Which has a funny bumpy shape. No more bracelets scattered over my dressing table.

A 3D printed lattice with hooks inserted.
The top fits into a brace in back of the mirror The unadorned back of the mirror. Showing the weird bumpy brace