#emc-devel | Logs for 2009-06-01

[00:49:06] <jepler> Roguish: yes, I beileve it will be an improvement
[05:56:45] <seb_kuzminsky> cradek: that means we all agree ;-)
[13:38:04] <cradek_> cradek_ is now known as cradek
[14:32:11] <skunkworks_> woo who0. compiled git checkout seems to work!
[14:33:03] <skunkworks_> took about 5 minutes to download the clone. (we have a bout a 3megabit connection here)
[14:44:08] <skunkworks_> wierd - for whatever reason - this laptop stopped throwing a realtime error. (both cvs and git checkout)
[14:44:15] <jepler> huh
[14:44:16] <jepler> I can't imagine why
[14:44:24] <skunkworks_> same here
[14:44:34] <skunkworks_> normally it happens right when emc starts.
[14:44:35] <cradek> warm weather?
[14:44:44] <cradek> (fan stays on or something)
[14:45:20] <skunkworks_> now it has been running for a good 20 minutes without an error. (and I am running stepper_inch)
[14:45:34] <skunkworks_> could be. plus I am plugged in..
[14:46:05] <skunkworks_> there it is - the second I unplugged the computer - rtapi error.
[14:46:26] <skunkworks_> maybe I never noticed that before.
[14:46:41] <cradek> cpu speed change maybe?
[14:46:46] <skunkworks_> most likely
[14:46:51] <skunkworks_> Good morning
[14:47:18] <cradek> hi
[16:03:31] <BJT-Work> what I don't fully understand about git yet is if I want to edit a 2.3 file vs a trunk file how that is done if you only have one set of files
[16:03:56] <BJT-Work> in cvs we have a local dir for 2.3 and one for trunk...
[16:06:23] <cradek> you can use git checkout to switch between the branches, or you could make a separate directory (git clone /local/path /new/local/path and then use git checkout in it)
[16:06:47] <cradek> you can make as many clones as you want - they are all equivalent
[16:07:08] <BJT-Work> ok, thanks
[16:07:35] <BJT-Work> only takes about 5 hours on dial up :)
[16:08:05] <cradek> don't clone over the modem again, clone your local one
[16:08:20] <BJT-Work> ok
[16:08:28] <cradek> should take no time
[16:08:34] <BJT-Work> I like the gui for git
[16:08:41] <cradek> gitk or some other one?
[16:09:29] <BJT-Work> well gitk is good for viewing but the commit button is not working yet
[16:09:41] <BJT-Work> qgit worked for the commit
[16:10:13] <BJT-Work> I just tried them for a few minutes but everything was pretty intuitive
[16:44:42] <jepler> there's a commit button in gitk?
[16:45:08] <BJT-Work> yea, but it is grayed out
[16:45:22] <BJT-Work> the one in qgit works
[16:45:27] <jepler> huh, I don't have that in gitk
[16:45:33] <jepler> might have to try qgit for commits
[16:45:43] <jepler> there's "git gui" for committing, but I found the interface hard to use
[16:45:49] <BJT-Work> I may not have something configured in gitk yet
[16:45:52] <jepler> (you have to use a menu item or keystroke to actually add a specific file to the commit)
[16:46:58] <BJT-Work> I like the feature in gitk that lets you navigate to a branch
[16:52:18] <jepler> gitk is one of the neatest things about git compared to cvs: you can quickly and visually see the whole project history
[16:53:35] <BJT-Work> and you can sort by name etc. and that is nice
[18:41:48] <skunkworks_> SWPLinux: missed the pre-show. How did it go?
[18:44:39] <SWPLinux> strangely, things didn't go well on Saturday, but they worked great on Sunday
[18:45:06] <skunkworks_> Nice :)
[18:45:13] <skunkworks_> a little stress?
[18:45:14] <SWPLinux> the other funny thing is that I'm not really in any of the photos, and nobody asked me any questions (they interviewed the guy who hired me instead)
[18:45:18] <SWPLinux> uh, yeah
[18:45:33] <SWPLinux> the MTV guys were really great though
[18:45:49] <SWPLinux> do you run your D945GCLF much?
[18:46:05] <skunkworks_> with windows - it is running all the time.
[18:46:17] <skunkworks_> with linux - I just tinker
[18:46:44] <SWPLinux> ok. I think I had a heat issue, so I'm curious about whether you've seen that as well
[18:46:52] <skunkworks_> I have not had any problems. (acutally the xp machine has been on for weeks)
[18:47:10] <SWPLinux> high workload?
[18:47:52] <skunkworks_> running a sat card - decripting video and displaying on the screen.
[18:48:02] <skunkworks_> I have not looked at cpu usage.
[18:48:53] <skunkworks_> plus it is mounted in a mid sized tower - so lots of room
[18:48:54] <SWPLinux> ok
[18:48:58] <SWPLinux> ah
[18:49:20] <SWPLinux> the little black boxes were basically in direct sunlight, and every once in a while they would just stop doing anything
[18:49:26] <SWPLinux> no ping responses, nothing
[18:49:28] <SWPLinux> then they
[18:49:44] <SWPLinux> then they'd start up again, and more or less continue from where they left off
[18:49:53] <skunkworks_> odd
[18:50:03] <SWPLinux> yep
[18:50:20] <SWPLinux> were you still in KS when Jon Elson talked about the overheat protection in Pentiums?
[18:50:24] <jepler> someone at fest was saying that thermal management will do that .. exactly
[18:50:30] <SWPLinux> yep
[18:50:46] <skunkworks_> huh - interesting. just stops for a while - then takes back off?
[18:50:52] <SWPLinux> yep
[18:51:29] <SWPLinux> I had ssh sessions going to all 12 of them, and I could see that sometimes they'd be in the middle of downloading an image from a camera, processing, or whatever
[18:51:30] <skunkworks_> did those cases have any external fans?
[18:51:36] <SWPLinux> one small one
[18:51:58] <SWPLinux> there's room for another, but of course there's no way to get flow-through due to the pci riser card
[18:52:08] <SWPLinux> it would just be two fans next to each other
[18:53:27] <SWPLinux> later - time to board
[19:05:13] <jepler> how do others feel about comment blocks like these?
[19:05:13] <jepler> +/***********************************************************************
[19:05:13] <jepler> +* INI FILE *
[19:05:13] <jepler> +************************************************************************/
[19:05:50] <jepler> I never write them myself
[19:06:30] <cradek> /***********************************************************************
[19:06:33] <cradek> they're stupid
[19:06:37] <cradek> ************************************************************************/
[19:06:42] <micges> I was thinking that they are usefull for > 1000 line fine..
[19:06:51] <micges> but ok I was wrong
[19:07:00] <cradek> :-)
[19:07:02] <jepler> how are they useful?
[19:07:07] <jepler> will you remember to search for them?
[19:07:21] <BJT-Work> I like
[19:07:25] <BJT-Work> # my comment
[19:07:47] <micges> no but geany has function to roll in functions
[19:08:22] <jepler> I don't understand what that means
[19:08:34] <micges> wfm
[19:09:40] <CIA-48> EMC: 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/axis/extensions/emcmodule.cc:
[19:09:40] <CIA-48> EMC: remove unused stuff, redundant stuff, and make whitespace a bit more consistent
[19:09:40] <CIA-48> EMC: (based on a patch from micges)
[19:10:16] <micges> I mean this : http://imagebin.ca/view/Y0j0FLS.html
[19:11:33] <jepler> oh. I think the word I've seen used for that is "fold"
[19:11:53] <micges> ok :)
[19:12:36] <jepler> fwiw I'd probably not have as much of a problem with // Ini file:
[19:12:43] <jepler> in my personal style I never format comments as big boxes
[19:14:40] <micges> I just copied them from homing.c in motion dir :P
[19:16:00] <jepler> that's not my style :/
[19:16:20] <micges> ok
[20:12:17] <micges> is changes in lines 19 and 20 are ok? http://www.pastebin.ca/1443985
[20:13:08] <micges> (while debugging interpl there are messages type names not numbers)
[20:13:27] <cradek> if it works, I think that is a good change
[20:13:49] <cradek> I don't know enough to say whether it is right, other than that
[20:14:23] <micges> thanks
[20:46:47] <micges> good night all
[21:17:35] <jepler> replacing '// #ifdef' with '#if 1' is not an improvement. Remove the #if altogether.