Back
[00:04:57] <fenn> as long as they dont say "you cant reproduce this EMC image" then it should be fine
[00:24:22] <SWPadnos> yes, though it's hard to tell
[00:24:48] <SWPadnos> it does look as though it's acceptable to stick an image into some other work, as long as each item is credited appropriately
[00:25:12] <SWPadnos> but there is the option of the creator of the work to request that it be removed, which could cause complications
[00:25:30] <SWPadnos> I think I'll have a text-only paper :)
[00:33:52] <jepler> SWPadnos: the 4.1 "upon request, remove" item in the license refers to removing the "reference to Licensor or Original Author", not to removing the original work from a derivative work
[00:35:09] <SWPadnos> ah - thank you. my eyes are glazing over, especially when looking at legalese on an over-bright low resolution LCD :)
[00:35:22] <SWPadnos> with a crappy font
[00:35:44] <jepler> and, on my browser, not word-wrapped
[00:36:11] <SWPadnos> mine either, hence the crappy font (in Programmer's Notepad, word-wrapped but not much better for it)
[00:36:59] <SWPadnos> it is amazing how much better it looks on a high-ish quality CRT (same size/resolution)
[03:49:21] <jmkasunich> hi yall
[03:49:31] <cradek> back home?
[03:49:35] <jmkasunich> yep
[03:49:44] <jmkasunich> looking around for a trout
[03:49:46] <cradek> cool.
[03:50:00] <cradek> I forget what that was for, but it seemed like it was sure needed
[03:50:22] <jmkasunich> somebody who will remain unnamed wanted to replace stepgen with freqgen and PID
[03:51:42] <cradek> oh, that was surely just a troll :-)
[03:51:50] <SWPadnos> :P
[03:52:11] <jmkasunich> slap!
[03:52:15] <cradek> haha
[03:52:45] <SWPadnos> actually, it wasn't a desire to replace stepgen that drove me. it was the (re-)realization that STEPGEN_MAXACCEL + MAX_ACCEL per axis is really stupid, and sometimes even confusing
[03:53:23] <jmkasunich> unfortunately the magic "pretuned PID loop" in stepgen relies on a max accel value for the tuning
[03:54:01] <SWPadnos> just the fact that there had to be two ini values, that are different but related (in strange ways) is kind of a hack
[03:54:08] <SWPadnos> but it's the lesser hack of evils or something
[07:31:56] <alex_joni> how about having only STEPGEN_MAXVEL in the ini?
[07:32:14] <alex_joni> then ini_axis can catch that, and set the axis MAXVEL to something lower (like 5-10%)
[07:32:42] <alex_joni> and if the user doesn't like that, he just has to define MAX_VELOCITY to override the default
[14:26:08] <fenn> alex_joni: since that's so obvious, how could we have missed it? what's the catch
[14:43:24] <cradek> I did that many moons ago in the TP (95%). Since we (jmk) didn't want to do the same thing for jogging, there was no point, so I took it out.
[14:47:56] <cradek> better would be to have stepgen 105% and emc 100%, so the numbers look right when the user sees them
[14:48:38] <skunkworks_> Yes - I was confused with my engraver why I wasn't getting the max velocity
[14:48:47] <skunkworks_> that is about when you took it out
[14:50:56] <fenn> why does it matter what the user sees? answering a curious question is easier than multiple config values that must be manually calculated
[14:51:26] <cradek> because still better is avoiding curious questions AND finicky values
[21:09:01] <fenn_> fenn_ is now known as fenn