Latest revision |
Your text |
Line 62: |
Line 62: |
| <b><u>8/6/2012</u></b> Made lots of changes to previous code of g-voxel.c. Also, now running "./g-voxel [.g file] [region-name]" in bin/ of the build directory outputs a file "voxels.txt" that gives a frame by frame representation of the desired region. | | <b><u>8/6/2012</u></b> Made lots of changes to previous code of g-voxel.c. Also, now running "./g-voxel [.g file] [region-name]" in bin/ of the build directory outputs a file "voxels.txt" that gives a frame by frame representation of the desired region. |
| | | |
− | <b><u>12/6/2012</u></b> g-voxel.c modified so it allows multiple rays per voxel. for input raysPerVoxel what I do is shoot a uniform raysPerVoxel*raysPerVoxel rays, so probably this variable name is a misnomer. again the output is voxels.txt which gives the output text file frame by frame. | + | <b><u>12/6/2012</u></b> g-voxel.c modified so it allows multiple rays per voxel. |
− | | |
− | | |
− | <b><u>14/6/2012</u></b> same as last time, floats replaced by fastf_t. some unnecessary statements variables and statements removed(mistakes pointed out by d_rossberg)..
| |
− | a major error was allocating space for ALL voxels. so now as soon as a raytrace is done, the results are printed out to file voxels.txt. thus at any point space for only numVoxels[0] is assigned, major savings.
| |
− | | |
− | I need to change the structure for rayInfo so it includes region names also.
| |
− | this means using pp->pt_regionp->reg_name from struct partition but i am presently getting bugs in the result. so working on this so that I canc hange the output format so it lists data region wise.
| |
− | | |
− | | |
− | <b><u>18/6/2012 -20/6/2012</u></b>
| |
− | structure for rayInfo modified.
| |
− | rayInfo is structure for storing info each time a raytrace is called. It contains a linked list of regions inside each voxel.
| |
− | voxels.txt now has data in the format:
| |
− | | |
− | 1/0 (coordinates of voxel) (region-name) (fill fraction)
| |
− | | |
− | where 1/0 tell you if the voxel is in or not(according to threshold).
| |
− | | |
− | 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.
| |