Package: inet.tutorials.queueing
GenericSchedulerTutorialStep
network(no description)
Usage diagram
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram.
Properties
| Name | Value | Description |
|---|---|---|
| isNetwork | ||
| display | bgb=600,300 |
Unassigned submodule parameters
| Name | Type | Default value | Description |
|---|---|---|---|
| provider1.displayStringTextFormat | string | "created %p pk (%l)" |
determines the text that is written on top of the submodule |
| provider1.packetNameFormat | string | "%a-%c" |
see directives in module documentation |
| provider1.packetRepresentation | string | "byteCount" |
determines the chunk of the packet data |
| provider1.packetLength | int | ||
| provider1.packetData | int | -1 | |
| provider1.attachCreationTimeTag | bool | true | |
| provider1.attachIdentityTag | bool | true | |
| provider1.attachDirectionTag | bool | true | |
| provider1.clockModule | string | "" |
relative path of a module that implements IClock(1,2); optional |
| provider1.providingInterval | double | 0s |
elapsed time between subsequent packets allowed to be pulled by the connected packet collector, 0 means any number of packets can be pulled at the same simulation time |
| provider1.scheduleForAbsoluteTime | bool | true |
when a clock is used relative means that setting the clock will not affect the simulation time of the event |
| provider2.displayStringTextFormat | string | "created %p pk (%l)" |
determines the text that is written on top of the submodule |
| provider2.packetNameFormat | string | "%a-%c" |
see directives in module documentation |
| provider2.packetRepresentation | string | "byteCount" |
determines the chunk of the packet data |
| provider2.packetLength | int | ||
| provider2.packetData | int | -1 | |
| provider2.attachCreationTimeTag | bool | true | |
| provider2.attachIdentityTag | bool | true | |
| provider2.attachDirectionTag | bool | true | |
| provider2.clockModule | string | "" |
relative path of a module that implements IClock(1,2); optional |
| provider2.providingInterval | double | 0s |
elapsed time between subsequent packets allowed to be pulled by the connected packet collector, 0 means any number of packets can be pulled at the same simulation time |
| provider2.scheduleForAbsoluteTime | bool | true |
when a clock is used relative means that setting the clock will not affect the simulation time of the event |
| scheduler.displayStringTextFormat | string | "scheduled %p pk (%l)" |
determines the text that is written on top of the submodule |
| scheduler.reverseOrder | bool | false | |
| scheduler.schedulerClass | string |
determines the input queue of the packet, the parameter must be the name of a C++ class which implements the IPacketSchedulerFunction interface and is registered via Register_Class |
|
| collector.displayStringTextFormat | string | "received %p pk (%l)" |
determines the text that is written on top of the submodule |
| collector.clockModule | string | "" |
relative path of a module that implements IClock(1,2); optional |
| collector.initialCollectionOffset | double | 0s | |
| collector.collectionInterval | double |
elapsed time between subsequent packets pulled from the connected packet provider |
|
| collector.scheduleForAbsoluteTime | bool | true |
when a clock is used relative means that setting the clock will not affect the simulation time of the event |
Source code
network GenericSchedulerTutorialStep { @display("bgb=600,300"); submodules: provider1: PassivePacketSource { @display("p=100,100"); } provider2: PassivePacketSource { @display("p=100,200"); } scheduler: PacketScheduler { @display("p=300,100"); } collector: ActivePacketSink { @display("p=500,100"); } connections allowunconnected: provider1.out --> scheduler.in++; provider2.out --> scheduler.in++; scheduler.out --> collector.in; } //-------------------------------------------------File: tutorials/queueing/QueueingTutorial.ned