that's a manually generated file.
While we're on the subject of docs (and while I wait for a reboot), I was going to ask if there is a source somewhere for the "G Code Quick Reference" card (gcode.html) I found the gcode.html file, but it seems (and I may regret saying this, but...) that there should be a source (LyX?) so that there can also be an easily printable PDF version. Comments? Advice? Bronx Cheers?
KimK: docs/html/gcode.html is handwritten.
it's been years since it fit in one column on one page
html is extremely easy to print - I dare say a pdf is harder
The output of printed html can be inconsistent compared to a printed pdf
I bring it up because I heard a request for a second g-code ref page in strict numerical order for lookup. It sounded like a good idea to me. The card now is grouped by function, which is also good, we keep that.
And also because we might want a source for other reasons, if it won't fit on one page anymore, maybe a duplex trifold on A3/legal/whatever? Like those Vim reference cards you see, very handy. And the Lyx source could be handled "automagically" as we are doing everything now.
Just something to think about
Maybe after the rush I'll put something together and post it for public derision?
Of course, maybe LyX *isn't* the best choice if the idea is to make sure it fits on one page/two pages. That could lead to a lot of lather, rinse, repeat. Maybe (and I'm just throwing ideas out here) this shouldn't be done in LyX, so if not LyX, than what? OOo Writer or Calc? Suggestions? Rejections? Public Rioting?
I'm afraid I have no useful suggestion - I don't know how to make it reformattable like you want.
I can sympathize with whoever wants a list in numeric order, though. it would be better for reverse-engineering gcode if you don't already know it well.
[03:54:08] <cradek> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?WrappedRotaryAxes
ugh, someone (ahem) should document how this really works
EMC: 03cmorley 07v2.4_branch * r471643e574f5 10/src/emc/usr_intf/pncconf/pncconf.py: fix firmware directory names for 7i43 and 5i22
* Jymmm volunteers cradek to document how that really works!
Seriosusly? I'f think it would be the opposite....
# If the sign of the axis-word is "+", then the motion is counterclockwise
# If the sign of the axis word is "-", then the motion is clockwise
ccw is the positive angular direction in virtually the whole world except on clocks
I'm thinking compass.... 0 at 12oclock, 90 @ 3oclock, etc
in the math world, 0 is to the right, and angles increase counterclockwise
I was thinking this (and clocks)... http://en.wikipedia.org/wiki/File:Kompas_Sofia.JPG
The EU Protractors are BOTH 0-180 and 180-0 =)
[04:48:56] <cradek> http://upload.wikimedia.org/wikipedia/commons/thumb/4/4c/Unit_circle_angles_color.svg/720px-Unit_circle_angles_color.svg.png
zero @ 3oclock too
If any developer can tell me what the "debug" numbers mean in ClassicLadder's "Sections Manager", I will be happy to add the information to the docs. Screenshot: http://imagebin.ca/view/TibErk.html
Of F=, L=, P=, the only pattern I see is that P is always =0. F and L have no pattern that I can see as far as big/small, complex/simple, etc.
jepler: Do you happen to remember what classic ladder was missing for the print button to work? Some package? Random? ;)
skunkworks: AC_MSG_CHECKING(for libgnomeprintui-2.2)
AC_MSG_RESULT(no -- printing from classicladder will not be possible)
looks like it's libgnomeprintui
jepler: thanks for exhaustive git answer.. I had always done a git pull -rebase and somehow missed that change
mhaberler: I hope it clarified more than it confused
I have to do more reading on git - it really blows svn and cvs away but the rope is still a bit long for me.
it sure wouldn't suck to have floating-point support in rtapi_printf. it only sucks to implement it.
dtoa is the go-to implementation of float->ascii conversions .. only problems are that it performs memory allocations and seems to run for 17000 to 40000 CPU cycles on this system (5-13us @ 3.16GHz)
jepler: dtoa seem to be composition of two itoa and one float format parsing
is not it?
psha: converting the mantissa of a floating-point number accurately to decimal is very hard to get right in all cases
hm, i have to refresh memory about it...
I recommend this paper: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.164.813&rep=rep1&type=pdf
er, that's not the one I wanted
I think this is the one: http://kurtstephens.com/files/p372-steele.pdf
I've never implemented the algorithm, rather the paper convinced me to find a ready-made implementation based on the paper's algorithm (dtoa/gdtoa)
.. for a non-emc2 project, that is
i'll first glance trough 754 format specs...
yes, key word is 'accurate' :)
it's not that easy to decide how to round number as i expected...
yes, I'm sure there are tons of fast but wrong conversions
tempting to write a %A formatter for kernel space. It's easy to convert that to decimal in userspace, unlike the current hex representation.
$ printf '%f\n' 0XC.8F5C28F5C28F5C3P-2
I don't know what you're talking about, but that looks a lot more useful
seems easy to make a filter to make it human-readable
dmesg | scripts/fix-my-%f-please
here's %A-like formatter http://emergent.unpy.net/files/sandbox/fp_a.c
in case someone wants to fit it into rtapi_snprintf while my back's turned
huh, it's a bit to my surprise that the exponent in a %A-format is in decimal. $ printf '%A %A\n' $((2**12)) $((2**13))