Changes between Version 10 and Version 11 of Documentation/bAccountManagement/aScheduler

Timestamp:

Mar 31, 2008, 5:36:43 PM (16 years ago)

Author:

Joseph F. Miklojcik III

Comment:

minor typo fixes

Documentation/bAccountManagement/aScheduler

@@ -3 +3 @@
 == Reservations ==
 
-As this is a wireless testbed, it is difficult to run multiple experiments without interference. Therefore, we currently only support one experiment at a time on the individual grid. In Orbit speak, a grid is a set of nodes together with the controling console which can be used to run experiments. In the present setup, the testbed consists of a signle large grid (main grid) with 400 nodes and an array of sandboxes i.e. "grids" with only 2 nodes and a console, which are development and test environments intended to reduce the time experimenters need on the main grid. Ideally, experimenters develop their software (application programs, routing protocols, measurement instrumentation, etc.) on offsite machines and then use the sandboxes for integration with the orbit environment and orbit software infrastructure. Once the experiment runs successfully in the sandbox environment, it can be moved to the main grid.
+As this is a wireless testbed, it is difficult to run multiple experiments without interference. Therefore, we currently only support one experiment at a time on the individual grid. In Orbit speak, a grid is a set of nodes together with the controlling console which can be used to run experiments. In the present setup, the testbed consists of a single large grid (main grid) with 400 nodes and an array of sandboxes i.e. "grids" with only 2 nodes and a console, which are development and test environments intended to reduce the time experimenters need on the main grid. Ideally, experimenters develop their software (application programs, routing protocols, measurement instrumentation, etc.) on off-site machines and then use the sandboxes for integration with the orbit environment and orbit software infrastructure. Once the experiment runs successfully in the sandbox environment, it can be moved to the main grid.
 
 ||[[Image(Schedule-howto3.jpg, width=500)]]||
@@ -32 +32 @@
 Two tier reservation approval policy: scheduling requests received before noon will be pre-approved for the following day. For example, if it is Tuesday morning before noon, and you ask for 4 to 6 in the evening Wednesday, you will know for sure whether you have this time by 2 in the afternoon on Tuesday. Users are limited to two hours a day of pre-approved time on the main grid.
 
-For the reservations that are made less than twelve hours in advance or for ones that are more tha 2 hours a day the slots will be automatically approved at the begining of the slot.
+For the reservations that are made less than twelve hours in advance or for ones that are more than 2 hours a day the slots will be automatically approved at the begining of the slot.