Libresource
Home
Search
My Page
Guest -
Login
Navigation
location:
>
Artenum OpenSource
>
Keridwen
>
Documentation
>
Keridwen Modules
>
Keridwen Core
>
External Technologies Wrapping
Contextual Menu
Presentation
Documentation
Application Cases
FAQ
Keridwen Modules
Key Features
Licenses
Publications
Innovative Technical Solutions
Integrated Modelling Environment (IME)
Service Oriented Approach (SOA)
Software Life Cycle
Supported Platforms
The OSGi standard
Community
Authors and credits
Become a member
Forum
Project Status
Upgrade account
Commercial Offer
Services & Support
Development
API
Examples
Roadmap
Edit this menu
Resource Menu
Properties
Security
More actions...
----
Node Information
Create new resource
Delete this resource
Move this resource
Unbind this resource
----
List children
Go to parent
----
search from here
External Technologies Wrapping
__Tailored and business components in a large set of languages, including native ones like C/C++ or Fortran, can be integrated through techniques fully validated with a low extra-cost in memory and CPU. Various approaches can be used depending on the needs of tailored software to be integrated.__ [/projects/keridwen/html/wrapping_png|{image:/projects/keridwen/html/wrapping_png|height=300|align=left}] \\ 1.1 Java/JNI Wrapping: The Java/JNI wrapping technique provided a very deep integration of low-level components like libraries. This technique is already used for several large libraries, like VTK or Gmsh in C/C++ or SIG codes or simulation kernels in Fortran. At runtime, the OSGi-based design of Keridwen facilitates the identification and the deployment of the relevant binary package for each targeted platform. This approach also allows an efficient integration of optimised sub-routines, based on a native implementation, into complex simulation loops gathering various languages. Various application cases have confirmed the relevance of such approach in terms of memory and CPU time. [/projects/keridwen/html/SystemCall_png|{image:/projects/keridwen/html/SystemCall_png|height=350|align=right}] {html}
{html} 1.1 System calls: In alternative, runnable standalone applications can also be integrated through system commands calls. The implemented Keridwen modules take in charge the detection and the adaptation of the call to each platform, the transmission of input and output files and the management of the corresponding job (PID, errors codes...). This approach is especially relevant for pre-existing runnable software where a non-intrusive integration scheme is needed for technical or historical reasons. This technique offers to the scientific expert the possibility to keep the full control of the evolution of his simulation software, having on the other hand the possibilities offered by the integration in a Keridwen-based IME. This approach has been successfully used in several application cases (SPIS, SIG tools...). 1 Services and Supports On demand, Artenum can provide the expertise of its experts to integrate your software component into Keridwen based IME. Feel free to [http://www.artenum.com/EN/contact.php|__contact us__] for further information.
Last edited by Arnaud Trouche at May 4, 2017 5:21 PM -
Edit content
-
View source