Category archives: Snaking
Discussions of programming, particularly of programming Python
Changing strings to tuples has far-reaching effects (PySNMP optimisation might constitute a fork?)
Written by
on
in
Snaking.
Today I spent almost exclusively on getting the tuple-based OID code worked through PySNMP, TwistedSNMP and Cinemon. The changes were far more extensive than I was hoping. They are mostly integrated, but it's going to take a few more hours to track down all of the string-assumptive code.
Anyway, the OID class now seems fairly ...!-->!-->
Patches suck time (Greedy little performance enhancing vermin that they are...)
Written by
on
in
Snaking.
So, other than spending... I don't even want to think about how much time... working with D'Arcy this morning, I worked on getting the patch for PySNMP put together (SourceForge's CVS being back online). That was going to be a 20 minute task before I started the real work on fixing the OID object mechanism... ...
Presentation paper work... (Only about 1.5 months left)
Written by
on
in
Snaking.
D'Arcy decided to go to PyCon, so we're going to drive down together. Did some rewriting for the PyCon paper, mostly just expanding the section describing the rationalisation of various object-interactions during the 2.2 type-class unification work. That made the section longer, but didn't actually move me further through the outline. I need ...
If the box isn't up the program won't run (I'm a software guy... not even an OS guy, really...)
Written by
on
in
Snaking.
After my visit to grams (she won 3:2), came home and got an email pointing out that both Cinemon instances were down. The boxes are still off the network, so there's nothing I can do about it at the moment, but it's somewhat frustrating to have the project sitting offline for this long.
Since I ...!-->!-->
I still seem to be working on it (Even though I thought I was stopping after that last post...)
Written by
on
in
Snaking.
Got distracted from going to bed by the desire to have 4-point coplanar contours properly tessellate. Wound up having to write a new utility function to determine whether a cloud of points is coplanar.
Not a particularly involved function, just note that for all sets > 3 points, you create a vector from A to B, ...!-->!-->
How quickly one forgets (Basic algebra and geometry...)
Written by
on
in
Snaking.
Spent the rest of the evening working on tessellation code, but never did get around to fixing the problem with the Jelle-project tessellation. Instead I realised that I had no test cases for a "combining" tessellation. To understand what that is, consider this shape...
When we render this shape, we want it to look something ...
!-->!-->
Clockwise versus counter-clockwise geometry strikes again (Shadow code is sensitive to the problem as well...)
Written by
on
in
Snaking.
Sat down to figure out why the shadow-rendering context in OpenGLContext has such problems with the tessellations of Jelle's project. First thing I wound up doing was backing out earlier changes to try to get the VBO extension working, then had to back-port the Python 2.3 PyInt_AsUnsignedLongMask function so that the typemaps for long integers ...
OpenGL just seems so messy (Providing "natural" semantics for a low-level API...)
Written by
on
in
Snaking.
Was just reading through the GLEWpy source-code for the ARB vertex-buffer-object extension. It's basically about the same level as the auto-generated SWIG, or ctypes interfaces. It should work fine, but it doesn't feel natural. Brian's interface looks a lot more natural to me, but it's also a lot more code.
I just have this nagging ...!-->!-->
It would be so much easier if I had hardware with these extensions... (Oh well, gives me an excuse ;) )
Written by
on
in
Snaking.
Spent a few hours reviewing and trying to integrate Brian's Vertex Buffer Object extension patch. It was made against the 2.0.1 release (my fault, I've been slow getting to it), so there was a bit of migration work to do. Problem is, the migration to SWIG 1.2.23 seems to have changed how the new vertex-pointer ...
No way to generate patches (SourceForge's anonymous CVS for "p" projects is down...)
Written by
on
in
Snaking.
Not a huge amount of PySNMP speedup for the day, wound up doing quite a lot of whole-application profiling, but hours of that only represents a few runs in total (it takes a long time to load 100MB of profile data in wxProfile). Discovered that, in the demo code, almost 33% of running time is ...