| 00:30.40 | *** join/#brlcad Iordanis__ (Iordanis@host214-207.cvd.fit.edu) |
| 01:33.50 | *** join/#brlcad zero_level (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 01:53.54 | brlcad | hi zero_level |
| 01:54.14 | zero_level | hii.. |
| 01:55.08 | zero_level | i am currently working on a patch that will load images in the icv library |
| 01:55.15 | zero_level | that was missing there. |
| 03:02.05 | *** join/#brlcad zero_level (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 03:02.55 | brlcad | zero_level: sounds good |
| 03:15.26 | zero_level | i believe we dont get patch notification on this window.. |
| 03:20.14 | *** join/#brlcad kesha_ (~kesha@14.139.122.114) |
| 03:33.06 | zero_level | @blcad earlier i thought of using cxImage library but i think when u said why do i use this, i actually had no reason to justify i tried to find all night about why cxImage is better, then i compared the codes of cxImage and current utilities.. |
| 03:35.58 | brlcad | zero_level: yeah, no notification for patches (until they are committed) |
| 03:36.10 | zero_level | but seeing that i found cxImage may not be that good because the brlcad's IPTs make use of the pix and bw format very efficiently and using cxImage library we will have to read the whole image in one go, which in current scenario is read line by line |
| 03:37.27 | zero_level | i have thus planned to re work on my proposal and as u suggested include only the cosolidation part and improvements in the usability and addition of options, |
| 04:12.26 | *** join/#brlcad kesha_ (~kesha@14.139.122.114) |
| 04:15.36 | *** join/#brlcad Iordanis__ (Iordanis@host214-207.cvd.fit.edu) |
| 04:56.43 | *** join/#brlcad kesha (~kesha@14.139.122.114) |
| 04:57.48 | kesha | My eyes are unable to catch ADD NEW button on https://sourceforge.net/p/brlcad/patches/ |
| 04:58.09 | kesha | Where is that button ? |
| 05:00.47 | kesha | I want to submit a patch .. |
| 05:31.23 | brlcad | hello kesha |
| 05:34.07 | brlcad | kesha: are you logged in? |
| 05:34.34 | brlcad | kesha: there should be a "Create Ticket" button on the left |
| 05:34.36 | kesha | yes.. |
| 05:34.45 | kesha | I found it just a sec ago.. |
| 05:34.48 | kesha | Thanks.. |
| 05:34.58 | brlcad | lots of ..... |
| 05:35.07 | kesha | The label has been changed !! |
| 05:35.18 | brlcad | yeah, the whole interface was changed last week |
| 05:36.13 | kesha | http://brlcad.org/wiki/Patches should also be modified accordingly... |
| 05:38.14 | kesha | brlcad: i want to dedicate doing code refactoring this summer with brlcad.. my exams completed today and now I will get time.. |
| 05:38.53 | kesha | in code Refactoring projects, I picked up "move LIBWDB comments " and changed them in 10 mins.. It was just a small piece of work.. |
| 05:39.18 | kesha | I want to do some hardcore refactoring.. |
| 05:39.21 | kesha | now.. |
| 05:41.11 | brlcad | kesha: it's a wiki, go for it ;) |
| 05:41.19 | kesha | brlcad: Can you help me planning out how to go about systematically.. I mean if the development schedule is made wisely and good, then it reduces half the mess.. |
| 05:41.44 | brlcad | kesha: what's your background? |
| 05:42.37 | brlcad | just the short/quick version, highlights ;) |
| 05:42.50 | kesha | brlcad: I have completed Second Year B.Tech in Information and Communication technology .. Have a good grasp on C.. |
| 05:43.05 | brlcad | what is a B.Tech? |
| 05:43.06 | kesha | yea ! :P |
| 05:43.34 | kesha | Bachlor of Technology ..This is what its called in India' |
| 05:43.37 | kesha | ;) |
| 05:44.07 | brlcad | okay |
| 05:44.33 | brlcad | how long have you been programming? started in college? |
| 05:44.43 | brlcad | i.e., 2 years? |
| 05:44.45 | kesha | brlcad: I have done courses on system level programming, object oriented programming and ofcourse, introduction to programming |
| 05:44.53 | kesha | no.since 11th grade ... |
| 05:44.56 | kesha | i.e 4 years.. |
| 05:45.06 | brlcad | how long with C? |
| 05:46.00 | kesha | brlcad: Officially it was in 1st year college, but I was very enthusiatic and did a course to learn C , C++ before entering college.. |
| 05:46.13 | kesha | brlcad: 4 years with C.. |
| 05:46.51 | brlcad | you really don't need to end every sentence with ... |
| 05:47.07 | brlcad | relax :) |
| 05:47.11 | kesha | oops ! |
| 05:47.38 | kesha | realised after you pointed it out |
| 05:49.42 | brlcad | kesha: so if you had to identify three of our project ideas that were the most interesting, what would they be? |
| 05:54.56 | kesha | brlcad: First of all, my first priority would be Code Refactoring, next is GUI and thirdly, am not so confident about Geometry Conversion and Processing, but after I do some searching and surfing, I can say better on that topic. |
| 05:57.13 | kesha | brlcad: If Refactoring is not of high impact as of now, I would love to go for GUI. |
| 06:00.37 | kesha | Integrating with Analysis tools in GUI . |
| 06:16.31 | *** join/#brlcad rays2pix (~deepak@14.139.226.34) |
| 06:37.08 | brlcad | kesha: code refactoring is an entire category or projects |
| 06:37.43 | brlcad | I would encourage some consideration of geometry conversion and processing, not a lot of interest in that area to date |
| 06:37.59 | brlcad | again though, those are all major areas of development, what specifically interests you? |
| 06:51.32 | *** join/#brlcad priyanka (~priyanka@118.102.186.30) |
| 07:01.01 | *** join/#brlcad vladbogo (~vlad@86.121.101.132) |
| 07:36.32 | *** join/#brlcad kesha (~kesha@14.139.122.114) |
| 07:41.46 | *** join/#brlcad kesha_ (~kesha@14.139.122.114) |
| 08:40.48 | *** join/#brlcad kesha_ (~kesha@14.139.122.114) |
| 08:47.09 | *** join/#brlcad ncsaba (~ncsaba@p54982FD5.dip0.t-ipconnect.de) |
| 08:50.03 | *** join/#brlcad kesha_ (~kesha@14.139.122.114) |
| 08:56.51 | ncsaba | Hi all |
| 08:57.54 | ncsaba | anybody knows if there is already some (visible, public) project to illustrate the parameters of the different promitives ? |
| 08:58.08 | ncsaba | s/promitives/primitives |
| 09:01.09 | ncsaba | OK, I suppose this page could be augmented: http://brlcad.org/wiki/BRL-CAD_Primitives |
| 09:23.33 | ncsaba | and this one should also be augmented with figures: doc/html/manuals/mged/brlcad_solids.html |
| 09:29.16 | ncsaba | I would add the "Primitive Solids" as a separate link in the "mged" table of contents - from my POV it is the most important page for BRLCAD beginners ! |
| 09:31.07 | *** join/#brlcad zero_level (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 09:31.51 | ncsaba | I will start to create some drawings for the parameters of the most frequently used (by me) primitives |
| 09:49.49 | *** join/#brlcad Kseniia (~kvirc@46.98.81.52) |
| 09:50.30 | *** join/#brlcad Kseniia (2e625134@gateway/web/freenode/ip.46.98.81.52) |
| 10:15.29 | *** join/#brlcad kesha_ (~kesha@14.139.122.114) |
| 11:15.11 | *** join/#brlcad vladbogo (~vlad@86.121.101.132) |
| 12:04.38 | *** join/#brlcad vladbogo_ (~vlad@86.121.102.254) |
| 12:10.08 | *** join/#brlcad vladbogo__ (~vlad@86.124.248.194) |
| 12:11.09 | *** join/#brlcad ncsaba (~ncsaba@p54982FD5.dip0.t-ipconnect.de) |
| 12:16.38 | *** join/#brlcad vladbogo_ (~vlad@86.121.101.110) |
| 12:34.02 | *** join/#brlcad rays2pix (~deepak@14.139.226.34) |
| 13:19.00 | *** join/#brlcad jasleen (~chatzilla@117.255.245.52) |
| 13:44.09 | ncsaba | anybody knows where can I find a reference for the available parameters of each shader type ? |
| 13:45.21 | ncsaba | I actually looked over all documentation I could find in the svn checkout, plus googled for "brlcad shader parameters" -> there's no useful result ! |
| 13:46.15 | ncsaba | I really find this as the biggest problem of brlcad - everything is there you could use, just so hard to find that it is practically useless |
| 13:47.42 | ncsaba | I go and look into the source code, and will figure out the plastic shader parameters I can use - but really, this is not how it should work |
| 14:12.15 | starseeker | ncsaba: it's open source - help to fix it! |
| 14:14.21 | *** join/#brlcad cstirk (~quassel@c-71-56-216-45.hsd1.co.comcast.net) |
| 14:15.23 | brlcad | ncsaba: there's a document on the website |
| 14:15.27 | brlcad | under documentation |
| 14:16.26 | brlcad | http://brlcad.org/w/images/2/2c/Optical_Shaders.pdf |
| 14:16.55 | ncsaba | well I can't help fixing it all at once -> I'll do now some pictures of the primitive parameters, I find that the most important |
| 14:16.58 | brlcad | ncsaba: I think we all agree that the shader subsystem sucks too ;) |
| 14:17.20 | brlcad | or at least is terribly difficult to find |
| 14:17.25 | ncsaba | that one pdf I already found |
| 14:17.29 | brlcad | it's been documented several times in several ways over the years |
| 14:17.56 | ncsaba | but that one only mentions 2 parameters of the plastic shader if I'm not mistaken |
| 14:17.59 | zero_level | @ brlcad can u tell me the need of magic number for icv_image_file |
| 14:19.04 | brlcad | ncsaba: if you right-click each input field on the combination editor, there is a description |
| 14:19.28 | ncsaba | BTW, I'm also searching for text annotations in BRLCAD, I suppose there's no such thing implemented yet ? Would help me now at the current task of picturing parameters |
| 14:19.43 | brlcad | zero_level: nearly all of our structures have a "magic number" that is used for memory corruption detection |
| 14:19.56 | ncsaba | brlcad: ok, that's something I didn't try, I'm not really using the GUI, all is done via CL |
| 14:20.25 | brlcad | zero_level: simple concept, you set a value like 0x12341234 and check that the value is that every time you use it ... if it's ever not 0x12341234 then you know you have bad memory |
| 14:21.00 | brlcad | ncsaba: you are correct, there are presently no text annotations but that's actually a task being currectly worked |
| 14:21.39 | brlcad | ncsaba: man mater may give some insight |
| 14:21.48 | zero_level | i have created a structure in my patch for the size, do you suggest putting a magic number there. ? |
| 14:21.54 | *** join/#brlcad chalk (272f0c7c@gateway/web/freenode/ip.39.47.12.124) |
| 14:21.57 | *** join/#brlcad code_walker (~Shubham@120.59.146.195) |
| 14:22.03 | brlcad | we do need some way to interactively query the shader system for available shaders, their parameters, and documentation |
| 14:22.03 | chalk | hello |
| 14:22.10 | brlcad | maybe a "shader" command to replace "mater" |
| 14:22.35 | brlcad | zero_level: don't worry about magic numbers right now |
| 14:22.39 | brlcad | hello chalk |
| 14:23.16 | ncsaba | brlcad: thanks for the shader hints, that helps -> would be perhaps good to add them to the glossary text for "shader"/"mater" |
| 14:23.19 | chalk | hey i need some advice on the idea i have chosen |
| 14:25.56 | *** join/#brlcad code_walker (~Shubham@120.59.146.195) |
| 14:26.32 | ncsaba | brlcad: the shader man page is not really helpful for shader parameters, but the GUI has good help text |
| 14:26.40 | chalk | well i am an undergraduate student and i have taken two courses on C++,one is Algorithm and computing and the other one is Object-oriented programming and data structures. During my courses, i have debugged alot of programs on C++ and was wondering whether i am eligible to take on the idea of fixing bugs.... |
| 14:26.49 | code_walker | brlcad |
| 14:27.15 | code_walker | i have made successfully a small version of cpd |
| 14:27.18 | code_walker | in c |
| 14:28.04 | ncsaba | brlcad: what is the status of the text annotations project, is there anything usable already ? |
| 14:28.09 | ncsaba | some pointers ? |
| 14:28.30 | code_walker | i needed to know,should i adapt current cpd in c |
| 14:28.56 | code_walker | this regarding code reduction |
| 14:29.00 | code_walker | is* |
| 14:29.18 | chalk | hey brylcad are you there? |
| 14:29.48 | code_walker | ya u there? |
| 14:31.26 | chalk | okay well i needed to ask that what kind of programs would be assigned to us if i apply to fix bugs? |
| 14:35.32 | chalk | umm... |
| 14:36.07 | chalk | ...can anyone answer my question |
| 14:36.18 | ncsaba | brlcad: I would add this line to the entry for "shader" in the "doc/html/manuals/mged/brlcad_glossary.html" file: |
| 14:36.19 | ncsaba | For a list of available shaders and the meaning of the parameters |
| 14:36.19 | ncsaba | open the combination editor in mged, select a shader, and right click on the input fields. |
| 14:36.32 | brlcad | ncsaba: hm, it looks like the appendix seen on the website is not something actually recorded in docbook |
| 14:36.48 | brlcad | I presume the intent there is that it would be auto-generated based on keywords and commands used |
| 14:37.13 | ncsaba | which appendix ? |
| 14:37.26 | brlcad | so might just help to beef up the "mater" command documentation, doc/docbook/system/mann/en/mater.xml |
| 14:37.55 | brlcad | ncsaba: "the glossary text" I presumed you were referring to the command/keyword appendix in volume II |
| 14:38.04 | brlcad | otherwise, what glossary text ;) |
| 14:38.12 | ncsaba | "doc/html/manuals/mged/brlcad_glossary.html" |
| 14:38.35 | brlcad | chalk and code_walker: run this: /msg ibot ask |
| 14:39.02 | chalk | how? |
| 14:39.12 | brlcad | what do you mean how? |
| 14:39.16 | brlcad | with your keyboard |
| 14:39.17 | brlcad | you type it |
| 14:39.23 | chalk | okay okay sorry |
| 14:40.17 | brlcad | chalk: you're welcome to submit a proposal for absolutely anything really |
| 14:40.27 | brlcad | but I would suggest proposing something as specific as possible |
| 14:40.40 | code_walker | brlcad:i have made a small version of cpd in c |
| 14:40.42 | brlcad | fixing bugs is great and all, but it's usually a cop-out |
| 14:41.02 | brlcad | code_walker: you already said that :) |
| 14:41.23 | code_walker | ya but presumed u didn't noticed that |
| 14:41.33 | code_walker | so i repeated it |
| 14:42.23 | code_walker | i think this project code reduction is mainly to adapt current cpd in c |
| 14:42.29 | code_walker | and c++ |
| 14:42.32 | brlcad | I did notice it, I read pretty much everything (as do most on IRC) ;) |
| 14:42.49 | code_walker | k |
| 14:42.50 | brlcad | what does that mean to you "adapte current cpd in c/c++"? |
| 14:42.54 | code_walker | my bad then |
| 14:42.56 | ncsaba | brlcad: what I would like to see is some kind of brlcad reference which you can consult when you actually know what you want to do but not exactly how... as opposed to a tutorial where you want to learn things you don't know about the new software |
| 14:43.05 | code_walker | pmd-cpd |
| 14:43.14 | chalk | i am not coping out, its just that i really want to participate in google summer of code and this is the thing which i actually understood completely. |
| 14:43.24 | brlcad | ncsaba: and how to go about presenting that? |
| 14:43.27 | ncsaba | I find most of the things are scattered in tutorials currently |
| 14:43.28 | brlcad | there is the apropos command |
| 14:43.36 | brlcad | which searches the short descriptions |
| 14:43.45 | brlcad | ala unix apropos command |
| 14:44.08 | brlcad | chalk: I wasn't suggesting that you specifically are coping out, my bad |
| 14:44.26 | code_walker | actually this project is mainly to improve the current verdions of cpd's that are there in the market right now |
| 14:44.28 | brlcad | I was suggesting that usually the person suggesting that is capable of far more, but just shy or haven't done their research |
| 14:44.35 | chalk | no no iits okay |
| 14:45.02 | chalk | well actually i did my research |
| 14:45.25 | chalk | and fixing bugs is all i could completely undestand...honestly |
| 14:45.34 | ncsaba | brlcad: well a reference, which explains the exact meaning of things - so if I want to look up a primitive for example, I know exactly the meaning of all parameters |
| 14:46.01 | chalk | what i want to ask is that if i apply to fix bug, what chance do i have of being selected?? |
| 14:46.06 | ncsaba | right now I'm still experimenting till I get it right |
| 14:46.14 | brlcad | chalk: all you could completely understand is probably a function of research and terminology |
| 14:46.21 | brlcad | several of the ideas are very simple |
| 14:47.00 | ncsaba | the mged commands page is a good reference, but it's not all |
| 14:47.04 | brlcad | I propose a challenge to the way you're thinking about the ideas page though |
| 14:47.14 | brlcad | it's not a dinner menu |
| 14:47.19 | brlcad | you're not picking something to do |
| 14:47.42 | brlcad | it's merely a page of recipe titles |
| 14:48.06 | brlcad | it's your job to come up with something interesting (to you!), an interesting dish to make that others will probably like too |
| 14:48.41 | ncsaba | brlcad: I will come back to the BRLCAD reference later - right now I will focus on creating images for the primitive parameters |
| 14:48.42 | brlcad | you're the chef, not the consumer |
| 14:48.58 | brlcad | ncsaba: we have a primitive reference in our todo |
| 14:49.03 | brlcad | along with a slew of other docs |
| 14:49.25 | brlcad | see the very bottom of the TODO file |
| 14:49.29 | ncsaba | yes, but I need that primitive reference _now_ for my own use :-) |
| 14:49.40 | ncsaba | so if there is none, I will do it myself |
| 14:49.47 | *** join/#brlcad code_walke (~Shubham@120.59.146.195) |
| 14:49.54 | ncsaba | if you have any partial results, please point me to it... |
| 14:49.55 | brlcad | BRL-CAD Ray Tracing Shaders and BRL-CAD Primitives are the two relevant ;) |
| 14:50.11 | brlcad | there is a primitive reference now, at the back of volume II |
| 14:50.23 | brlcad | it's just not very explanatory |
| 14:50.25 | ncsaba | ok, let mes see |
| 14:50.35 | brlcad | it identifies everything with pictures, though |
| 14:50.45 | *** join/#brlcad code_walker (~Shubham@120.59.146.195) |
| 14:51.01 | code_walker | brlcad:u there? |
| 14:51.05 | brlcad | the TODO entry is to make that a stand-alone document with even more detail |
| 14:51.12 | brlcad | code_walker: OMG |
| 14:51.18 | code_walker | i got |
| 14:51.22 | brlcad | did you run "/msg ibot ask" |
| 14:51.26 | code_walker | disconnected |
| 14:51.40 | brlcad | I mentioned ibot ask before you disconnected |
| 14:51.46 | code_walker | ya |
| 14:51.50 | brlcad | and did you? |
| 14:51.51 | code_walker | i didn't |
| 14:51.59 | brlcad | why not? |
| 14:52.10 | code_walker | doing it right now |
| 14:52.23 | code_walker | my net is troubling me today |
| 14:52.29 | code_walker | thats y |
| 14:52.45 | code_walker | getting dc very frequently |
| 14:52.49 | brlcad | there is a protocol of behavior for IRC that helps make group chat pleasant for all and scalable |
| 14:53.42 | *** topic/#brlcad by code_walker -> /msg ibot ask |
| 14:53.45 | brlcad | you were able to chat for a solid 20 minutes before you got disconnected, so I don't buy that |
| 14:54.27 | brlcad | code_walker: that was not right |
| 14:54.32 | *** topic/#brlcad by brlcad -> BRL-CAD || http://brlcad.org || logs: http://ibot.rikers.org/%23brlcad/ || GSoC 2013! http://brlcad.org/wiki/Google_Summer_of_Code |
| 14:54.33 | code_walker | by troubling i mean bad |
| 14:54.38 | code_walker | net speed |
| 14:54.44 | code_walker | very low |
| 14:54.56 | brlcad | what does net speed have to do with typing "/msg ibot ask" |
| 14:54.58 | code_walker | i can't do my all the stuffs properly |
| 14:55.16 | code_walker | ya sorry |
| 14:55.19 | code_walker | for that |
| 14:56.07 | brlcad | code_walker: participating in open source is CENTERED around effective communication |
| 14:56.17 | brlcad | it's a dominant factor in proposal selection |
| 14:56.35 | *** join/#brlcad aks001 (uid10889@gateway/web/irccloud.com/x-wvqykhyrtiynsjlw) |
| 14:56.55 | brlcad | right now, I think it's definitely an area you should work on |
| 14:57.06 | brlcad | learning and mistakes are expected, okay |
| 14:57.07 | code_walker | k i will |
| 14:57.58 | brlcad | having to stop like this to explain this basic point is not okay |
| 14:58.35 | brlcad | if you don't understand something, you should ask specific questions and get clarification |
| 14:58.59 | brlcad | we ARE here to help you (and others) |
| 14:59.43 | brlcad | did you run the ibot ask thing yet? |
| 14:59.56 | code_walker | ya i did |
| 14:59.58 | chalk | hey brlcad what is ibot?? |
| 15:03.19 | brlcad | code_walker: what is the point that is trying to convey? |
| 15:03.33 | brlcad | ibot: ibot |
| 15:03.33 | ibot | hmm... ibot is not a help system |
| 15:03.39 | brlcad | heh |
| 15:03.42 | code_walker | about project? |
| 15:04.30 | brlcad | ibot: infobot |
| 15:04.30 | ibot | well, infobot is me, http://infobot.svn.sourceforge.net/svnroot/infobot/ // The original infobot is no more, it has been replaced by the latest version of blootbot, accompanied by a rename back to infobot // apt/ibot/infobot/purl is now an infobot run by TimRiker |
| 15:04.31 | code_walker | i just wanted to ask more about cpd's implementation |
| 15:05.04 | brlcad | code_walker: what was the point of running "/msg ibot ask"? |
| 15:05.06 | code_walker | so that i should work more to improve my current code |
| 15:05.38 | code_walker | to ask what is meant to ask |
| 15:06.11 | brlcad | code_walker: we can talk about that after you understand this rather critical point of communication |
| 15:06.17 | brlcad | no, that was not the point |
| 15:06.46 | brlcad | the you made a mistake earlier, and that link explains the mistake |
| 15:08.42 | code_walker | rather it is about asking your question and getting a good answer for it |
| 15:08.51 | code_walker | its not important |
| 15:08.54 | code_walker | that |
| 15:09.12 | brlcad | still not it |
| 15:09.30 | brlcad | "10:51 < code_walker> brlcad:u there?" <-- this should not happen |
| 15:10.00 | code_walker | i understood that before too |
| 15:10.14 | code_walker | and i will not repeat that again |
| 15:10.16 | brlcad | that's why communication is so important |
| 15:10.24 | brlcad | you never once indicated that you've understood that point |
| 15:10.37 | code_walker | actually,i saw others doing that |
| 15:10.38 | brlcad | I can't read your mind, only what you wright |
| 15:10.48 | brlcad | s/wright/write/ |
| 15:10.53 | brlcad | can't wright write ;) |
| 15:11.04 | code_walker | my bad |
| 15:11.36 | ncsaba | brlcad: but then there's not much difference to a mail-based forum, if the interactivity is just occasional - then I for example would prefer to just write a mail |
| 15:11.49 | ncsaba | if I come to IRC, I really want interactive and direct discussion :) |
| 15:11.54 | code_walker | im sorry,the main aspect of coding "don't copy" |
| 15:12.05 | brlcad | code_walker: you were called out because you did it twice, the second time AFTER I gave you the information that explained to not do that |
| 15:12.33 | brlcad | open source has little tolerance for not reading information... :) |
| 15:12.36 | brlcad | anyways, moving on |
| 15:12.39 | brlcad | cpd |
| 15:12.54 | code_walker | ya |
| 15:12.57 | brlcad | can you explain to me what bearing that has on code reduction? |
| 15:13.54 | code_walker | actually,i had made a small version of cpd in c but its applications are limited right now |
| 15:14.01 | code_walker | im expanding it |
| 15:14.07 | ncsaba | brlcad: I can't find the volume II on the web - and the locally installed version has no appendix, just as you said |
| 15:14.08 | code_walker | to be more accurate |
| 15:14.11 | ncsaba | all I found is htis : http://brlcad.org/wiki/BRL-CAD_Primitives |
| 15:14.23 | code_walker | i wanted to more about its implementation |
| 15:14.29 | code_walker | know* |
| 15:15.48 | brlcad | code_walker: but you're not answering my question -- you're explaining that you put a fuel injector in a car and I'm asking you where we're driving |
| 15:16.15 | brlcad | what does cpd have to do with code reduction? can you explain it to me? |
| 15:16.22 | code_walker | ya |
| 15:16.43 | *** join/#brlcad jasleen (~chatzilla@117.253.233.214) |
| 15:16.58 | code_walker | im making a cpd to detect simple duplicated code segments in c |
| 15:17.09 | brlcad | start with what a cpd is |
| 15:17.12 | code_walker | which are exact copy |
| 15:17.19 | brlcad | i'm sure there are others here which don't know that acronym |
| 15:17.22 | code_walker | cpd is a copy paste |
| 15:17.25 | code_walker | detector |
| 15:17.34 | code_walker | which finds the |
| 15:17.42 | brlcad | and how does your copy-paste detector different from simian? |
| 15:17.43 | code_walker | duplicated code segments |
| 15:17.48 | code_walker | ya |
| 15:17.51 | code_walker | thats what |
| 15:17.55 | code_walker | is my point |
| 15:18.04 | code_walker | actually thats what i |
| 15:18.43 | brlcad | please think your thought through and type it |
| 15:18.44 | code_walker | thats why i wanted to |
| 15:18.45 | brlcad | a running |
| 15:18.47 | brlcad | dialog |
| 15:18.49 | code_walker | know more about |
| 15:18.50 | brlcad | of what |
| 15:18.52 | brlcad | you're thinking |
| 15:18.55 | brlcad | gets very annoying |
| 15:18.56 | brlcad | quickly |
| 15:19.02 | code_walker | cpd |
| 15:19.03 | brlcad | :) |
| 15:19.46 | code_walker | im wanted to make it exclusively for c/c++ |
| 15:20.15 | code_walker | should i code that same cpd as that of simian |
| 15:20.29 | code_walker | but i don't want to do that |
| 15:21.12 | brlcad | I'm not sure I understand your concern, frankly |
| 15:21.24 | brlcad | are you actually proposing to implement a simian alternative for GSoC? |
| 15:21.31 | brlcad | or reduce BRL-CAD code? |
| 15:21.38 | brlcad | there's certainly not time to do both |
| 15:21.39 | code_walker | no |
| 15:22.09 | code_walker | thats why im asking from you to know more about its implementation |
| 15:22.45 | brlcad | but what's the relevance? |
| 15:23.28 | brlcad | if you're proposing to work on your CPD for GSoC, I'd have to ask what the value is for BRL-CAD |
| 15:23.36 | code_walker | to improve over the existing versions of cpd |
| 15:23.44 | brlcad | if you're not proposing to work on it for GSoC, then I have to ask why we're talking about it ;) |
| 15:24.11 | code_walker | i will work it for gsoc only |
| 15:24.16 | brlcad | what's the relevance for GSoC |
| 15:24.19 | brlcad | okay |
| 15:24.38 | code_walker | k i will research more about it then |
| 15:24.39 | brlcad | so then my first point -- what is the value for BRL-CAD? |
| 15:24.52 | code_walker | highest |
| 15:25.01 | brlcad | you're not understanding |
| 15:25.08 | code_walker | im concerned more about brlcad |
| 15:25.21 | brlcad | but your project has nothing to do with BRL-CAD |
| 15:25.40 | code_walker | ya but i will do it under brlcad rather |
| 15:25.41 | brlcad | you might as well be proposing to implement a new web browser |
| 15:25.58 | brlcad | because all the devs use web browsers and yours is going to be better |
| 15:26.05 | brlcad | and it'll help |
| 15:26.20 | brlcad | maybe it would, but it has nothing to do with BRL-CAD directly from what you've described |
| 15:27.03 | code_walker | thats my point i want to introduce a better tool in the market |
| 15:27.07 | brlcad | GSoC doesn't exist to get pet projects funded |
| 15:27.15 | code_walker | for code reduction in c/c++ |
| 15:27.18 | brlcad | it exists to help foster open source communities |
| 15:27.34 | brlcad | your project only fosters your project |
| 15:28.02 | brlcad | more power to you and I think it's great that you have a project in mind and that you're making it open source |
| 15:28.11 | brlcad | it just doesn't make it a viable open source project |
| 15:28.17 | code_walker | ya |
| 15:28.21 | brlcad | maybe if you write it all up into a proposal, it'll make more sense |
| 15:28.30 | code_walker | ya |
| 15:28.38 | code_walker | i have done that already |
| 15:28.46 | brlcad | but at this point, I'd have to wonder how you're even different from the half-dozen other code reduction tools already available |
| 15:29.15 | code_walker | ya they are better in anysense |
| 15:29.27 | brlcad | if you wanted to use your tool/method on BRL-CAD for GSoC, that'd be a completely different matter |
| 15:29.41 | code_walker | especially after they wer based on statemen to statement |
| 15:29.45 | code_walker | implementation |
| 15:30.03 | brlcad | so you're saying yours sucks and you should be given a gsoc slot to make it better? :) |
| 15:30.10 | ncsaba | brlcad: I found finally the web version of the "Introduction_to_MGED.pdf", which must be the volume II you were talking about -> will work on getting that in docbook, but not in a tutorial - I find this deserves to live in a separate and properly named reference file |
| 15:30.11 | brlcad | not much of a salesman ;) |
| 15:30.45 | brlcad | ncsaba: yes, the mged intro is vol II (sorry, long history with that document) |
| 15:30.53 | brlcad | all of the lessons in vol II are in docbook already |
| 15:31.01 | code_walker | i just want to get more ahead in this project to know more about it |
| 15:31.10 | ncsaba | yes, but not the appendix with the primitives |
| 15:31.13 | code_walker | and |
| 15:31.15 | brlcad | ncsaba: the appendicies at the end weren't converted to docbook, right |
| 15:31.22 | chalk | ibot ask |
| 15:31.22 | ibot | Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. |
| 15:31.25 | brlcad | the thinking was that they'd be auto-generated |
| 15:31.29 | code_walker | certainly make it better than before |
| 15:31.54 | brlcad | code_walker: "i just want to get more ahead in this project to know more about it" |
| 15:32.11 | ncsaba | brlcad: aha, that certainly makes sense - but then it should go into annotations in each primitive ? |
| 15:32.21 | brlcad | 1) you don't need gsoc for that and 2) it's a very self-centered perspective, which isn't the open source way |
| 15:32.54 | brlcad | ncsaba: something like that -- default annotations |
| 15:33.01 | code_walker | but this is the right time to be a part of gsoc |
| 15:33.16 | brlcad | for example the screenshots that are already in that appendix are just captures of the wireframe when you go into primitive edit mode |
| 15:33.24 | brlcad | with an underlayed ray trace |
| 15:33.29 | code_walker | because my final year of graduation is going to start now |
| 15:33.34 | brlcad | code_walker: this is the right time |
| 15:33.37 | brlcad | that is not the right project |
| 15:33.48 | code_walker | its the most crucial time |
| 15:33.52 | brlcad | gsoc does not exist to get pet projects funded |
| 15:33.59 | ncsaba | brlcad: then I would do that as a primitive function which generates the right picture |
| 15:34.04 | brlcad | it's the most crucially wrong project |
| 15:34.45 | ncsaba | wire-frame + annotations, then raytrace with underlay |
| 15:34.58 | code_walker | but i can do more in this project |
| 15:35.00 | brlcad | code_walker: your goal should not -- CANNOT -- be just the development of your tool |
| 15:35.03 | code_walker | as |
| 15:35.12 | ncsaba | and then a script which runs that for each primitive it finds |
| 15:35.16 | code_walker | i have done a similar project in my college oo |
| 15:35.39 | brlcad | it should DIRECTLY foster open source in some way (NOW) .. if you proposed developing your tool and applying it to an open source project like BRL-CAD with a reasonable development timeline and clear benefits, that'd be another matter |
| 15:35.56 | code_walker | i want to make a tool which i started to make in my college but didn/t finshed it |
| 15:36.06 | brlcad | but that's not what you're proposing, and I doubt there'd be enough time to do both |
| 15:36.27 | brlcad | code_walker: good for you, so make your tool |
| 15:36.37 | brlcad | I have a dozen projects I made in college but didn't finish too |
| 15:36.54 | code_walker | ya |
| 15:37.03 | brlcad | and not one of them is relevant to GSoC |
| 15:37.14 | brlcad | gotta run, talk more later |
| 15:37.17 | ncsaba | brlcad: do you have some pointer to some existing annotations processing tool brlcad (potentially) already uses ? |
| 15:37.20 | code_walker | but when i saw that on brlcad's idealist |
| 15:37.53 | code_walker | i thought thats a good chance to increase my research on it |
| 15:39.09 | code_walker | is that thing bad on my part? |
| 15:39.51 | *** join/#brlcad Iordanis (Iordanis@host214-207.cvd.fit.edu) |
| 15:42.52 | ncsaba | brlcad: I really would like to work on improving the documentation - but I also don't want to duplicate already done work, and I surely need pointers to current practices, so whatever I do is aligned with the way brlcad is doing it - and currently this GSOC thingy takes all your time, so I guess I'll be back later once things cool down here |
| 15:44.03 | ncsaba | or will switch to mailing - IRC is simply frustrating for me currently |
| 16:15.24 | *** join/#brlcad code_walker (~Shubham@120.59.146.195) |
| 16:20.55 | brlcad | code_walker: it's not a bad thing, but it can't be the ONLY thing .. you have to tie your project to tangible direct immediate goals that benefit BRL-CAD, and NOT focus (at all) on your cpd project objectives |
| 16:21.39 | brlcad | it can be a means to an end, but not the goal (for gsoc) |
| 16:22.52 | code_walker | and im doing it for the benefit of brlcad only |
| 16:23.22 | code_walker | sir can i ask you a question |
| 16:23.23 | code_walker | ? |
| 16:23.59 | brlcad | it doesn't have to only benefit brl-cad, but you do have to identify brl-cad benefits and make them part of your plan, explain how they're worthwhile, defend your approach, etc |
| 16:24.39 | brlcad | code_walker: *sigh* |
| 16:24.42 | brlcad | read this: 12:23 < code_walker> sir can i ask you a question |
| 16:24.44 | brlcad | and read this: |
| 16:24.45 | brlcad | ~ask |
| 16:24.45 | ibot | Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. |
| 16:25.17 | brlcad | really, it seems like you're just not trying very hard at all |
| 16:26.08 | code_walker | what is in calling a mentor "sir" |
| 16:26.15 | code_walker | wrong* |
| 16:27.23 | brlcad | what does the second sentence say? if you don't comprehend what you read, we cannot work with you |
| 16:27.50 | *** join/#brlcad rays2pix (~deepak@14.139.226.34) |
| 16:45.23 | code_walker | brlcad:i have used occurrence table concept to built a cpd |
| 16:45.36 | code_walker | i there a better way? |
| 16:45.39 | *** join/#brlcad vladbogo (~vlad@86.121.100.121) |
| 16:46.57 | brlcad | there usually is a better way to do just about anything |
| 17:58.11 | *** join/#brlcad Iordanis (Iordanis@host214-207.cvd.fit.edu) |
| 19:18.13 | *** join/#brlcad vladbogo (~vlad@86.121.103.57) |
| 19:43.49 | *** join/#brlcad starseeker (~starseeke@66-118-151-70.static.sagonet.net) |
| 20:32.04 | maths22 | brlcad: on the GSOC homepage, they should have the new logo (I think) |
| 20:34.03 | brlcad | maths22: afaik, that is the new logo... |
| 20:34.23 | brlcad | at least I pulled it from the gsoc site |
| 21:11.10 | rays2pix | BRLCAD_ADDEXEC(pix-rgba pix-rgba.c ";libfb;libbu;${PNG_LIBRARY};${BABL_LIBRARY}") - have added this line in CMakeList to create a new executable |
| 21:12.36 | rays2pix | it link.txt for corresponding file doesnt have the "-lbabl" updated in it |
| 21:14.24 | rays2pix | To link with a 3rd party library-libbabl i set include dir and added library dependency as above. Am I missing a step here.? |
| 21:20.53 | zero_level | rays2pix: i dont know but without any pre chats its hard to understand what u have asked ? |
| 21:21.49 | rays2pix | zero_level: plainly how to add library dependency in CMake build system |
| 21:22.29 | brlcad | rays2pix: where is BABL_LIBRARY set? |
| 21:22.51 | brlcad | (you can't just make up new ones, they are tested for and set) |
| 21:23.27 | rays2pix | brlcad: I have set that within utils CMakeLists.txt |
| 21:23.41 | rays2pix | set(BABL_LIB /usr/local/lib/libbabl-0.1.so) |
| 21:23.54 | brlcad | BABL_LIB != BABL_LIBRARY |
| 21:24.11 | brlcad | and that's still not the right way to specify a library |
| 21:24.59 | brlcad | it'll ultimately need to turn into -lbabl |
| 21:25.25 | brlcad | though if you're going to introduce a new dependency, you should have a detailed justification (cost benefit analysis) |
| 21:25.46 | brlcad | and a plan :) |
| 21:26.18 | rays2pix | just tried it for a quick testing. . doing some tests for it. |
| 21:27.41 | rays2pix | brlcad:where should I refer for adding a library in the right way? |
| 21:34.33 | maths22 | brlcad: there are two logos: the little black and blue one and the 3d one. |
| 21:34.54 | maths22 | shouldn't the black and blue one be a stylization of the 3d one designed for a thumbnail? |
| 21:37.48 | brlcad | rays2pix: any of the other existing libraries, our cmake examples, the cmake docs, .. |
| 21:38.25 | brlcad | maths22: you're welcome to update it, but I just didn't want to use the exact same one we used last year except for the name changed |
| 21:38.31 | brlcad | black and white worked out nicely |
| 21:38.52 | brlcad | i don't see a "3d" one |
| 21:43.13 | *** join/#brlcad zero_level (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 22:03.16 | *** join/#brlcad zero_level_ (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 22:03.44 | *** part/#brlcad zero_level_ (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 22:03.52 | *** join/#brlcad zero_level_ (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 22:04.07 | *** part/#brlcad zero_level_ (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 22:04.20 | *** join/#brlcad zero_level_ (0e8bf3a2@gateway/web/freenode/ip.14.139.243.162) |
| 22:21.43 | maths22 | I will take a look later |
| 22:25.58 | Notify | 03BRL-CAD Wiki:Sean * 5154 /wiki/Google_Summer_of_Code/Project_Ideas: |
| 22:26.00 | Notify | 03BRL-CAD Wiki:Sean * 5155 /wiki/Google_Summer_of_Code/Project_Ideas: |
| 22:26.02 | Notify | 03BRL-CAD Wiki:Sean * 5156 /wiki/STEP_Coverage_Tes: Created page with "STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but the..." |
| 22:26.04 | Notify | 03BRL-CAD Wiki:Sean * 5157 /wiki/STEP_Incremental_Loading: Created page with "STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but it ..." |
| 22:26.06 | Notify | 03BRL-CAD Wiki:Sean * 5158 /wiki/STEP_Multiple_Protocol_Parsing: Created page with "STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but cur..." |
| 22:26.08 | Notify | 03BRL-CAD Wiki:Sean * 5159 /wiki/STEP_AP_242_Parser: Created page with "STEP is the current standard for exchange of CAD data between different software packages. BRL-CAD makes use of the STEPcode project to implement its step-g importer, but it ..." |
| 22:26.10 | Notify | 03BRL-CAD Wiki:Sean * 5160 /wiki/Google_Summer_of_Code/Project_Ideas: |
| 22:26.20 | Notify | 03BRL-CAD Wiki:Priyankapk * 0 /wiki/User:Priyankapk: |
| 22:26.23 | Notify | 03BRL-CAD Wiki:Starseeker * 5161 /wiki/STEP_Libraries: Tweak STEP Libraries project |
| 22:26.24 | Notify | 03BRL-CAD Wiki:Phoenix * 5162 /wiki/User:Phoenix/GSoc2013/Proposal: /* Things I have done this year */ |
| 22:26.26 | Notify | 03BRL-CAD Wiki:IIIzzzaaakkk * 5163 /wiki/User:Izak: /* DEVELOPMENT SCHEDULE AND TIMELINE */ |
| 22:26.28 | Notify | 03BRL-CAD Wiki:IIIzzzaaakkk * 5164 /wiki/User:Izak: /* PROJECT SUMMARY */ |
| 22:26.31 | Notify | 03BRL-CAD Wiki:41.92.211.105 * 5165 /wiki/User:Izak: /* LINKS TO CODE OR ALGORITHMS WHICH YOU INTEND TO USE */ |
| 22:26.32 | Notify | 03BRL-CAD Wiki:41.92.211.105 * 5166 /wiki/User:Izak: /* LINKS TO CODE OR ALGORITHMS WHICH YOU INTEND TO USE */ |
| 22:26.34 | Notify | 03BRL-CAD Wiki:14.139.243.162 * 5167 /wiki/User:Level_zero/proposal: Addition of working schedule |
| 22:26.46 | Notify | 03BRL-CAD:brlcad * 55274 brlcad/trunk/include/bu.h: no longer searches share/brlcad/VERSION by default, searches DATA_DIR and share |
| 22:27.44 | Notify | 03BRL-CAD:phoenixyjll * 55275 brlcad/trunk/src/librt/tests/test_ssi.cpp: Use the sketch primitive to represent 2D intersection curves. |
| 22:28.02 | Notify | 03BRL-CAD:carlmoore * 55276 brlcad/trunk/src/libfb/fb_generic.c: fix type (need long unsigned) |
| 22:28.04 | Notify | 03BRL-CAD:carlmoore * 55277 brlcad/trunk/src/libfb/fb_paged_io.c: fix type (needed long unsigned) |
| 22:28.06 | Notify | 03BRL-CAD:carlmoore * 55278 (brlcad/trunk/src/liboptical/material.c brlcad/trunk/src/liboptical/photonmap.c): fix types |
| 22:28.22 | Notify | 03BRL-CAD:carlmoore * 55279 brlcad/trunk/src/sig/ddisp.c: shift the isatty test further up (no point in processing the options if this fails), and add '< inputfile' to the usage |
| 22:28.26 | Notify | 03BRL-CAD:bob1961 * 55280 brlcad/trunk/src/librt/primitives/metaball/metaball.c: Minor tweak to rt_metaball_get. |
| 22:28.29 | Notify | 03BRL-CAD:carlmoore * 55281 brlcad/trunk/src/sig/dfft.c: additions to the Usage |
| 22:28.34 | Notify | 03BRL-CAD:carlmoore * 55282 brlcad/trunk/src/sig/dfft.c: use spaces, not tabs |
| 22:28.37 | Notify | 03BRL-CAD:carlmoore * 55283 brlcad/trunk/src/conv/dbupgrade.c: shift duplicate code from if-else, remove unneeded 'if (reverse )' from an 'else', and shift logic around to avoid unnecessary creation of output file |
| 22:28.39 | Notify | 03BRL-CAD:carlmoore * 55284 brlcad/trunk/src/conv/nmg/asc-nmg.c: try to implement no-argument situation |
| 22:28.53 | Notify | 03BRL-CAD:brlcad * 55285 brlcad/trunk/src/proc-db/csgbrep.cpp: it's evident that it's still running, just say the output file. |
| 22:28.56 | Notify | 03BRL-CAD:brlcad * 55286 brlcad/trunk/src/librt/primitives/nmg/nmg_rt_segs.c: use %p to print pointers |
| 22:28.58 | Notify | 03BRL-CAD:carlmoore * 55287 brlcad/trunk/src/liboptical/sh_prj.c: fix type warnings |
| 22:29.01 | Notify | 03BRL-CAD:carlmoore * 55288 brlcad/trunk/src/sig/dfft.c: oops, was looking for both stdin & stdout w/r to isatty; move back to earlier location (removing a set of braces), and also fix usage of -? |
| 22:29.03 | Notify | 03BRL-CAD:brlcad * 55289 brlcad/trunk/NEWS: richard improved/fixed the gqa command in r52355 so that regions with zero hits which are in the overlap list are not reported as having zero hits. |
| 23:06.46 | zero_level | ``Erik: is there a way to remove already submitted patch |
| 23:34.30 | *** join/#brlcad jbschw (4355ee54@gateway/web/freenode/ip.67.85.238.84) |
| 23:35.03 | jbschw | #j yellowfin |
| 23:35.06 | jbschw | whoops |