Using Caesar's Multi-Language Support

Multi-Language and Shared Objects

ZMQ Messaging Interface

Caesar.jl has a ZMQ messaging interface (interested can see code here here) that allows users to interact with the solver code base in a variety of ways. The messaging interface is not meant to replace static .so library file compilation–see below–-but rather a more versatile and flexible development strategy.

The current known interface implementations to Caesar.jl are:

Starting the Caesar ZMQ server

Start the Caesar.ZmqCaesar server in a Julia session with a few process cores:

julia -p 4

Then run the following commands, and note these steps have also been scripted here:

#import the required modules
using Caesar, Caesar.ZmqCaesar

# create empty factor graph and config objects
fg = Caesar.initfg()
config = Dict{String, String}()
zmqConfig = ZmqServer(fg, config, true, "tcp://*:5555");

# Start the server over ZMQ

# give the server a minute to start up ...

The current tests are a good place to see some examples of the current interfacing functions.

TODO: expand the ZMQ documentation

Static, Shared Object .so Compilation

The Julia language is a (Just-In-Time / Precompiled) static and strongly typed language. Modules are already naturally compiled to static objects and can also be compiled to more common .so files. See this AOT vs JIT compiling blog post for a deeper discussion.

The future planning for the Caesar.jl framework and the mm-iSAM inference algorithm plans to use the package: so that linkable .so files or even full executables can be compiled. Please add your comments to this issue discussion.

Alternative Methods

Interfacing from languages like Python may also be achieved using PyCall.jl although little work has been done in the Caesar.jl framework to explore this path. Julia is itself interactive/dynamic and has plenty of line-by-line and Integrated Development Environment support – consider trying Julia for your application.