• 13 Posts
  • 757 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle





  • Gotta be real, LLMs for queries makes me uneasy. We’re already in a place where data modeling isn’t as common and people don’t put indexes or relationships between tables (and some tools didn’t really support those either), they might be alright at describing tables (Databricks has it baked in for better or worse for example, it’s usually pretty good at a quick summary of what a table is for), throwing an LLM on that doesn’t really inspire confidence.

    If your data model is highly normalised, with fks everywhere, good naming and well documented, yeah totally I could see that helping, but if that’s the case you already have good governance practices (which all ML tools benefit from AFAIK). Without that, I’m totally dreading the queries, people already are totally capable of generating stuff that gives DBAs a headache, simple cases yeah maybe, but complex queries idk I’m not sold.

    Data understanding is part of the job anyhow, that’s largely conceptual which maybe LLMs could work as an extension for, but I really wouldn’t trust it to generate full on queries in most of the environments I’ve seen, data is overwhelmingly super messy and orgs don’t love putting effort towards governance.


  • Seriously missed an opportunity to being that back as their agent.

    Legitimately though, Cortana was pretty great. There was a feature to help plan commutes (before I went more or less full remote), all it really did was watch traffic and adjust a suggest time to depart but it was pretty nice.

    Say it every time someone mentions WP7/8/10, those lumia devices were fantastic and I totally miss mine, the 1020 had a fantastic camera on it, especially for the early 2010s


  • I bought the LCD when it was really steeply discounted, like nearly $280 CAD before taxes and duties for a new one. I bought my partner an oled one and the screen is strikingly different to me, size makes a difference and it’s a lot more vibrant (+ HDR).

    The LCD is a solid machine and a great value, I like my partner’s screen and battery life but I don’t know if it’s worth spending twice the price. Regardless, both are really easy to service, way more comfortable than the switch is too.







  • Yeah, makes sense based on where the sensor is, my heater didn’t have a thermocouple on it so I drilled a hole for a thermistor midplate, it’s super slow to respond is the downside but in theory it should be accurate enough.

    I don’t have experience with the bambu, in theory everything will experience thermal expansion but for the voron setup, the bimetallic construction is some of the issue, they have different thermal expansion properties so it can cause deflections. Part quality will vary wildly depending on sourcing too, vorons are very diy and open as the draw, but there’s just so much variability from sourcing, mods, assembly etc.



  • It looked like you have a textured sheet? 0.2 mm variation over the entire built area isn’t huge, might be exaggerating it.

    How much of a heat soak? If you’re going to the edge, let that sit for at least an hour, preferably more, look at Ellis’ page on thermal expansion, frame will absolutely expand. I use backers on my 2.4, gantry is giant bimetallic strip, backers do seem to help with that. Klipper does have the ability to correct for this as well, in that link. I do also have a kinematic bed mount (it’s coupled loosely to the frame, basically gives the bed room to expand), which again does seem to help, but I’d personally say heat soak is the first thing to do to achieve consistency.

    And to echo others, degrease your bed with dish soap & water (unless your surface can be damaged, Buildtak that’s a no, don’t of that for example). If that’s a textured sheet, may need to give a bit more of a squish, but get it good and clean first. Ellis has some solid 1st layer calibration and troubleshooting guides to go through. For pei, personally I’ve found I needed to rough up the surface a bit with a brass brush, I don’t love pei on my voron, usually use buildtak but have had really good results with the fire resistant version of garolite.

    Edit: read up on your probe, eddy current based? Sounds really interesting, my first point is probably moot, though possible you could be picking up the texture or if you have strong magnets it could affect it (my bed has an array of strong round magnets, seen others that are just a magnetic sheet), the do call that out in their FAQ.



  • I was looking through, generally custom macros are in the config folder, unsure if they’ve implemented it differently, here’s the Raise3D repo I found earlier, klipper has some code in c for the microcontroller stuff AFAIK with klippy in python, I’ve not personally dove into the code, just config and macro stuff largely.

    Actually digging through a bit, there’s some gcodes in /klippy/gcode.py in the above repo I don’t see in the Mainline Klipper equivalent, like M9999, it might be a start, klippy lives on the host machine.



  • Yeah, didn’t think it was an image, just images in gcode are encoded.

    I did find their github with a klipper config, but yeah, unsurprisingly it’s not there. You could see if it has documentation through the klipper console? I’m betting it’s not going to be in your klipper config unfortunately. Definitely leaning toward it being the portion that has the firmware validate the key and then set things up.