Hip2Norm: an object-oriented cross-platform program for 3D analysis of hip joint morphology using 2D pelvic radiographs

We developed an object-oriented cross-platform program to perform three-dimensional (3D) analysis of hip joint morphology using two-dimensional (2D) anteroposterior (AP) pelvic radiographs. Landmarks extracted from 2D AP pelvic radiographs and optionally an additional lateral pelvic X-ray were combined with a cone beam projection model to reconstruct 3D hip joints. Since individual pelvic orientation can vary considerably, a method for standardizing pelvic orientation was implemented to determine the absolute tilt/rotation. The evaluation of anatomically morphologic differences was achieved by reconstructing the projected acetabular rim and the measured hip parameters as if obtained in a standardized neutral orientation. The program had been successfully used to interactively objectify acetabular version in hips with femoro-acetabular impingement or developmental dysplasia. Hip(2)Norm is written in object-oriented programming language C++ using cross-platform software Qt (TrollTech, Oslo, Norway) for graphical user interface (GUI) and is transportable to any platform.

INVESTIGATING THE ROLE OF THE CONTACT LINE IN HETEROGENEOUS NUCLEATION WITH HIGH SPEED IMAGING

While nucleation of solids in supercooled liquids is ubiquitous [15, 65, 66], surface crystallization, the tendency for freezing to begin preferentially at the liquid-gas interface, has remained puzzling [74, 18, 68, 69, 51, 64, 72, 16]. Here we employ high-speed imaging of supercooled water drops to study the phenomenon of heterogeneous surface crystallization. Our geometry avoids the "point-like contact" of prior experiments by providing a simple, symmetric contact line (triple line defined by the substrate-liquid-air interface) for a drop resting on a homogeneous silicon substrate. We examine three possible mechanisms that might explain these laboratory observations: (i) Line Tension at the triple line, (ii) Thermal Gradients within the droplets and (iii) Surface Texture. In our first study we record nearly perfect spatial uniformity in the immersed (liquid-substrate) region and, thereby, no preference for nucleation at the triple line. In our second study, no influence of thermal gradients on the preference for freezing at the triple line was observed. Motivated by the conjectured importance of line tension (τ) [1, 66] for heterogeneous nucleation, we also searched for evidence of a transition to surface crystallization at length scales on the order of δ ∼ τ/σ, where σ is the surface tension [14]; poorly constrained τ [49] leads to δ ranging from microns to nanometers. We demonstrate that nano-scale texture causes a shift in the nucleation to the three-phase contact line, while micro-scale texture does not. The possibility of a critical length scale has implications for the effectiveness of nucleation catalysts, including formation of ice in atmospheric clouds [7].

Practical Object-Oriented Back-in-Time Debugging

Back-in-time debuggers are extremely useful tools for identifying the causes of bugs, as they allow us to inspect the past states of objects no longer present in the current execution stack. Unfortunately the "omniscient" approaches that try to remember all previous states are impractical because they either consume too much space or they are far too slow. Several approaches rely on heuristics to limit these penalties, but they ultimately end up throwing out too much relevant information. In this paper we propose a practical approach to back-in-time debugging that attempts to keep track of only the relevant past data. In contrast to other approaches, we keep object history information together with the regular objects in the application memory. Although seemingly counter-intuitive, this approach has the effect that past data that is not reachable from current application objects (and hence, no longer relevant) is automatically garbage collected. In this paper we describe the technical details of our approach, and we present benchmarks that demonstrate that memory consumption stays within practical bounds. Furthermore since our approach works at the virtual machine level, the performance penalty is significantly better than with other approaches.

Context-Oriented Programming

Context-dependent behavior is becoming increasingly important for a wide range of application domains, from pervasive computing to common business applications. Unfortunately, mainstream programming languages do not provide mechanisms that enable software entities to adapt their behavior dynamically to the current execution context. This leads developers to adopt convoluted designs to achieve the necessary runtime flexibility. We propose a new programming technique called Context-oriented Programming (COP) which addresses this problem. COP treats context explicitly, and provides mechanisms to dynamically adapt behavior in reaction to changes in context, even after system deployment at runtime. In this paper we lay the foundations of COP, show how dynamic layer activation enables multi-dimensional dispatch, illustrate the application of COP by examples in several language extensions, and demonstrate that COP is largely independent of other commitments to programming style.