Changes between Version 1 and Version 2 of WARPLab/Framework/Modules

Timestamp:

May 15, 2013, 2:38:18 PM (11 years ago)

Author:

chunter

Comment:

--

WARPLab/Framework/Modules

@@ -2 +2 @@
 = WARPLab Modules =
 
-
-
-
-
-----OLD BELOW----
-A typical WARPLab experiment script contains a collection of {{{Node}}} objects and a single {{{Trigger}}} object.
+The WARPLab Framework consists of 5 core modules: the {{{Node}}}, the {{{Baseband}}}, the {{{Interface Group}}}, the {{{Transport}}}, the {{{Trigger Manager}}}, and {{{User Extensions}}}.
 
 [[Image(typical.png,width=800)]]
 
-Attached to each {{{Node}}} is a number of different submodules: {{{Baseband}}}, {{{Interface Group}}}, {{{Transport}}}, {{{Trigger Manager}}}, and {{{User Extension}}}. Each of these modules are objects from different MATLAB classes. This document serves to explain each MATLAB class and what it is responsible for.
+The above figure shows how these 5 modules relate to one another in the context of a typical WARPLab example script. Additionally, the figure shows another framework element, the {{{Trigger}}}, which is not a part of a WARPLab node, but is one way of coordinating action among the multiple nodes in a WARPLab experiment.
 
 === Node ===
-[[Image(node.png,width=800)]]
 
-A {{{Node}}} is an object of the [browser:ResearchApps/PHY/WARPLAB/WARPLab7/M_Code_Reference/classes/wl_node.m wl_node class]. The primary role of the node object is to broker commands to other modules within the node and collect responses to those commands to deliver back to the user. Furthermore, the methods within the wl_node class are able to deal with vector inputs of of multiple wl_node objects, allowing automatic iteration through the provided nodes to replicate a single command provided by the user script. Beyond being the access point for users to interact with all of the modules in a WARPLab node, the wl_node class processes a few node-level commands of its own (such as [wiki:../../Commands/Node#identify identify]-- a command to help users identify a particular node by blinking LEDs on the hardware).
+A {{{Node}}} is responsible for broker commands to other modules within the node and collect responses to those commands to deliver back to the user. The other modules in the system belong to the {{{Node}}} module. Furthermore, the {{{Node}}} may also process commands for the node itself and not any of the other modules. The WARPLab Reference Design's implementation of a {{{Node}}} module is [wiki:../Reference/Node described here].
 
 === Trigger ===