certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] Matlab Toolbox


From: Eric Noulard
Subject: Re: [certi-dev] Matlab Toolbox
Date: Tue, 11 Oct 2011 10:57:21 +0200

2011/10/11 Christian Stenzel <address@hidden>:

> The second task will be a 1516 transition.
> Hard to say how much time is needed for taht task.
> Obviously we have the current toolbox as template.
> In 1516, there are some new methods, methods with different signatures
> and new HLA types. That's why we need new conversion method for Matlab
> to HLA1516 types and vice versa.
> In my opinion the concept of Matlab/HLA bindings is proven through the
> current toolbox. So the task is "only a programming task", meaning that
> we do not have to develop new concepts but have to map the 1516-API.
> Therefore we can introduce a new file rti1516.cpp do the programming
> stuff as usual.
> The m-file folder could be seperated in a hla13 and a hla1516 part.
>
> My problem here is that I have nearly no time at time. This will change
> hopefully in the next year. So if you really need a free 1516-Tbx as
> fast as possible you're on your own. I can only support you with some
> templates and hints if you need some. If you wait we can do the task
> together.

Just a small comment on that 1516 part.
CERTI architecture makes it possible mix in the same simulation
HLA1.3 and IEEE1516 federate.

In fact CERTI internals almost does not care about the standard, this
is essentially
an federate API thing. That said since in HLA1.3 there was no user "encoding"
recommandation the only "possibly" incompatible thing is the encoding part.

To be clear, using CERTI a HLA13 federate may perfectly send and UAV
that will be received as RAV by a 1516 federate but bot federate
should use the same user encoding.

Again from CERTI point of view the 1516 encoding type are defined in
the libHLA part
which does not depend on any other CERTI library part (it can even be used with
any C++ application).

So to summarize, you should already be able to use Matlab HLA13 federate
with a C++ IEEE-1516 federate as soons as they use the same user encoding
for user provided data (attribute values of objects or parameter
values of interaction).



-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]