This one is geared toward experiment design and iterative profile development. People shouldn't use the new feature all the time, but it should be a good QoL improvement for people who need it while being ignorable for people who don't.
Started work on implementing what I think is probably the biggest feature for what I hope will be the next update to CRUCS, though there are a few things that I'd like to try to get into that. This involves one highly invasive change that I'll need to audit the whole (thankfully small) existing code base to make sure everything is updated to do things slightly differently and there's an aspect where I'll want to try a few different approaches to see what works best.
@yomimono We've got a lake dragon, but it's not in the lake proper. There's a cave that enters into it and the dragon is stuck in that where it allegedly controls the tides. Don't remember its name so yeah, we could do better.
New tutorial video is up. Here I'm taking roasting data from two batches of coffee where the data initially looks very different and I'm showing another way of looking at the data which explains how these ended up matching on the sensory spec.
It's an analysis technique that I've been successfully using for over two decades that never really caught on, I think in large part because there wasn't any software to make it easy. The latest CRUCS update changes that.
Decided it would be less work to just re-record the tutorial and instead of trying to figure out what sort of graphical screen recorder was going to work for me, I just used ffmpeg. Should probably stick the command into a 1 line shell script with a nice name so I don't have to look up the options I need next time.
Recorded a new tutorial video, but the screen recorder only grabbed the upper left quarter of the screen instead of the whole thing (HiDPI issue I guess? What are people using for screen recording on Linux/X.org these days?). I can probably still make it work instead of re-recording the whole thing, but I'll want to eat a lunch before I attempt that.
@stux I've swam with sharks (they were around the coral reef on Coiba when I spent some time there [at a research station, not in the prison]). Sharks are fine. Would do it again.
This is based on an analysis technique I was using way back when I was tracking roasts with pen and paper. I've written about that elsewhere, but it never really caught on, I think mainly because it's historically been too time consuming to slice and dice the data like this. Building the feature into CRUCS makes that a lot more accessible so hopefully people will start using that to better contextualize their roasting and tasting data.
CRUCS version 1.2.0 is now live. The main addition is the Analysis menu and report. There are some other uses, but the main idea here is you can import data from multiple batches and get a view into how these compare within various defined ranges. There's some room for improvement to the feature, but it's useful enough that I didn't want to further delay getting it out. Should do a tutorial video on that soon.
The next thing that I'd like to try adding once the currently pending release is out will let me talk about roasting plan design in very sci-fi sounding terms like applying a localized time dilation (which is very useful if you're designing training exercises). I've also had a thought on further enhancements to the time entry fields.
Author of Typica software for coffee roasters.