Changes between Version 19 and Version 20 of GIR3.2_ERM

Timestamp:

11/02/11 13:33:13 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GIR3.2_ERM

@@ -18 +18 @@
  * [attachment: ERM-Feedback-20111024.txt]
  * [attachment: ERM-Feedback-20111024a.txt]
-
 A second evaluation was completed after new packages were made available on November 1, 2011.
 
-
 = Embedded Real-Time Measurements How-to =
 
-Second Evaluation'''
+'''Second Evaluation'''
 Two Packages were made available for the second ERM evaluation:
   * [http://groups.geni.net/geni/attachment/wiki/Embedded%20Real-Time%20Measurements/ERM-Simulator.v.1.zip?format=raw  Simulation Source Code] 
@@ -31 +29 @@
 ==Simulation Source Code Package ==
 
-Unpack the Simulation Source Code Package:
+Unpacked the Simulation Source Code Package:
 {{{
 $ unzip ERM-Simulator.v.1.zip 
@@ -123 +121 @@
 * Events are the arrival and departure of the lightpath demands according to the Poission distribution and exponential service times.
 * This simulator can perform, unicast, anycast communication paradigms. In the case of multicast, the light-trees are configured in the network, where the optical switches (ROADMS) perform the light splitting.
-* The routing used in the simulator is Shortest-path (OSPF) and the wavelength assigments can be random or first-fit.
+* The routing used in the simulator is Shortest-path (OSPF) and the wavelength assignments can be random or first-fit.
 * Impairment-aware RWA algorithms are implemented via a Quality-of-Transmission (QoT) estimator.
 * Rudimentary energy models are implemented for the optical physical layer.
@@ -151 +149 @@
 -------------------
 Viewing the Results:
-------------------
+-------------------
 Results can be viewed in a folder created during the simulation ../output
 
@@ -187 +185 @@
 $ cd GENI_ERM_NetFPGA/NF2
 }}}
-
 A README.txt is included which documents the following:
 {{{
 The hardware portion of the ERM Box code primarily used to actuate a semiconductor optical amplifier (SOA). 
 This code is written using the existing netFPGA code structure. 
-Please visit the NetFPGA wiki (http://netfpga.org/foswiki/bin/view/NetFPGA/OneGig/Guide#Obtaining_Gateware_Software_Pack) for more informat
-ion on how to use it. 
+Please visit the NetFPGA wiki (http://netfpga.org/foswiki/bin/view/NetFPGA/OneGig/Guide#Obtaining_Gateware_Software_Pack) for more information on how to use it. 
 
 +------------------------------------------------------------------------
 | $Id$
-| 
 | Description: Quick intro to NetFPGA
 +------------------------------------------------------------------------
@@ -219 +214 @@
 | 1.0 Tree structure
 +-----------------------------------------------------------------------
-
 The tree is structured as follows:
-
 
 NetFPGA2.1-x.y
@@ -277 +270 @@
 The best way to learn how to use the tree is by example. If you look at
 the geni_umf_v3_3pin project, you will notice several things:
+
 1- The src directory contains two files: crytpo.v and user_data_path.v. These are the
    two verilog files that are created for the ERM Box NetFPGA code. 
@@ -288 +282 @@
 
 * 2.1 USING LIBRARY MODULES
-
 The lib_modules.txt file specifies a list of modules to use from the library.
 The modules are specified relative to the NetFPGA2.1-x.y/lib/verilog directory.
@@ -295 +288 @@
 
 * 2.2 ADDING YOUR OWN CODE
-
 To add your own code, write the verilog files and put them in the src directory.
 You can also choose to partition them into separate directories under src. Note
@@ -305 +297 @@
 
 * 2.3 OVERRIDING LIBRARY CODE
-
 You might decide that you only need to change one file of a library module. You
 don't need to copy all the sources and remove the library module from 
@@ -312 +303 @@
 
 * 2.4 COREGEN
-
 If you need to use IP cores generated with Xilinx's Coregen, copy the .xco file
 that was generated to your project's synth directory. You don't need any of the
@@ -323 +313 @@
 
 NF2_ROOT - set to the root directory of the tree (NetFPGA2.1-x.y)
-NF2_DESIGN_DIR - set to the project's directory 
-                 (e.g. $NF2_ROOT/projects/reference_nic)
+NF2_DESIGN_DIR - set to the project's directory (e.g. $NF2_ROOT/projects/reference_nic)
 NF2_WORK_DIR - set to the working directory (somewhere with lots of space)
 
@@ -334 +323 @@
 to your setup. THE DEFAULTS WILL *NOT* WORK!
 
-
 +-----------------------------------------------------------------------
 | 4.0 Simulation
 +-----------------------------------------------------------------------
-
 To simulate your design, there are several libraries to help. Take a look
 at reference_router/verif/test_router_full to see how to use the perl
@@ -361 +348 @@
 | 5.0 Implementation
 +-----------------------------------------------------------------------
-
 To implement your design, cd to the synth directory and type make. If all
 goes well, you should end up with nf2_top_par.bit file that you can use 
@@ -374 +360 @@
 | 6.0 Running the hardware
 +-----------------------------------------------------------------------
-
 To run the hardware, there are two steps:
 1- load the kernel module
@@ -398 +383 @@
 | 7.0 Contacts 
 +-----------------------------------------------------------------------
-
 - Jad Naous <first initial last name at stanford period edu> 
         For reference design questions, library modules, synthesis and 
         simulation makefile questions.
-
 - Glen Gibb <first initial r last initial at stanford period edu>
         For board problems and simulation Perl libraries.
 }}}
+
+The review of the README conclude the second evaluation; Software evaluation was not possible.