RE: [certi-dev] CERTI - Move to HLA 1516

[Gotthard, Petr]

Hi again,

First of all, it's great that you consider CERTI as a possible
replacement for your RTI. I'll try to answer some questions from my
perspective.

> I was wondering if you could give your estimate on how much work it
> would actually be to implement the 1516 interface for CERTI.

The HLA 1516 functions that are similar to HLA 1.3 and implemented in
CERTI RTIA/RTIG can be implemented quite easily. I believe most of your
"high priority" services are in this category.

I'd guess ~1 month (full time) for an experienced C++ developer that
knows the basic IEEE 1516 behaviour but doesn't have experiences with
CERTI. (It's a great HLA training exercise.)

> Is this something that someone with only basic HLA knowledge would
> be able to do?

The "easy services" yes. The "not so easy services" like name
reservation would require some help from the experienced CERTI
developers, but they're always very helpful. :-)

> Furthermore, are they also other parties interested in working on this
task?

I'm interested, but currently able to perform only minor tasks.

> Also, how would you broadly envision such an implementation?

This was discussed here:
http://lists.nongnu.org/archive/html/certi-devel/2008-10/msg00009.html

There should be both 1.3 and 1516 interfaces. As there is a socket
interface between libRTI and RTIA, the 1516 specific modifications can
be limited to the libRTI1516 only. Ideally, the RTIA/RTIG will be able
to serve both 1.3 and 1516 without recompilation.


I hope some of the CERTI experts will add their comments later.

Best Regards,
Petr

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Ijperen, Jeroen van
Sent: Friday, January 08, 2010 1:13 PM
To: CERTI development discussions
Subject: [certi-dev] CERTI - Move to HLA 1516

>From what I have understood from our developers we need (high priority):
- Basic Federation functionality (create, join, destroy)
- Object management (create, discover, update, etc)
  * We noticed that the Name reservation mechanism had not been
introduced in 1.3, which we will need.
- Interactions
- Time regulation - advance time steps, no look ahead, no time contraint

Things we do not need (low/no priority):
- Federation save/restore
- Regions
- Ownership management

Obviously we would prefer a full implementation, but that depends on how
complete the current version is. :)

Kind regards,

Jeroen van IJperen
TASK24

-----Oorspronkelijk bericht-----
Van: address@hidden
[mailto:address@hidden
Namens Gotthard, Petr
Verzonden: vrijdag 8 januari 2010 12:52
Aan: CERTI development discussions
Onderwerp: RE: [certi-dev] RE: CERTI - HLA1516.1 C++ headers - Differs
from IEEEspecification

Hi Jeroen,
I have one question before the discussion starts ;-) Do you need a full
IEEE 1516 implementation, or just a subset of HLA services? (HLA
services are listed e.g. at
http://www.nongnu.org/certi/PyHLA/manual/node8.html.) What HLA services
are for you "high priority" and what could be "low or no priority" (if
any)?

Regards
Petr

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Ijperen, Jeroen van
Sent: Friday, January 08, 2010 12:07 PM
To: address@hidden
Subject: [certi-dev] RE: CERTI - HLA1516.1 C++ headers - Differs from
IEEEspecification

Hello,

Our company does development on a simulator currently working with the
IEEE 1516 interface, but we are considering switching to CERTI as our
RTI. Obviously, we would like to keep our HLA 1516 interface intact. Our
first step right now is making an estimate how much work would actually
be required for this. 

Eric informed me that CERTI currently only has the SISO HLA 1516
headers, but no actual implementation. He also indicated that any help
with implementing this was most welcome. 

I was wondering if you could give your estimate on how much work it
would actually be to implement the 1516 interface for CERTI. Is this
something that someone with only basic HLA knowledge would be able to
do? Furthermore, are they also other parties interested in working on
this task?

Also, how would you broadly envision such an implementation? I assume
you want to remain compatible with the 1.3 version of HLA. Would you
move the current implementated functionality to the 1516 sources,
letting the 1.3 version use a subset of 1516 functions?

Kind regards,

Jeroen van IJperen
TASK24

-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel


-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel


-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel