ikm imagining a little bit there being a safe place, where people can safely invent and engage new ideas that help people, in a creative manner that works for them.

the support, and by this i mean behavioral not structural, seemed focused specifically on the research task. i don’t know if it was intended that way, though, it may have simply stemmed from how inspiring the idea could feel.

maybe what it comes down to, could be like, how can we protect our shared innovative spritis when conflict around what this innovation is used for rises? my parent always taught me to ask questions. this didn’t make me friends i. school, but when i took an engineering class as a college freshman i learned that all problems can be solved within

when it happened i had been aggressively studying noticing things i didn’t notice before, so parts of me were likely still studying this in a small way as a child i was a software developer. this was rare in my decade. i was the only kid in my school with a computer.

for me, things tend to come down to general issues of my nervous system, cognitive and motor functioning, etc. it seems reasonably probavle that a good portion of this is psychological, despite being severe and neurologically real.

often problems like these have been solved already by people who did not have the tools (e.g. software development experience) to utilize their solution and ended up discarding it

i’m imagining maybe as a first draft idea, for a non-adhering layer placement above a support surface, to maybe have the nozzle a little high and extrude material slowly so it cools, and let it drop onto the surface below cooled. then to fill in a layer above or around this to flow into the gaps,

note: i prefer cam/laser approaches to 3d printing. with 3d printing i prefer custom filaments like wax, but don’t have experience with custom extruders. regarding machines. i prefer robot arms to xyz arrays. i find robot arms more humanly intuitive and flexible, and suspect they aren’t common because the control code can have more math.

On 4/22/23, Undescribed Horrific Abuse, One Victim & Survivor of Many wrote:

i’m imagining maybe as a first draft idea, for a non-adhering layer placement above a support surface, to maybe have the nozzle a little high and extrude material slowly so it cools, and let it drop onto the surface below cooled. then to fill in a layer above or around this to flow into the gaps,

this was the first draft idea for support that needs no breaking away. likely this has already been pursued by many people in various places somewhere out there. a first trial might involve a grid of test squares.

although i describe mecode as "not very good at all" i like how it could provide for an interactive 3d printer read-eval-print loop. i'm familiar with some small parts of the internals now and tihnk it could be fun to make a small wrapper library, maybe with an idea of merging some of the concepts down if ideas take off. for now staying in python opens avenues for integrating easily with new machine learning research.

i seem likely to spin out around this, but am keeping some further code in the hopes the small stability that helps produces some further progress. noting the most relevant point here is https://github.com/jminardi/mecode/issues/78 where i ask some other past contributors to connect around maintenance of jminardi's library going forward, which at least one of them mentioned in the past but got no reply to.

-------------------------------------------- i was thinking if i had a 3d printer generate small squares with random parameters, the user could pick the one that looked best to quickly calibrate an unknown printer. [the fact that my printer is already somewhat calibrated is slightly confusing for me when dissociated. i can further refine the values but it there is some difference or conflict in what is efficient for me and what is more useful for others. reducing the urgency would likely help (this is true of most things).] i wanted to do this in a way that provided for live interaction with the printer, so the process could be further improved via live feedback or AI.

--- the issue i've been running into is that when i set the feed rate to something nonzero, the printer seems to wait forever saying it is busy. i seem to need experience sending successful g-code. i've learned enough about g-code now that i can probably read a premade file, so it would make sense to find one of those files and bum it down, like bisecting code when there isn't a debugger, to figure out how to correctly use the extruder without freezing the printer up. i was hoping to be able to interrupt the printer if it is in a frozen state, but so far i haven't figured out how to do this in this particular state yet (it looks like disconnecting the usb device would add some options, as well as learning more gcode). attached are the files i have, which don't quite function but show my attempt to prototype something that could parameterize stuff. i copypasted some documentation into _parser.py which contains code to parse my copypasting into structures. meanwhile test.py uses these structures to send code to the printer. ------- another thing i've discovered is that i'm actually using a very old version of mecode that happened to have a fork recently updated. the mainline gcode had two major version updates prior to the fork i've been engaging. this gives me a desire to merge the two together which is unfortunately inefficient. it would be more efficient to try to run the newer code, porting my fixes over if they become needed (this could take me some time from my spasms, which i've recently been finding a couple possible avenues that could help reduce). i might also want to look for forks that are based off the newer tip, to see what the actual latest codebase is.

the protocol can use line numbers and checksums, which mecode uses, also of note

thoughts on superslicer/prusaslicer/etc: - i make small things so it's most helpful to contribute to others - these systems would already have the gcode language enumerated - i don't have to use the whole system; but being nearer it would help me contribute something somewhere it could get used - there may be other gcode generators one could integrate with, for example there is a GPL gcode exporter for blender at https://blendermarket.com/products/blecolac---3dprinter-cnclaser-gcode-expor...

hihi thinking back on this, i guess the biggest inhibition was the difference from last night to today. i don't quite recall what triggered the inhibition last night. one of the biggest confusions in this situation with me, is that i'm used to being able to calmly work for multiple days to accomplish a complex project in a planning-type way ("do it right") rather than a deadline-type way ("get it done"). most of my habits still assume i can do this; it's where my senses of fun, accomplishment, planning, puzzling, etc came from during the course of the free parts of my life. nowadays doing this stimulates severe issues. [...] [there's ummm some severe tensions, many ptsd-like, that kind of collect like a descending ceiling]

one of my fears around "doing something right" is that when i spend too long without producing something useful i can have a sudden cognitive change and lose the progress. i've lost so many huge projects over the years. so it can be nicer for me to contribute a small thing publicly than to work on a big thing privately, because then i can see a result. it gets inhibited faster though.

i'm guessing that this was a recreational project and i've basically performed a step on it by trying something and learning about how it went. i did not get to the point of trying the actual project, so maybe daydreams might imagine whether it's interesting to think of a faster way to get to that point (there's some inhibition around an obvious approach), or the daydream could adjust to be something that's less distant. meanwhile, i guess i might do something different or such for a bit since the inhibition is so strong.

guess i'll upload to codeberg

the fork is just a merge of the open prs (excluding mine) with tweaks so that the tests pass again, made in downtime when i was failing to meet goals. it's just pleasant to upload it again because of the frustrating and surprising 500 errors on github.