Our big group bug ended up being a flop. Glenn spent a week or so to stitch together 3 images to test the bug and our solution (<3Gb, =3Gb, >3Gb). The bug stated that images over 3Gb wouldn't render properly, but we were having issues loading MUCH smaller images, even less than 1Gb. Having only 1.5 weeks left of class, we don't have the time to futher problem solve this issue.
Since our group bug seemed like a dead end, our group considered working on my 2nd bug as the new big group bug, since it ended up being more complicated than I initially thought. However, when trying to test for the bug existence, the patches and test files included in the bug report were alone proving to be troublesome.
To further complicate things, this bug requires design clarification before we can imlement a patch, and would require many back-and-forth emailing with the VTK developers. We would have to discuss implementation specifications before even starting to fix the bug. Based on past experience communicating with the developers, this conversation alone could take weeks, especially since we are not very established in the VTK community.
This bug would probably have been doable if we had initially chosen it as our group bug, but now it doesn't seem like there is not enough time.
That being the case, we are planning on bringing our bug fixing to an end and instead start to focus on our group presentation (using prezi). At least we were all able to experience the entire OpenSource code commit process from our first individual bugs. Today, we are planning on meeting to start our designing/creating our presentation.
No comments:
Post a Comment