User:Anuragmurty

About me

• Name: Anurag Murty
• E-mail address: anuragmurty@gmail.com
• IRC username: anuragmurty

I am an MTech student of Computational Science at IISc Bangalore

About The GSoc Project

Brief Description of my project on the GSoC page

Development Log

1.First task is compilation of BRL-CAD

BRL-CAD succesfully built from source

2.Learning to use the Software / Explore the code

Have Completed the tutorial on BRL-CAD available on the site(Basically mged commands and USING the software)

3 Raytracing Commands related to my project work

having learnt to use rt , rtweight from a USERs perspective, going through the respective codes and understanding the modules now

4. Wrote a small patch for bitv.c in src/libbu.Waiting for feedback:)

5. Going through the gqa program as I have been asked to learn to use and understand it too

6. patch for ctype.c also submitted. waiting for reviews. had some problem with the previous patch too. Turned out that it wasnt in the unified diff format as required.

[ PS: Some problem with IRC. Unable to join the brlcad channel. Should be fixed in a while hopefully.]

7. 21st to 23rd -- done understanding code for rtexample.c. discussed with mentor(d_rossberg) about how to extend rt_shootray for getting the voxels. parameters to be used : size of voxels,rays to be shot per voxel, minimum volume to be considered as threshold for considering. have started with implementation of a first , very basic program to get voxels.(one ray per voxel for now, simple shapes also).

8. first patch accepted.. test_bitv.c!! second patch i submitted test_ctype has to be modified according to hacking guidelines...

9. working on rt_shootray for 3 views, which will be submitted today, but in a little while.

10. Written rtexample_3view.c that uses the midpoints of the faces of the bounding rectangular parallelopiped to shoot three rays in three perpendicular directions and gives data of the partitions encountered(the hit code is exactly taken from rtexample.c). the same is being submitted as a patch.

11. Indentation changes made to test_ctype. Also, a typo related patch was submitted yesterday. Working on shooting a grid of rays at object to be raytraced(towards the negative x-axis). Should be able to submit that as a patch tonight or maybe tomorrow.

12. i will be going through codes for libanalyze and libged commands as directed by brlcad. Also, I will not be available on IRC tonight(as i will be travelling)

13. 30/5/2012 : Got commit access today. Lot of time spent trying to rebuild brlcad. Some problems with MGED dependencies. Everything deleted and rebuilt. Working fine now. Though still unable to locate what went wrong. Presently completing the code for shooting a grid of rays and putting it in src/conv so I can make my first commit.

14. 31/5/2012 made my first commit. A simple, safe g-voxel program which did not actually get voxels. Just shot a grid of rays.

15. 1/6/2012 i wrote a simple voxelize program. right now, it just prints if the voxel in the path of each ray is in or out. Right now, the parameters are hardcoded(parameters like threshold a voxel is to be filled to consider as in, size of voxel in each dimension , others). I think i also will have to consider some other method apart from only using the bounding box as in some cases(example, a 3-D plus sign) too many rays are shot which might be a waste of time.

16. 5/6/2012 have shifted the evaluation of voxel to main and writing code for multiple rays per voxel. though multiple rays through a voxel is buggy(minor, most probably). Will commit as soon that is done

17. 6/6/2012 there was problem with voxel calculations when hitDistOut was on a voxel boundary. Also, I was computing the ending ray data slightly wrong. this was also rectified.

multiple rays are being shot now-- through same point because i have to ask my mentor whether those rays have to be random and how to proceed on volume calculations after that.

I have two variables for now- ray num threshold, threshold- depending on how the IN/OUT of a voxel has to be determined. one of these two will be discarded.