You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While simulating the ns-3 filter example (examples/ns3-filter.cc and examples/fed-filter.cc), the federate sends and receives the messages, without it passing through ns-3, even though the end point names in ns-3 match the end points in the federate. This example was tried with no modification from the user.
Versions:
ns-3 source: https://github.com/nsnam/ns-3-dev-git
helics-ns3: Branch: HELICS_2_0
HELICS-src: Tag/v2.0.0-rc1
The simulation was run using these commands -
In terminal 1: helics_broker --federates 2
In terminal 2: From ns-3 source, ./waf --run scratch/ns-3 filter
In terminal 3: From ns-3 source, ./waf --run scratch/fed-filter
The following warning was found in ns-3 log for endpoint 1 and 2 -
The text was updated successfully, but these errors were encountered:
While simulating the ns-3 filter example (examples/ns3-filter.cc and examples/fed-filter.cc), the federate sends and receives the messages, without it passing through ns-3, even though the end point names in ns-3 match the end points in the federate. This example was tried with no modification from the user.
Versions:
ns-3 source: https://github.com/nsnam/ns-3-dev-git
helics-ns3: Branch: HELICS_2_0
HELICS-src: Tag/v2.0.0-rc1
The simulation was run using these commands -
In terminal 1: helics_broker --federates 2
In terminal 2: From ns-3 source, ./waf --run scratch/ns-3 filter
In terminal 3: From ns-3 source, ./waf --run scratch/fed-filter
The following warning was found in ns-3 log for endpoint 1 and 2 -
The text was updated successfully, but these errors were encountered: