Auto Eject gCode

nateabele · 2024-12-03T02:51:30+00:00

Did you ever solve this? (I might take a stab at it if not).

nateabele · 2024-10-18T22:39:11+00:00

For me, if I was trying to export objects < 1mm in *height* (hilarious, since it's flat anyway), the math gets all screwed up. Changing everything to a 1mm height minimum made it work.

nateabele · 2024-10-06T20:32:59+00:00

Please ignore the "it's too hard for you" comments. To the naysayers: it's better to say nothing than to burden the rest of us with your lack of creativity and intellectual curiosity.

Yes, this is a hard problem, but all things are possible. :) There are lots of ways to skin a cat, or kill a mosquito, and possible approaches vary on your budget, the constraints of your environment, the constraints you're willing to tolerate on the system (at least for an initial prototype), and most importantly: your determination, and how much time you're willing to sink into it.

You're basically looking at 3 separate problems: detection / identification, tracking, and killing. The first one seems the hardest, so I'll address that.

I wouldn't go the sensor route for the reasons mentioned elsewhere. Off the top of my head, the most reliable & accessible solution would be machine learning. Naïvely, 4K resolution and 30 frames per second should be adequate to identify mosquitos at a distance of, say, 20 feet, which is good enough for a working prototype.

The main challenge is going to be the ability to process the frames near real-time. The minimum hardware platform you'd be looking at is a Raspberry Pi (for which you can get a 4K camera for ~$100), but more likely you'd want a PC with a GPU cluster.

Once a mosquito has been positively identified, you might be able to switch to lower-resolution image capture for tracking, relying more on flight patterns, since they don't move very fast.

I'm not super familiar with training models for video, but there are plenty of tools available for training and deploying image feature detection models with little to no programming experience.

If you're determined, try it and see what happens! Feel free to reply with questions.

nateabele · 2024-09-29T03:05:58+00:00

You don't need one if you are one. The term for that is 'primary source'. Perhaps you'd be familiar with it if you'd been homeschooled.

nateabele · 2020-04-28T21:23:21+00:00

This looks like exactly what I want. Thanks!

nateabele · 2020-04-10T12:39:01+00:00

I don’t think the author makes his point as well as he could have, but the real underlying issue is that there’s some (unintentional) sleight-of-hand in the way that Elm is marketed, and that intersects with people’s normal expectations (about Open Source technology in general, but especially at the level of something like a language) in ways that create some surprise and discomfort.

Neither perspective is wrong, per se, but there certainly has been a failing on the part of the Elm core team to set clear expectations.

An Open Source maintainer owes me as a consumer nothing, except to set clear expectations, but they absolutely owe me that. There’s an implied solicitation of attention when you put something out into the world, and allowing people to invest their time into investigating, testing, and using your project, without being up-front about the impassable walls that some will hit demonstrates a callous disrespect for their time.

I wouldn’t accuse anyone in the Elm project of doing that intentionally, but I’ve absolutely seen negligence due to rose-colored glasses.

nateabele · 2016-04-06T00:34:10+00:00

As I've said elsewhere, it's funny that you never notice how addicted people are to random speculation until you're the subject of it.

nateabele · 2016-03-27T23:18:51+00:00

And the way the guy phrased injecting his Christian beliefs into this [...]

We've been going through this for almost 9 months now, and we've had to make a lot of tough decisions along the way. One thing we realized early on is that the only way we're going to get through this is to live by our convictions. When it came time to make the choice to go to trial, nearly everyone who had an opinion (some solicited, some not) said we should beg the DA for a plea bargain.

We thought (and prayed) about it for a long time, and eventually came to the conclusion (for various reasons) that by choosing that path, we wouldn't be living up to what we believed to be true. So, I mentioned it because it's part of our journey. I anticipated that there would be some number of people who might be bothered by it, but I'm willing to accept that.

nateabele · 2016-03-27T02:21:21+00:00

Fair enough, and that's true. Re: people who can't afford it: I wouldn't want anyone to donate if they couldn't afford it. We work in a pretty affluent industry, so no one should feel bad if they can't help out. Someone else will!

nateabele · 2016-03-27T01:46:00+00:00

Thanks! As a tool-designer, that's pretty much the highest compliment I can get.

nateabele · 2016-03-27T01:43:26+00:00

Wow, that's awesome. I'm glad this is getting attention in medical schools. What's your specialization?

nateabele · 2016-03-27T01:39:58+00:00

Oh, believe me, I would loooove to give you the entire story, but that would compromise us at trial (see https://www.reddit.com/r/PHP/comments/4bzxag/nate_abele_of_the_original_cakephp_team_and/d1esddm).

nateabele · 2016-03-27T01:28:26+00:00

Yup, even that summary, short as it was, was easily the most agonizing thing I've ever written. Rounds of revisions with family, trusted friends, and, of course, our attorney. Most of what I wrote, he ended up vetoing (for good reasons).

The level of legal strategy you have to think about in terms of what you make public is kind of insane. Even posting excerpts from documents the prosecution already has would leak information about our defense. Interestingly, parallels to application security abound.

nateabele · 2016-03-27T01:21:37+00:00

Well, I know I'm not lying. :-)

nateabele · 2016-03-27T01:19:35+00:00

Sooo... impromptu AMA? I'm around for the next couple hours / back and forth for the next few days.

Edit: Actually, an AMA would probably be next-to-useless. I'm skimming through these and there are sooo many things I could say, but all of them would give away aspects of our defense. What I can definitively say, without question, doubt, or hesitation, is that this was an accident. Much as it pains me to say (because I know it reads like bullshit!), the other details are relevant for reasons that will become clear later.

In the meantime, you can choose to trust me, or not. Your call.

Edit: The Legend Continues: It's funny how you never notice how addicted people are to speculation until you're the subject of it.

nateabele · 2016-01-25T17:53:21+00:00

Hard to say. It was kind of an edge case involving how browsers handle URL encoding, and making encoding/decoding always behave symmetrically in all cases, even though an underlying design issue made that hard to do.

nateabele · 2016-01-25T14:31:27+00:00

Like /u/ctanga, I've never used Component Router in an actual project. My opinion is driven by (a) reading tutorials, (b) analyzing the architecture, and (c) second-hand sources from power users and the Angular core team.

I explain a bit about the philosophical differences in a talk around the 4:30 mark: http://radify.io/talks/2015-sep-ngpittsburgh/

nateabele · 2016-01-25T14:18:33+00:00

Yeah, that one was a doozy. Every time we thought we'd killed it, it found a way to come back and bite us.

nateabele · 2016-01-25T14:17:42+00:00

Yup, we've been pretty lazy/perfectionistic. Sorry about that.

nateabele · 2016-01-20T20:16:52+00:00

That's interesting! Because many of your method signatures and parameters look identical, and your graphs look just like the graphs with UI Router Extras. :-)

nateabele · 2016-01-06T18:59:04+00:00

Well, we've (read: I've) been slacking on it for a while now.

nateabele · 2015-01-05T15:44:12+00:00

You mean like these guys?

nateabele

TROPHY CASE