Part and parcel with model-based engineering is model translation. Because the model is now the specification, accurate translation from one system to another becomes essential. But even if a model is accurately read, the intent of the model has to also be properly interpreted. Key to proper model interpretation is healing — the process of modifying model data so that it conforms to the rules of the target system, while adhering to the intent of the source.
In a past blog, The Impact of Model-Based Definition (MBD) on 3D Modeling and Manufacturing, we discussed the growing role of MBD. To recap: although 3D modeling has been the standard in design for decades, many manufacturers still rely heavily on 2D drawings when communicating with suppliers. MBD enables the next step in CAD evolution where the 3D model becomes the means of communicating manufacturing data and specifications (product and manufacturing information or PMI).
Analysis applications often use solid models generated by CAD systems as their input; for example, the structural analysis of an engineering model. The user of the system applies a set of loads and boundary conditions to the model, and then the software performs its analysis and supplies a set of deformations or stresses in the material, allowing an engineer to look at the results and decide whether the design fits its purpose.
The beginning of the year is a time for planning, both in our personal lives, as well as professional. It is no different here at Spatial. We are excited to begin sharing our plans and goals for the future with our customers. One of our focus areas this year is model-based definition, or MBD.
Spatial's 3D InterOp requires that all translations be done on the same thread that creates the SPAISystemInitGuard. This complicates programs that may wish to create separate threads for a translation. This is often done in GUI applications that require the main thread to listen for events and handle all translation logic in a separate thread that will not impact the interactivity of the main thread.
Recently I was asked by a customer how to render a 3D visualization model translated from a CAD file by Graphical 3D InterOp (see ref 1 below.) The customer is using HOOPS so the quick answer was to use our bridge libraries which connect our products together and sure enough there is a 3D InterOp/HOOPs bridge for precisely this purpose. However I thought that I would really like to know how the data gets passed between the different components, especially as I had a small test application I had used a while ago and I never got the dis
Helpful Qt Tools for 3D Software Development Kits
When software developers opt for tools that are cross platform, they often turn to Qt. Qt is arguably the most popular toolkit for making applications that can run on Windows, Mac or Linux with little additional effort. Spatial’s 3D software development kits can be paired with Qt to produce enterprise quality applications that are platform agnostic.
The R24 release of 3D InterOp is now available for download. Although they are available online, not everyone pours over the 3D InterOp Release Notes for R24 like we might hope. What follows is a shorter summary of what’s new in 3D InterOp Suite R24. The description of what’s new falls into three areas; new products, functional enhancements, and platform changes.
Try to buy a single-core laptop today and you’ll have a difficult time even finding one. The leading computer manufacturers offer at least dual-core for base models of their economy lines, even for laptops. Let that sink in. Our days of single core machines, even laptops, are over. Many of the leading mobile products are also at least dual-core with higher end products having even more cores.
One of the common phrases that comes up a lot here, especially with respect to interface discussions, is the phrase "What vs. How." I usually forget to think about what this really means, but last night I got a vivid illustration of the concept.