adios2-serial-bin

ADIOS2 Adaptable IO system for simulations - binary tools (serial)

The Adaptable IO System (ADIOS) provides a simple, flexible way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how you wish to process them this run, the routines in the host code (either Fortran or C) can transparently change how they process the data.

libtntnet13t64

Tntnet libraries

Tntnet has a template-language called ecpp similar to PHP, JSP or Mason, where you can embed c++ code inside a HTML page to generate active content. The ecpp files are precompiled to C++ classes called components and compiled and linked into a shared library. This process is done at compiletime. The web server Tntnet needs only the compiled component library.

libvisp-me3.5

visual servoing platform me tracking library

This package contains the ViSP (Visual Servoing Platform) moving edges (me) tracking runtime library.

libadios2-mpi-auxiliary-2

ADIOS2 Adaptable IO system for simulations - auxiliary libraries (MPI)

The Adaptable IO System (ADIOS) provides a simple, flexible way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how you wish to process them this run, the routines in the host code (either Fortran or C) can transparently change how they process the data.

libtopcom0t64

Triangulations Of Point Configs and Oriented Matroids (library)

TOPCOM is a collection of clients to compute Triangulations Of Point Configurations and Oriented Matroids, resp.

libadios2-mpi-c++11-2

ADIOS2 Adaptable IO system for simulations - C++11 binding libraries (MPI)

The Adaptable IO System (ADIOS) provides a simple, flexible way for scientists to describe the data in their code that may need to be written, read, or processed outside of the running simulation. By providing an external to the code XML file describing the various elements, their types, and how you wish to process them this run, the routines in the host code (either Fortran or C) can transparently change how they process the data.