| 01:04.50 | hcurtis | Page 2 of the MGED Quick Reference Card has a graphic that very clearly illustrates the differences between groups, regions, and primitives. I understand that much better now. |
| 01:32.15 | Notify | 03BRL-CAD Wiki:Inderpreet * 7328 /wiki/User:Inderpreet/GSoC14/logs: /* Week 5 */ |
| 02:06.03 | hcurtis | Since group_head appears on lines 213, 885, 910, 914, and 2944 of fast4-g.c in commit 56495, I need to correct the code in and near all of these places (maybe not on line 885). |
| 03:08.23 | hcurtis | I researched this, but I could not find a clear answer. When I allocate memory for the group_head wmember list in BRL-CAD's fast4-g.c, should I use bu_*alloc() or bu_get()? |
| 03:10.02 | hcurtis | I do know that bu_*alloc() is right for items that are large or infrequently needed. In contrast, bu_get() is suitable for small pointers and is faster. Sean said he wants fast4-g.c to be faster, but maybe group_head is too large for bu_get() to handle. Does anyone here know? |
| 04:46.11 | *** join/#brlcad caen23 (~caen23@92.83.166.162) |
| 05:26.19 | Notify | 03BRL-CAD Wiki:Hcurtis0010 * 7329 /wiki/User:Hcurtis0010/GSoC2014/logs: /* Week 5 */ |
| 05:28.30 | *** join/#brlcad jordisayol (~jordisayo@unaffiliated/jordisayol) |
| 05:30.12 | *** part/#brlcad jordisayol (~jordisayo@unaffiliated/jordisayol) |
| 05:47.59 | Notify | 03BRL-CAD Wiki:Hcurtis0010 * 7330 /wiki/User:Hcurtis0010/GSoC2014/logs: /* Week 5 */ |
| 06:39.38 | *** join/#brlcad hsrai (~hsrai@202.164.53.116) |
| 08:54.33 | *** join/#brlcad albertcoder (~albertcod@101.215.122.150) |
| 10:09.56 | *** join/#brlcad javampire (~ncsaba@p4FF73698.dip0.t-ipconnect.de) |
| 10:11.02 | javampire | kanzure: Hi Bryan, I see you merged Raj's pull request, thanks for that ! |
| 10:12.12 | javampire | kanzure: if you want also to participate in the discussion I have with Raj please let us know, although it will be a challenge to find times which accommodates the time-zones of all 3 of us... |
| 10:21.03 | *** join/#brlcad zxq9 (~ceverett@FL9-125-199-207-150.okn.mesh.ad.jp) |
| 10:32.18 | *** join/#brlcad piyushparkash (~piyushpar@117.205.70.67) |
| 11:34.59 | *** join/#brlcad piyushparkash (~piyushpar@117.205.70.67) |
| 12:58.27 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 14:09.28 | Notify | 03BRL-CAD Wiki:Popescu.andrei1991 * 7331 /wiki/User:Popescu.andrei1991/devlogs2014: /* Week 5 */ |
| 14:09.46 | Notify | 03BRL-CAD Wiki:Popescu.andrei1991 * 7332 /wiki/User:Popescu.andrei1991/devlogs2014: /* Week 5 */ |
| 15:51.23 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 15:56.57 | *** join/#brlcad piyushparkash (~piyushpar@117.205.70.67) |
| 16:00.26 | *** join/#brlcad albertcoder (~albertcod@49.138.114.182) |
| 16:59.04 | *** join/#brlcad albertcoder (~albertcod@101.214.136.151) |
| 16:59.43 | *** join/#brlcad alisha (~alisha@101.62.202.87) |
| 17:06.11 | *** join/#brlcad albertcoder (~albertcod@101.214.136.151) |
| 17:11.57 | *** join/#brlcad albertcoder (~albertcod@101.214.136.151) |
| 17:23.38 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 17:33.09 | *** join/#brlcad hcurtis (b82d188d@gateway/web/freenode/ip.184.45.24.141) |
| 18:22.21 | *** join/#brlcad piyushparkash (~piyushpar@117.205.70.67) |
| 18:52.00 | *** join/#brlcad albertcoder (~albertcod@101.208.230.229) |
| 18:56.37 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 20:36.03 | *** join/#brlcad albertcoder (~albertcod@49.138.76.9) |
| 20:51.05 | Notify | 03BRL-CAD Wiki:Albertcoder * 7333 /wiki/User:Albertcoder/GSoC2014/logs: /* Week 5 */ |
| 21:35.01 | Notify | 03BRL-CAD Wiki:Ankeshanand * 7334 /wiki/User:Ankeshanand/GSoC14/logs: /* Week 5 */ |
| 21:48.47 | clock | has anyone used brl-cad for purpose of 3D printing? |
| 22:45.04 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 23:18.12 | hcurtis | I am working on the fast4-g.c task. I see that group_head appears five times in the program. I need to figure out what form these stack-allocated instances of group_head will take upon becoming dynamically allocated. |