hey @Cezar looking forward to coding? :)
I was just going through tasks just yesterday and was thinking about your project
pretty excited to see what you can accomplish
yup :D i'm planning to go through the raytracer more thoroughly during the community bonding period, and then to start trying things asap
by the way, any other administrative things i must do?
and since you were thinking about the project, do you happen to have any pointers or suggestions? :D
by the way, any other administrative things i must do?
yes, there are -- get a public log set up somewhere, think about what work schedule you want to do (which students should discuss with their mentor but you are a special case), read through the docs if you haven't yet, turn your proposal into a project plan (with your mentors), and finally introduce yourself and your project publicly
and since you were thinking about the project, do you happen to have any pointers or suggestions? :D
if i recall, you ran a profile so making sure you have testable component will be essential to know you're making progress without breaking things -- read up on TDD if you haven't before
a good starting point will be libbu's pointer table API (bu_ptbl) -- I suggest you start by writing a unit test that uses the API (examples in src/libbu/tests) and once you understand what it's for, look where it's used and make a test for that code (e.g., a test for rt_boolweave or rt_boolfinal) -- then you'll be set up to do something about it
@Sean i got something going at this address. let me know what i need to add or change
are there any examples of a work schedule (haven't been able to find any on the wiki)?
That’s looking good Cezar. You say you checked the wiki but were you looking at past year pages? There are dozens of examples.
i submitted a patch with tests for bu_ptbl
i also updated the dev log; regarding the work schedule, this is what i found by searching, but it looks like a development schedule :-?
that's one, but not necessarily the best example -- go to http://brlcad.org/wiki/Google_Summer_of_Code and click on each year to see all the plans for nearly everyone
i was looking at those at first, but that seems to be what i put in my dev log
is it missing anything?
Last updated: Jan 09 2025 at 00:46 UTC