Back
[11:10:29] <madeline> hi
[11:12:41] <ace4016> hello
[11:13:00] <madeline> how are you?
[11:15:47] <ace4016> doing alright; yourself?
[11:19:58] <madeline> I'm doing well
[13:27:26] <anonnumberanon> sup
[13:27:58] <ace4016> ahoy
[13:39:06] <rue_house> NI
[13:40:28] <rue_house> er, I mean
[13:40:31] <rue_house> ekki-ekki-ekki-ekki-ptang-zoom-boing-mrowr
[13:54:05] <anonnumberanon> gnu gpl3 good for github?
[14:25:50] <rue_shop5> ?
[14:55:20] <anonnumberanon> man git
[14:55:47] <anonnumberanon> im making my first github post mang
[15:09:57] <anonnumberanon> https://github.com/MobileSuitTech
[15:10:00] <anonnumberanon> here it is
[15:10:11] <anonnumberanon> u can check out the code now rue_shop5
[15:30:39] <rue_shop5> remember, its better to stream this so its not using a lot of memory, on the grounds it'll be running on an avr
[15:31:46] <rue_shop5> anonnumberanon, did you see the code I did that seems to work really well right now?
[15:32:07] <rue_shop5> rephrasing your code to fit in the system I'm using would be a bit of a chaor
[15:32:09] <rue_shop5> :/
[15:47:28] <anonnumberanon> rue_shop5, yeah there are many things in this program that can be much better, for example don't need an array of 56 combinations, minimum required is just saving the current combinations, comparing it with the currently just calculated combination and store the new one in its place if the new one is better. I could make these changes if the application calls for it.
[15:47:53] <anonnumberanon> >saving the current combinations
[15:48:15] <anonnumberanon> Oops no I meant to write combination, only save one combination at a time.
[15:51:34] <anonnumberanon> I may come back to the x, r of robot problem later on today but I'm learning how to draw a PCB first.
[15:53:09] <rue_shop5> I check them as I go, and remember them if they win
[15:55:48] <anonnumberanon> By any good programming standard, yes that's how it should be done.
[15:57:57] <anonnumberanon> But I'm thinking of streaming remark now. Maybe do something every time that you get a new angle/beacon. But that doesn't really make sense or is hard to visualize. Would need to see how the beacons are acquired first. How fast, how many during one sample collection, etc.
[15:58:17] <anonnumberanon> In any case this code is already fast so further optimization may be moot.
[18:11:49] <cnnx> hi, any of you know where I can buy replicas of the mars curiosity rover wheels/tires/legs? in a smaller diameter of course, but that I could use for my own rover
[18:12:00] <cnnx> or do I need to print them with a 3d metal printer
[18:29:33] <cnnx> or does a company sell a chassis alreaday
[18:29:36] <cnnx> already
[18:41:23] <robopal> contact nasa jpl center; public relations office
[18:45:42] <cnnx> robertj: okay thanks will do
[19:22:58] <cnnx> is the 3040 chinese cnc machine good for milling robot parts in mteal or aluminium?
[19:23:05] <cnnx> like wheels or arms or chassis
[19:24:12] <orlock> Aluminium is a metal.. and it would depnd on the grade end speed
[19:24:16] <orlock> i'd say "maybe"
[19:24:23] <cnnx> okay
[19:24:41] <orlock> but depending on the strength you need.. just 3d print them
[19:24:55] <cnnx> are they other better suited 3d pritners
[19:24:58] <cnnx> for robot parts
[19:25:03] <cnnx> like 1000$ range
[19:25:22] <orlock> Depends on your requirements - a prusa is fine for me
[19:25:28] <cnnx> let me google it
[19:25:50] <cnnx> i want to build a solar powered outdoor robot
[19:26:00] <cnnx> is it big enough to create pieces that big
[19:27:39] <orlock> 200x200x180ish build volume
[19:27:57] <orlock> you are asking how long a bit of string is
[19:32:34] <cnnx> orlock: laptop battery died, i'm back
[19:33:06] <orlock> cnnx: you are asking how long a bit of string is
[19:33:16] <cnnx> yeah
[19:33:19] <cnnx> i realize