dzervas

huh, you’re right! I’m trained on a different kind of code. In C# in particular, which I use mostly to do sneaky stuff (patch/inject runtime code to, um, “fix” it) and when I see a project that it’s too clean it smells

I also see python code (I code regular stuff in it) that could be written much more cleanly using monkey-patching

nice!

damn

you have a multi-billion cluster at your disposal it seems

you can do i: int to make this error out

are these choc or x?

awesome design! love the mountainy form

pffft there’s no way you draw even near enough battery to even notice any temperature change

how many hours does the battery last?

continuing my above answer: your cell should be a cheap 1C (which is just cheaper than the 3+C, not bad, it’s totally fine for your application) The C rating means “the max amperage you can draw from the battery to be safe is <C rating> times <battery mah rating>”. So a 1C 2000mAh battery has max amp draw of 2A (or 2000mA) while a 2C 500mAh has 1A (2x500mA)

If your battery lasts for more than 10 hours straight that means you draw 1/10th of max amp - meaning a cool battery. In case of a 1C 2000mAh you draw 200mA

So: if your keeb lasts more than 10-15 hours you’re more probably fine as the battery is kept cool

The amount of current you draw should be super low, even for 1C batteries so the produced heat should be negligible. I would however leave some space for potential puffing and maybe somehow a small window to check (if possible)

1-2mm would be fine. if you don’t have such space, i’d personally do it but i wouldn’t recommend it