Editing User:Anuragmurty

From BRL-CAD

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 82: Line 82:
  
 
also to store names in a local variable of main(), i have used bu_vls_strgrab function.
 
also to store names in a local variable of main(), i have used bu_vls_strgrab function.
 
<b><u>21/6/2012</u></b> corrected a bug i found while doing some tests on g-voxel.c with some .g file inputs
 
 
<b><u>26/6/2012</u></b> first step towards moving the voxelize work into a library. made a function that is called from main in g-voxel.c and takes in as input userparameters for a voxelize and outputs a file with the necessary voxel information. used a structure for input parameters and additional inputs might be added later.
 
TODO: implement a callback function for writing result into the file.
 
 
 
<b><u>28/6/2012</u></b> implemented callback function for printing results of g-voxel.c.
 
moving it to libanalyze is next todo.
 
slight problem being faced : i am unable to commit using svn commit.
 
svn: Commit failed (details follow):
 
svn: OPTIONS of 'https://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk/src/conv': Could not create SSL connection through proxy server: Could not authenticate to proxy server: rejected Digest challenge (https://brlcad.svn.sourceforge.net)
 
trying to fix for a long time now
 
 
<b><u>29/6/2012</u></b> callback committed, some more modifications
 
 
<b><u>2/7/2012</u></b> library- libanalyze changed for accommodating voxelize functions, in voxels.c in libanalyze , all the functions are defined.
 
also, g-voxel.c modified and uses functions from libanalyze
 
 
<b><u>2/7/2012</u></b> modified call back and parameters to voxelize
 
<b><u>4/7/2012 and 5/7/2012</u></b> comparison against threshold not made in voxelize now. sent as callBackData sent as input to callback function and decision. same changes made to g-voxel etc also
 
 
<b><u>8/7/2012</u></b> went through ged-facetize which is going to be template for ged_voxelize.
 
 
<b><u>11,12/7/2012</u></b> wrote a voxelize.c program for libged. This has function ged_voxelize(struct ged*, int argc, char *argv[]). However, There is segementation fault when I run the program.
 
 
<b>------------------------------------------------------------------------------
 
 
<b><u> POST-MIDTERM EVALUATION WORK
 
note: this has been updated very late,towards the end of the GSoC duration
 
</u>
 
segmentation fault from the program voxelize.c was removed
 
the location of rt_prep_parallel was changed from callinf function to voxelize
 
 
15 july
 
changed a very roundabout way to bu_vls_strcpy
 
 
16th july -analyze.h unused functions for voxelize removed
 
  callback functions removed from analyze.h and included here
 
  rt_prep function added into voxelize function of voxels.c, callback removed
 
 
19-july ged.h changed to have ged_voxelize function
 
static callback functions were added to voxelize.c and g-voxel.c
 
 
 
MGED hook to voxelize created
 
help.tcl scripts changed to enable autocomplete
 
tclcad_obl.c scripts changed to enable autocomplete
 
callback function called create boxes made to actually make the voxels for a given input primitive/collection
 
some code cleanup was done in g-voxel.c
 
create_boxes function is called evrywhere instead of printFunction like intial case.
 
 
till now, all the parameters of a voxelize were hard coded, now (with Daniel's help), it takes command line arguments plus all the voxels are in a user-specified region.
 
 
code cleanup, specially for respecting alphabetical ordering.
 
voxel sizes multiplied by local2base, since the user provides the numbers in his own choice of units.
 

Please note that all contributions to BRL-CAD may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BRL-CAD:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)