Changes between Version 2 and Version 3 of SysopConsoleSpec


Ignore:
Timestamp:
01/19/2021 08:30:24 AM (5 years ago)
Author:
jdalbey
Comment:

more features

Legend:

Unmodified
Added
Removed
Modified
  • SysopConsoleSpec

    v2 v3  
    1212Play audio test clip for volume check 
    1313 
    14 Delete any existing log files:  CADcomments.log, Activity Log, etc. 
     14Delete (or reset) any existing log files:  CADcomments, Activity Log, CADdetails, unified log, evaluation log, cms and har messages, LCS database.   Might be nice to specify log files with test data for development runs.  
    1515 
    1616Create or select list of students (for CAD Clients, Activity Log, etc) 
    1717 
    18 Start the webserver  (locally if Development Workstation) 
     18Start the webserver  (locally if Development Workstation) 
    1919 
    2020Select a traffic model 
     
    2424Select a simulation Scenario 
    2525 
    26 Start the Simulation Manager with desired Scenario[[BR]][[BR]]Start Unified Logger Service (maybe this should be a daemon?)[[BR]][[BR]]Launch a browser with our webapps: 
     26Launch the Simulation Manager with desired Scenario (Note: operator must press the "Start" button on the GUI to begin the simulation).  
    2727 
    28  * einotebook   
    29  * cptms  
    30  * unifiedlogmonitor 
     28Launch the Lane Control System, if necessary, or show status. 
     29 
     30Start Unified Logger Service (maybe this should be a daemon?)[[BR]][[BR]]Launch a browser with our webapps: 
     31 
     32 * Instructor notebook 
     33 * CPTMS 
     34 * unified log monitor 
    3135 
    3236Launch a browser on separate monitor to show CMS/Har messages 
     
    3741 
    3842Archive log files (at end of session) 
     43 
     44---- 
     45== Optional Features == 
     46Be able to save the settings that have been selected for a certain run and provide a description.  Then be able to load the console from saved settings, such as "Practice scenario: hay truck incident".  I think this configuration consists of three items: 
     47 
     48 * Scenario script and resources 
     49 * Traffic model corresponding to the script 
     50 * LCS data corresponding to the script 
     51 
     52but conceivably might include other items, such as CMS messages already active.