Re: [certi-dev] Subscribe Object Class Attributes

[Eric Noulard]

2015-05-11 11:12 GMT+02:00 Daniel Nowrozi <address@hidden>:

Thanks for reply,

My problem is about republish last object attributes values for subscribers that are connected to RTI after publisher. in the standard said if one specific switch is on subscribers ask for provideAttributeValues, but in CERTI is not implemented.

What makes you think that "requestAttributeValueUpdate" service is not implemented?

UnlessIm' wrong, the service should be working in 1.3, 1515-2000 and 1516-2010 API.

(In 1.3 the service was called "requestObjectAttributeValueUpdate")

"Working" means that the federate service "provideAttributeValueUpdate" will be called on the subscriber side.

That said it is the responsibility of the federate receiving the "provideAttributeValueUpdate" to call

the "UpdateAttributeValue" service in return such that late subscriber get what they requested through provideAttributeValues.

The part which is NOT implemented in CERTI is the MOM switch "HLAautoProvide".

In fact MOM is not implemented at all.

 

how CERTI handle this situation, how recently connected subscribers can get last attribute values from publishers?

They call "requestAttributeValueUpdate" service

the publisher receive "provideAttributeValueUpdate" callback

the publisher shall call "UpdateAttributeValue" service  --> this is the user responsibility to implement this.

 

For all "unimplemented" feature in CERTI patches are welcome :-)

thanks a lot.

On Mon, May 11, 2015 at 1:08 PM, Eric Noulard <address@hidden> wrote:

2015-05-09 10:27 GMT+02:00 Daniel Nowrozi <address@hidden>:

Dear Eric!

I have a problem in understanding of subscribeObjectClassAttributes method. the standard 1516.2 said :
"for all object instances discovered as a result of this service invocation, shall be
provided to the joined federate from the RTI (via the Reflect Attribute Values service).
The set of class attributes provided shall be a subset of the available attributes of the specified object class."

and in the end its says.
"If the optional passive subscription indicator argument is not present or indicates that this is an active subscription, the invocation of this service may cause the Start Registration For Object Class service to be invoked at one or more other joined federates."

so if i run the HLA module that publishes instance objects, then run the HLA modules that subscribe to these instance attributes, how CERTI update these values in subscribers:

1. using auto provide switch for emitting provideAttributeValues

2. using requestAttributeValues in discoverObject

3. or else

The basic communication mean between subscriber and publisher is:

publisher call the UAV RTI service = UpdateAttributeValue each time the object they publish changed value

subscriber receive RAV RTI Callback = ReflectAttributeValue for each UAV call on the publisher side.

discoverObject callback is called on subscribefr side when new object are registred on publisher side

RAVU=requestAttributeValuesUpdate is a way for a subscriber to request some attrivbute value even if

those value didn't change on the publisher side. The publisher then receive a PAVU callback to which

it may answer with an UAV.

however what's the proper way?

May be you should be reading a generic HLA course like this one:
http://www.ecst.csuchico.edu/~hla/courses.html

Your question does not seems specific to CERTI implementation of HLA.

Passive/Active subscription is currenlty not supported by CERTI.

--

Eric

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

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

--

Eric