Re: [certi-dev] IEEE1516 includes

[Jean-Philippe Lebel]

While developing the HlaToolbox for Matlab, I had to go through all the 
differences between every implementation of the HLA Standard.

Hla 1.3 is pretty straight forward and most of the manufacturer uses the 
DLC compliant API. Mak, Pitch, Virtc and Portico. Certi is missing some 
region related code to be HLA 1.3 DLC Compliant (last time I checked).

Regarding IEEE1516, the story is a quite different:
Pitch DOESN'T use the DLC API although the differences are small (the 
namespace is not the same and some function use non-const parameters). I 
know they have an internal DLC compliant API but they don't plan on 
releasing it.)
Mak is IEEE1516 DLC compliant
Portico: work in progress but will support IEEE516DLC
Virtual Technologies still works on their 1516 binding but will be DLC 
Compliant.

They **all** use the same folder hierarchy as Mak (include\RTI\*.h)

I hope this helps.

JPL

Gotthard, Petr wrote:
> Besides the two you mentioned I have also this one.
> ftp:\\ftp.mak.com\out\Final_DLC_APIs.zip
>
> It's a package of C++/Java API for HLA1.3/HLA1516. Although stored on
> MAK server, it's the standard DLC API described by the SISO 2004
> standard. The MAK RTI uses the same files (plus some more that are
> implementation-specifc).
>
> The package contains also DLC API for HLA1.3, but MAK RTI doesn't use
> it. They use the HLA-NG like CERTI does. This is how include of MAK RTI
> looks like:
>
> include\baseTypes.hh
> include\federateAmbServices.hh
> include\fedtime.hh
> include\makRti.h
> include\NullFederateAmbassador.hh
> include\RTI.hh
> include\RTIambServices.hh
> include\RTItypes.hh
> include\RTI\Enums.h
> include\RTI\Exception.h
> include\RTI\FederateAmbassador.h
> include\RTI\Handle.h
> include\RTI\LogicalTime.h
> include\RTI\LogicalTimeFactory.h
> include\RTI\logicalTimeFactoryImpl.h
> include\RTI\logicalTimeFactoryImplFloat.h
> include\RTI\logicalTimeFactoryImplInteger.h
> include\RTI\logicalTimeImpl.h
> include\RTI\logicalTimeImplFloat.h
> include\RTI\logicalTimeImplInteger.h
> include\RTI\LogicalTimeInterval.h
> include\RTI\logicalTimeIntervalImpl.h
> include\RTI\logicalTimeIntervalImplFloat.h
> include\RTI\logicalTimeIntervalImplInteger.h
> include\RTI\NullFederateAmbassador.h
> include\RTI\RangeBounds.h
> include\RTI\RTI1516.h
> include\RTI\RTIambassador.h
> include\RTI\RTIambassadorFactory.h
> include\RTI\SpecificConfig.h
> include\RTI\Typedefs.h
> include\RTI\VariableLengthData.h
>
>
> Regards,
> Petr
>
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Eric Noulard
> Sent: Tuesday, September 30, 2008 4:38 PM
> To: CERTI development discussions
> Subject: Re: [certi-dev] IEEE1516 includes
>
> 2008/9/30 Gotthard, Petr <address@hidden>:
> > Eric,
> > the IEEE1516 includes that are now included in CVS are not inline with
>
> > SISO DLC API and thus incompatible e.g. with MAK RTI. (Perhaps the 
> > biggest difference is that all DLC API includes are in an "RTI"
> > subdirectory instead of having the "RTI_" prefix.) Could CERTI use the
>
> > official DLC API headers?
>
> Which should follow the best suitable standard.
> I did extract those headers from IEEE-1516-2000 document.
>
> > Or is there any reason for having the includes as they're now?
>
> None beside the fact that I did not have the DLC document and files.
> Do you have link to an up to date DLC spec?
>
> Mine is this one:
> http://www.sisostds.org/index.php?tg=fileman&idx=get&id=5&gr=Y&path=SISO
> +Products%2FSISO+Standards&file=SIS-STD-004.1-2004.zip
> or
> http://discussions.sisostds.org/default.asp?action=9&read=40014&fid=111
>
> I should have polled before updating those files...
> Now before creating an include/RTI subdir may be those of you which are
> using other RTIs (mak, pitch, portico ...) may give us feedback.
>
> I would personnally vote for the most up 2 date SISO DLC spec.
>
>
> --
> Erk