https://github.com/kitware/remus

Remus is a remote mesh/model service framework.
https://github.com/kitware/remus

Last synced: 2 months ago
JSON representation

Remus is a remote mesh/model service framework.

• Host: GitHub
• URL: https://github.com/kitware/remus
• Owner: Kitware
• License: other
• Created: 2012-10-17T18:38:41.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2019-11-07T16:11:32.000Z (about 5 years ago)
• Last Synced: 2023-10-20T21:00:59.557Z (about 1 year ago)
• Language: C++
• Homepage:
• Size: 1.95 MB
• Stars: 9
• Watchers: 5
• Forks: 9
• Open Issues: 19
• Metadata Files:
  • Readme: Readme.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
## Remus: A Remote Mesh/Model Service Framework

[![Imgur](http://i.imgur.com/8zsK3vl.png?2)](http://open.cdash.org/index.php?project=Remus)

Remus' goal is to make meshing 2- and 3-dimensional meshes easy.

We accomplish this by insulating your program from the instabilities and licenses

of the current generation of meshers by providing the ability to mesh

on remote machines using a basic client, server, and worker design.

## Building Remus

To build Remus you must have

+ A modern C++ compiler (gcc, clang, or VS),

+ [CMake](http://cmake.org) 2.8.11 or newer, and

+ [Boost](http://boost.org) 1.50.0 or newer, and

+ [ZMQ](http://zeromq.org/) 2.X or newer.

Remus provides a superbuild branch that can be used to easily build

Boost and ZMQ dependencies.

## Remus Layout ##

Remus is split into five distinct groups: Common, Proto,

Client, Server, and Worker.

Common is a collection of helper classes and is usable by any of the other groups.

It contains such useful features as MD5 computation, signal catching, process

launching and monitoring, mesh type registration, and a conditional storage class.

Proto contains all of the common classes that are used during serialization.

If an object is being sent from the client to the server, it is in the

proto group.

Client, Server, and Worker are rather self explanatory: they are the interfaces

to the client, server and worker components of Remus.

## Documentation ##

* [Client Documentation][]

* [Worker Documentation][]

* [Server Documentation][]

* [Constructing a Remus Worker File][]

* [Registering a New Mesh Type][]

[Client Documentation]: remus/client/Readme.md

[Worker Documentation]: remus/worker/Readme.md

[Server Documentation]: remus/server/Readme.md

[Constructing a Remus Worker File]: remus/worker/Readme.md#constructing-a-remus-worker-file

[Registering a New Mesh Type]: remus/client/Readme.md#register-a-new-mesh-type