Omegalib 4.1 Released!

-
An multiview osg+vtk omegalib 4.1 application has been used to analyse sonar data collected during the NASA ENDURANCE exploration of Lake Bonney, Antarctica.
This version adds experimental support for the Oculus Rift head mounted display through a custom omegalib module, and introduces major improvements to mission control client-to-client communication support.

Major Changes

omega
  • death switch timeout automatically kills stuck slave instances
  • getButtonSetting python function
  • event dispatching enable / disable functions
  • tile show/hide commands
  • improved bounding box calculation
  • SceneNode.setChildrenVisible
  • Python event callbacks process events as modules with NORMAL priority level, instead of processing them after all modules (i.e. below Lowest priority). This allows python event callbacks to mark events as processed before they are passed to lower-priority modules.
  • python MissionControlClient class. Other improvements to mission control support
  • removed -mc client command line option. Mission control clients can be controlled directly through scripting now.
  • Fixed Node.lookAt
  • Cleaned up GPU resource allocation
  • Extended the SceneNode python API with rlative transform methods and other utility methods.
  • 4.1.1 Fix: incorrect C++ to python data layout for Quaternion
omegaToolkit
  • Wand manipulator quick commands for enabling move/rotate/scale
  • improved Button widget customization
omegaOsg
  • FIX fixed depth test issue on some linux installs
cyclops
  • FIX scene tree removal / addition of subtrees
omegaVtk
  • FIX actor bounding box and draw settings.
A precompiled windows binary can be found here: https://github.com/febret/omegalib-windows/archive/v4.1.1.zip

Comments

Post a Comment

Popular posts from this blog

Parallel Gaussian Elimination Using MPI

-
Image
In this project, we had to implement a parallel solver for linear equation systems, using a technique known as Gaussian elimination (GE). As with many other algorithms for solving linear equation systems, GE is performed on the matrix representation of the system, Ax = b, where A is the coefficient matrix and b is the vector of known values. GE works by applying a set of elementary row operations (swapping rows, multiplying a row by a non-zero number, adding a multiple of one row to another) in order to turn the coefficient matrix into upper triangular form. The algorithm has been implemented in C, using the Message Passing Interface (MPI) API. The parallel GE program measured execution times for its four main components: data distribution, Forward Elimination , Pivot row identification, Back substitution. Read the full report here
Read more

Parallel Beam Tracing and Visualization of 200 Million Sonar Points

-
Image
For the final project in the UIC Spring 2013 Parallel Processing Class, I worked with a classmate to optimize our current implementation of a sonar beam tracer used for  The NASA ENDURANCE Project . The beam tracer is used to process the raw data collected by the ENDURANCE AUV in Lake Bonney, Antarctica, and correct sound beam paths using information about the water chemistry. The data is clustered and noise filtered to generate a final 3D Point cloud that can be visualized in our CAVE2 system. The ENDURANCE Sonar data in CAVE2. Photo(c) Lance Long. A lot of corrections and adjustments need to be applied to this data before the final results are acceptable. Some of the corrections derive from the sound speed estimation through the water column, AUV navigation corrections, water level changes and noise filtering thresholds. All this parameters influence the final result, and ideally researchers can tweak them and see the result of their actions in real time. Given the size of
Read more

Flickering 2D transform elements in Chrome: a simple fix

-
This quick post is to point out a fix to an issue I had to deal with a few weeks ago and was caused by a Chrome update. Components with absolute positioning and a 2D CSS transform started flickering when placed inside a scrollable component. A brief search online revealed several people with similar problems, but the suggested fixes were all very different. I tested several of them (including obvious changes to the z order) before finding the one that actually did the trick. What eventually worked for me was adding an empty 3D transform to the same elements with 2D transforms: transform:translate3d(0,0,0); I guess the reason why this works is that it forces elements to be drawn via a different rendering / compositing path than standard 2D elements.
Read more