I took a look at old and new RTI behavior as well as the impact on RPR federates and federations. Here is a first analysis of what the default switches should be. The difficult thing is to asses what the overall effect of various switch values have for a RPR FOM 2d17 federation using existing federates, possible in a mixed-mode HLA 1.3/2000/2010 federation. What can federates expect from each other and from other federates?

Feel free to comment and improve!

Bjorn M




Default Switches suggestion for RPR FOM 2.0 and later

Auto Provide
In order for one federate to benefit from this, other federates need to implement the Provide callback. This is not required by the GRIM for RPR FOM 2.0d17. This should be required in the future, i.e. RPR FOM 3.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value On

Convey Region Designator Set
No standard Dimensions are described in the GRIM for RPR FOM 2d17 and only samples (D1 are given in the FOM. So there is no standard design for DDM. Conveying DDM info if a federate subscribes without DDM is mainly used for debugging anyway.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value Off

Convey Producing Federate
Not available in HLA 1.3 or 1516-2000. Cannot be required by federates in a mixed HLA 1.3/2000/2010 federation.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value On

Attribute Scope Advisory
This was initially disabled in HLA 1.3 so should be off in the RPR FOM.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value Off

Attribute Relevancy Advisory
This was initially disabled in HLA 1.3 so should be off in the RPR FOM.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value Off

Object Class Relevance Advisory
This was initially enabled in HLA 1.3 so should be on in the RPR FOM.

RPR FOM 2.0: Propose value On
RPR FOM 3.0: Propose value On

Interaction Relevancy Advisory
This was initially enabled in HLA 1.3 so should be on in the RPR FOM.

RPR FOM 2.0: Propose value On
RPR FOM 3.0: Propose value On

Service Reporting
Used mainly for debugging.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value Off

Exception reporting
Used mainly for debugging.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value Off

Delay subscription evaluation
New feature in HLA Evolved, not required/available in HLA 1.3 federations. This feature is also mainly used by analytical/time managed federations.

RPR FOM 2.0: Propose value Off
RPR FOM 3.0: Propose value Off

Automatic resign action
If a federate crashes or is lost in some way, how should the RTI resign on behalf of it? Suggest a maximum clean up.

RPR FOM 2.0: Propose value CancelThenDeleteThenDivest
RPR FOM 3.0: Propose value CancelThenDeleteThenDivest

###


To unsubscribe from the SAC-PDG-RPR list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-RPR