What Does Kernel Collaboration Mean?

[Cary OConnor]

This option is one of the most powerful options in IronCAD that is normally transparent to a user in everyday usage. Due to IronCAD’s unique dual kernels, additional capabilities beyond translation have been developed. Kernel Collaboration in models allows each kernel to work together to get the desired result of a customer. For Example: A user working on a model in the ACIS kernel attempts to create a blend on the model. If the blend is to complex for ACIS to handle, traditional systems with ACIS kernels only would fail to create the blend. However in IronCAD, the boundary representation body will be given to the other kernel (Parasolid) and the blend will be attempted there. If the blend succeeds, the final boundary representation will be given back to ACIS. So the user will have an ACIS model with the desired blend shape. All of this happens behind the scene transparent to the user. So the user thinks that the blend shape just works and they are still working in the same kernel they started with. In reality, the ACIS traditional systems would have failed and users would have to work around the issue. The Kernel Collaboration works between both kernels in the same manner (Failure in Parasolid goes to ACIS and back visa versa). Kernel Collaboration currently is limited to certain operations (more can be developed in the future) like blend, chamfer, direct face modifications, shell, and Booleans.

 

How's Kernel Collaboration different from just switching Kernels? -- There is a big difference. Just using different kernels doesn't mean that you can build the model. Certain features may only build in one kernel or the other. For example, non-manifold conditions cannot be solved in Parasolid where ACIS can handle it (This is just an example, there are other cases where ACIS can't and Parasolid can). The real issue is that sometimes it is important to build a model in a certain kernel to give to vendors or downstream suppliers (without the issues with data translation). Since Kernel Collaboration always keeps the boundary representation in the kernel you specified, you can export in that kernels format and give the result to suppliers (When you export you only send a final boundary representation of the solid data. Since Kernel Collaboration keeps the final representation in the working kernel, there is no issue with opening a ACIS/Parasolid exported file in a different system even though it needed both kernels to build it in IronCAD). -- That's a head twister!

 

How do you enable Kernel Collaboration? -- Kernel Collaboration is on by default. The option is under the Tools/Options pull-down menu on the General Tab (Bottom-right of the dialog).

 

What are some noticeable side effects? -- If your model needs to take advantage of the Kernel Collaboration, you will notice slower regeneration times since the date needs to interact with both kernels (A price well worth the wait to get features generated don't you think).

 

How can you determine if your model is taking advantage of the Kernel Collaboration? -- Uncheck the Kernel Collaboration option in the Tools/Option/General Dialog. Select your model and select "Regenerate" under the Shape pull-down menu. If features in you model start failing, then you model was using Kernel Collaboration to build those features. Once you turn the Kernel Collaboration back on, regenerate the model again and the feature should complete. In reality, you never really need to know. That's why we make it transparent to the user. Just build your model, don't worry that IronCAD is doing double duty to help you out. One other note....IronCAD is the only CAD system that has this capability!

 

For an example: -- Load the attached scene file. Turn off the Kernel Collaboration. Regenerate the model. Notice the blend feature fails. Switch Kernels and notice that it cannot due to the non-manifold condition. Turn Kernel Collaboration back on. Regenerate. Blend completed in Parasolid and the Non-manifold handled by ACIS. What power .

 

 

 

KernelCollab.ics