cosmos 4.5.0 → 5.0.2.pre.beta2

data/data/config/system.yaml

@@ -1,371 +0,0 @@
----
-AUTO_DECLARE_TARGETS:
-  summary: Automatically load all the target folders under config/targets into the system
-  description:
-    When automatically discovering target folders the COSMOS naming convention
-    must be followed. Target folders must be uppercase and be named according to how
-    COSMOS will access them. For example, if you create a config/targets/INST directory,
-    COSMOS will create a target named 'INST' which is how it will be referenced.
-    This keyword is REQUIRED unless you individually declare your targets using the
-    DECLARE_TARGET keyword.
-DECLARE_TARGET:
-  summary: Declare a COSMOS target and name it
-  description:
-    Declare target is used in place of AUTO_DECLARE_TARGETS to give more
-    fine grained control over how the target folder is loaded and named within COSMOS.
-    This is required if AUTO_DECLARE_TARGET is not present.
-  example: DECLARE_TARGET INST INST2 inst.txt
-  parameters:
-    - name: Target Name
-      required: true
-      description: The directory name which contains the target information.
-        This must match a directory under config/targets.
-      values: <%= System.targets.keys %>
-    - name: Substitute Target Name
-      required: false
-      description: The target name in the COSMOS system. This is how the target
-        will be referred to in scripts. If this is not given (or given as nil)
-        the target name will be the directory name given above.
-    - name: Target Filename
-      required: false
-      description:
-        The name of the file in the target directory which contains the
-        configuration information for the target. By default this is 'target.txt'
-        but if you want to rename this you need to set this parameter.
-DECLARE_GEM_TARGET:
-  summary: Declare a COSMOS target which resides in a Ruby gem
-  description: COSMOS targets can be distributed in gem form in which case they
-    must be named 'cosmos-<gem-name>' where <gem-name> is the descriptive name of
-    the gem. See the COSMOS documentation at cosmosrb.com for for information on
-    creating a COSMOS gem target.
-  parameters:
-    - name: Gem Name
-      required: true
-      description:
-        The COSMOS gem name which must be cosmos-<gem-name> where <gem-name>
-        is the descriptive gem name. In the above example, the target will be named
-        'GEM-NAME' (note the cosmos- prefix is stripped off).
-      values: .+
-    - name: Substitute Target Name
-      required: false
-      description: The target name in the COSMOS system. This is how the target
-        will be referred to in scripts. If this is not given (or given as nil)
-        the target name will be the gem name as described above.
-    - name: Target Filename
-      required: false
-      description:
-        The name of the file in the target directory which contains the
-        configuration information for the target. By default this is 'target.txt'
-        but if you want to rename this you need to set this parameter.
-DECLARE_GEM_MULTI_TARGET:
-  summary: Declare a COSMOS target which resides in a Ruby gem with multiple targets
-  description: COSMOS targets can be distributed in gem form in which case they
-    must be named 'cosmos-<gem-name>' where <gem-name> is the descriptive name of
-    the gem. Multiple Targets can be packaged into a single gem. This directive
-    will tell COSMOS where to look for a target inside the first directory level
-    of the gem.  The sub-directory name must be all uppercase and must contain a
-    sub-directory named 'cmd_tlm'. See the COSMOS documentation at cosmosrb.com
-    for for information on creating a COSMOS gem target.
-  parameters:
-    - name: Gem Name
-      required: true
-      description:
-        The COSMOS gem name which must be cosmos-<gem-name> where <gem-name>
-        is the descriptive gem name. In the above example, the target will be named
-        'GEM-NAME' (note the cosmos- prefix is stripped off).
-      values: .+
-    - name: Target Name
-      required: true
-      description: The directory name which contains the target information.
-        This must match a directory under the first level of the gem base directory.
-      values: .+
-    - name: Substitute Target Name
-      required: false
-      description: The target name in the COSMOS system. This is how the target
-        will be referred to in scripts. If this is not given (or given as nil)
-        the target name will be the gem name as described above.
-    - name: Target Filename
-      required: false
-      description:
-        The name of the file in the target directory which contains the
-        configuration information for the target. By default this is 'target.txt'
-        but if you want to rename this you need to set this parameter.
-PORT:
-  summary: Set a Server Port
-  description:
-    Port is used to set the default ports used by the Command and Telemetry Server.
-    It is not necessary to set this option unless you wish to override the defaults
-    (given in the example usage). Overriding ports is necessary if you want to run
-    two Command and Telemetry Servers on the same computer simultaneously.
-  example: |
-    PORT CTS_API 7777 # Default
-    PORT TLMVIEWER_API 7778 # Default
-    PORT CTS_PREIDENTIFIED 7779 # Default
-  parameters:
-    - name: Port Name
-      required: true
-      description:
-        CTS_API - This port is what tools connect to to communicate with the COSMOS Scripting API.
-        TLMVIEWER_API - This port is used to remotely open and close telemetry screens in Telemetry Viewer.
-        CTS_PREIDENTIFIED - This port provides access to a preidentified stream of all telemetry packets
-        in the system. This is currently used by Telemetry Grapher and can be used to chain Command
-        and Telemetry Servers together as it also accepts commands.
-        CTS_CMD_ROUTER - This port provides access to a stream of all command packets
-        that have been accepted by COSMOS.
-      values: <%= %w(CTS_API TLMVIEWER_API CTS_PREIDENTIFIED CTS_CMD_ROUTER) %>
-    - name: Port Value
-      required: true
-      description: Port number to use for the specified port name
-      values: '\d{2,}'
-LISTEN_HOST:
-  summary: IP addresses or host names to bind API ports to
-  since: 4.0.0
-  parameters:
-    - name: Host Port Name
-      required: true
-      description:
-        CTS_API - This port is what tools connect to to communicate with the COSMOS Scripting API.
-        TLMVIEWER_API - This port is used to remotely open and close telemetry screens in Telemetry Viewer.
-        CTS_PREIDENTIFIED - This port provides access to a preidentified stream of all telemetry packets
-        in the system. This is currently used by Telemetry Grapher and can be used to chain Command
-        and Telemetry Servers together as it also accepts commands.
-        CTS_CMD_ROUTER - This port provides access to a stream of all command packets
-        that have been accepted by COSMOS.
-      values: <%= %w(CTS_API TLMVIEWER_API CTS_PREIDENTIFIED CTS_CMD_ROUTER) %>
-    - name: Host Value
-      required: true
-      description:
-        The IP address or host name to bind the Host Port Name to. By default,
-        the CTS_API and TLMVIEWER_API are bound to localhost meaning that only tools
-        on the same machine can connect. By default, CTS_PREIDENTIFIED and CTS_CMD_ROUTER
-        are bound to '0.0.0.0' to allow for tools on any machines to connect. This
-        allows for chaining two or more Servers out of the box.
-      values: .+
-CONNECT_HOST:
-  summary: IP addresses or host names to connect tools to
-  since: 4.0.0
-  parameters:
-    - name: Host Port Name
-      required: true
-      description:
-        CTS_API - This port is what tools connect to to communicate with the COSMOS Scripting API.
-        TLMVIEWER_API - This port is used to remotely open and close telemetry screens in Telemetry Viewer.
-        CTS_PREIDENTIFIED - This port provides access to a preidentified stream of all telemetry packets
-        in the system. This is currently used by Telemetry Grapher and can be used to chain Command
-        and Telemetry Servers together as it also accepts commands.
-        CTS_CMD_ROUTER - This port provides access to a stream of all command packets
-        that have been accepted by COSMOS.
-      values: <%= %w(CTS_API TLMVIEWER_API CTS_PREIDENTIFIED CTS_CMD_ROUTER) %>
-    - name: Host Value
-      required: true
-      description:
-        The IP address or host name to connect tools to. By default all
-        ports are bound to localhost so all tools connect to the local machine.
-      values: .+
-PATH:
-  summary: Set a Server Path
-  description:
-    Path is used to set the default paths used by the Command and Telemetry Server
-    to access or create files. It is not necessary to set this option unless you wish to
-    override the defaults (given in the example usage).
-  warning:
-    The PROCEDURES path must be set for Script Runner and Test Runner to locate your
-    procedure files. You can add multiple 'PATH PROCEDURES' lines to your configuration file
-    to set multiple locations.
-  example: |
-    PATH LOGS './logs' # Default location of system and tool log files
-    PATH TMP './tmp' # Default location of temporary marshal files
-    PATH SAVED_CONFIG './saved_config' # Default location of saved configurations (see note)
-    PATH TABLES './tables' # Default location of table files
-    PATH PROCEDURES './procedures' # Default location of Script procedure files
-    PATH HANDBOOKS './handbooks' # Default location to place handbook files
-  parameters:
-    - name: Path Name
-      required: true
-      description: Path name to set.
-      values: <%= %w(LOGS TMP SAVED_CONFIG TABLES PROCEDURES HANDBOOK) %>
-    - name: Path Value
-      required: true
-      description: File system path to use for the specified path name
-      values: .+
-DEFAULT_PACKET_LOG_WRITER:
-  summary: Set the class used when creating binary packet log files
-  warning: Overriding the default log writer can break the ability to write log
-    files that COSMOS can interpret. Proceed with caution!
-  example: DEFAULT_PACKET_LOG_WRITER packet_log_writer.rb # Default
-  parameters:
-    - name: Filename
-      required: true
-      description: Ruby file to use when instantiating a new log writer
-      values: '.+\.rb'
-    - name: parameter
-      required: false
-      description: Parameters which are passed to the log read upon initialization
-      values: .*
-      since: 4.0.0
-DEFAULT_PACKET_LOG_READER:
-  summary: Set the class used when reading binary packet log file
-  warning: Overriding the default log read can break the ability to read log
-    files. Proceed with caution!
-  example: DEFAULT_PACKET_LOG_READER packet_log_reader.rb # Default
-  parameters:
-    - name: Filename
-      required: true
-      description: Ruby file to use when instantiating a new log writer
-      values: '.+\.rb'
-    - name: parameter
-      required: false
-      description: Parameters which are passed to the log read upon initialization
-      values: .*
-      since: 4.0.0
-STALENESS_SECONDS:
-  summary: Number of seconds before marking the packet stale
-  description:
-    A stale packet is identified in telemetry screens by all the telemetry
-    items in the stale packet being colored purple..
-  example: STALENESS_SECONDS 30 # Default
-  parameters:
-    - name: Seconds
-      required: true
-      description: Integer number of seconds before packets are marked stale
-      values: '\d+'
-ENABLE_DNS:
-  summary: Enable reverse DNS lookups for tools
-  description: Enables reverse DNS lookups when tools connect to the Command and
-    Telemetry Server's pre-identified socket or to any target using the TCPIP Server
-    Interface. As of COSMOS 3.5.0 the default is to not use DNS.
-  since: 3.5.0
-DISABLE_DNS:
-  summary: Disable reverse DNS lookups for tools
-  description: Disable reverse DNS lookups when tools connect to the Command and
-    Telemetry Server's pre-identified socket or to any target using the TCPIP Server
-    Interface. This is useful when you are in an environment where DNS is not available.
-    As of COSMOS 3.5.0 the default is to not use DNS
-ENABLE_SOUND:
-  summary: Enable audible sounds when popups occur
-  description:
-    Enable sound makes any prompts that occur in ScriptRunner/TestRunner
-    make an audible sound when they popup to alert the operator of needed input.
-  since: 3.5.0
-ALLOW_ACCESS:
-  summary: White list machines that are allowed to connect to the Server
-  example: ALLOW_ACCESS ALL # Default
-  parameters:
-    - name: Name or IP Address
-      required: true
-      description:
-        Machine name to allow access or you can specify 'ALL' to allow
-        all machines access
-      values: .+
-META_INIT:
-  summary: Specify a file to initialize the SYSTEM META packet
-  description:
-    Filename should be a text file with key value pairs where the keyword
-    matches an item in the SYSTEM META packet. Note you do not have to specify ALL
-    the items in the SYSTEM META packet.
-  since: 4.0.0
-  parameters:
-    - name: Filename
-      required: true
-      description: Filename, either fully qualified, or relative to Cosmos::USERPATH
-      values: .+
-TIME_ZONE_UTC:
-  summary: Report all times as UTC
-  description:
-    COSMOS will report all times as UTC time. If this keyword is not used,
-    COSMOS will report all times as local times, where the local time zone is determined
-    automatically by Ruby based upon the operating system time settings. This setting
-    affects packet receive times, timestamped log filenames, message logs,
-    Cmd/Tlm extractor time ranges, etc.
-  since: 3.10.0
-ADD_HASH_FILE:
-  summary: Add a file to the hashing sum calculation
-  description:
-    Adds a file to the set of files used in marshal file hashing sum calculation.
-    Upon startup, COSMOS calculates a hashing sum over the command/telemetry definition files
-    for all targets. After the definitions have been processed, COSMOS saves the resulting
-    objects as marshal files in a folder with the hashing sum as part of the name.
-    The next time COSMOS runs, if the hashing sum of the cmd/tlm definition files
-    has not changed, COSMOS can load the marshal files instead of re-processing the definitions.
-    If a file is specified with the ADD_HASH_FILE keyword, COSMOS will include it in the
-    hashing sum calculation. This means that a change in the file will cause COSMOS to
-    re-process the cmd/tlm defintions and create a new set of marshal files.
-    The default hashing algorithm is MD5, but other Ruby Digest algorithms are also supported,
-    like SHA1 and SHA256
-  since: 4.4.0
-  example: ADD_HASH_FILE lib/user_version.rb
-  parameters:
-    - name: Filename
-      required: true
-      description: Filename, either fully qualified, or relative to Cosmos::USERPATH
-      values: '.+\.rb'
-CLASSIFICATION:
-  summary: Add a classification banner to the top of all the COSMOS tools
-  since: 4.3.0
-  example: |
-    CLASSIFICATION Unclassified green
-    CLASSIFICATION Secret 255 114 0
-  parameters:
-    - name: Display Text
-      required: true
-      description: The text to display in the classification banner
-      values: ".*"
-    - name: Color Name | Red Hex
-      required: true
-      description: The color name or the red value of a RGB triplet
-      values: ".*"
-    - name: Green Hex
-      required: false
-      description: The green value of a RGB triplet
-      values: '\d+'
-    - name: Blue Hex
-      required: false
-      description: The blue value of a RGB triplet
-      values: '\d+'
-HASHING_ALGORITHM:
-  summary: Specify which Ruby Digest hashing algorithm to use
-  description:
-    Set the hashing algorithm used for config hashing, tlm_viewer hashing, and
-    script hashing. COSMOS will truncate the resulting hash string down to 32 characters
-  since: 4.4.0
-  example: HASHING_ALGORITHM SHA256
-  parameters:
-    - name: Algorithm
-      required: true
-      description: Digest algorithm, one of MD5, RMD160, SHA1, SHA256, SHA384, SHA512
-      values: .+
-ALLOW_ROUTER_COMMANDING:
-  summary: Allow routers to receive and forward commands to interfaces
-  since: 4.5.0
-  example: ALLOW_ROUTER_COMMANDING
-X_CSRF_TOKEN:
-  summary: Secret token passed with API calls
-  since: 4.5.0
-  example: X_CSRF_TOKEN Secret
-  parameters:
-    - name: token
-      required: true
-      description: Token passed with api calls
-      values: .+
-ALLOW_ORIGIN:
-  summary: Allow a specific HTTP Origin header in Api calls
-  description: This keyword should only be used if COSMOS needs to be commanded from a web server.
-  since: 4.5.0
-  example: ALLOW_ORIGIN 1.2.4.4:8080
-  parameters:
-    - name: origin
-      required: true
-      description: Hostname colon port of origin
-      values: .+
-ALLOW_HOST:
-  summary: Allow a specific HTTP Host header in Api calls
-  description:
-    By default includes ['127.0.0.1:7777', '127.0.0.1:7778', '127.0.0.1:7877', '127.0.0.1:8779', '127.0.0.1:8780'].
-    API Ports changed by a PORT line will also be added automatically.  If you need external connections you must add your ip and
-    these ports to allow external access to work for apis
-  example: ALLOW_HOST 1.2.4.4:7777
-  parameters:
-    - name: host
-      required: true
-      description: Hostname colon port of host
-      values: .+

data/data/config/test_runner.yaml

@@ -1,119 +0,0 @@
----
-<%= MetaConfigParser.load('script_runner.yaml').to_meta_config_yaml(0) %>
-LOAD_UTILITY:
-  summary: Specify a test procedure to load into Test Runner
-  description: Procedures will be found automatically in the procedures directory
-    or can be given by a path relative to the COSMOS install directory or by an
-    absolute path.
-  parameters:
-    - name: Filename
-      required: true
-      description: Name of the test file in quotes
-      values: '.+\.rb'
-RESULTS_WRITER:
-  summary: Specify a different Ruby file to interpret and print the Test Runner results
-  description: The specified Ruby file must define a class which implements the
-    Cosmos::ResultsWriter API
-  parameters:
-    - name: Filename
-      required: true
-      description: Name of the Ruby file which implements a result writer
-      values: '.+\.rb'
-    - name: Class Parameters
-      required: false
-      description: Parameters to pass to the constructor of the results writer
-      values: .*
-ALLOW_DEBUG:
-  summary: Whether to allow the user to enable the debug line where the user can enter arbitrary statements
-PAUSE_ON_ERROR:
-  summary: Set or clear the pause on error checkbox
-  description: If this is checked, Test Runner will pause if the test encounters
-    an error. Otherwise the error will be logged but the script will continue.
-  parameters:
-    - name: Enable
-      required: true
-      description: Whether to pause when the script encounters an error
-      values: ['TRUE', 'FALSE']
-CONTINUE_TEST_CASE_AFTER_ERROR:
-  summary: Set or clear the continue test case after error checkbox
-  description: If this is checked, Test Runner will continue executing the current
-    test case after encountering an error. Otherwise the test case will stop at
-    the error and the next test case will execute.
-  parameters:
-    - name: Enable
-      required: true
-      description: Whether to continue the test case when the script encounters an error
-      values: ['TRUE', 'FALSE']
-ABORT_TESTING_AFTER_ERROR:
-  summary: Set or clear the abort testing after error checkbox
-  description: If this is checked, Test Runner will stop executing after the current
-    test case completes (how it completes depends on CONTINUE_TEST_CASE_AFTER_ERROR).
-    Otherwise the next test case will execute.
-  parameters:
-    - name: Enable
-      required: true
-      description: Whether to continue to the next test case when the script encounters an error
-      values: ['TRUE', 'FALSE']
-MANUAL:
-  summary: Set the $manual global variable for all executing scripts
-  description: The $manual variable can be checked during tests to allow for fully
-    automated tests if it is not set, or for user input if it is set. This capability
-    is completely dependent on user specific code which checks the $manual variable.
-  parameters:
-    - name: Enable
-      required: true
-      description: Whether to set the $manual global to true
-      values: ['TRUE', 'FALSE']
-LOOP_TESTING:
-  summary: Set or clear the loop testing checkbox
-  description: If this is checked, Test Runner will continue to run whatever level
-    of tests that were initially started. If either "Abort Testing after Error"
-    or "Break Loop after Error" are checked, then the loop testing will stop if
-    an error is encountered. The difference is that the "Abort Testing after Error"
-    will stop testing immediately after the current test case completes.
-    "Break Loop after Error" continues the current loop by executing the remaining
-    suite or group before stopping. In the case of executing a single test case
-    the options effectively do the same thing.
-  parameters:
-    - name: Enable
-      required: true
-      description: Whether to loop the selected test level
-      values: ['TRUE', 'FALSE']
-BREAK_LOOP_AFTER_ERROR:
-  summary: Set or clear the break loop after error checkbox
-  description: If this is checked, Test Runner continues the current loop by
-    executing the remaining suite or group before stopping.
-  parameters:
-    - name: Enable
-      required: true
-      description: Whether to break the loop after encountering an error
-      values: ['TRUE', 'FALSE']
-IGNORE_TEST:
-  summary: Ignore the given test class name when parsing the tests
-  parameters:
-    - name: Test Class Name
-      required: true
-      description: The test class to ignore when building the list of available tests
-      values: .+
-IGNORE_TEST_SUITE:
-  summary: Ignores the given test suite name when parsing the tests
-  parameters:
-    - name: Test Suite Name
-      required: true
-      description: The test suite to ignore when building the list of available tests
-      values: .+
-CREATE_DATA_PACKAGE:
-  summary: Creates a data package of every file created during the test
-AUTO_CYCLE_LOGS:
-  summary: Automatically start a new server message log and cmd/tlm logs at the
-    beginning and end of each test. Typically used in combination with CREATE_DATA_PACKAGE.
-COLLECT_METADATA:
-  summary: Prompt for Meta Data before starting tests
-DISABLE_TEST_SUITE_START:
-  summary: Disable the Test Suite Start button to prevent all tests in the Suite from running.
-    This is a useful option if you're simply using Suites and Groups to organize test cases but
-    do not want a user to accidentally run them all.
-DISABLE_TEST_GROUP_START:
-  summary: Disable the Test Group Start button to prevent all tests in the Group from running.
-    This is a useful option if you're simply using Suites and Groups to organize test cases but
-    do not want a user to accidentally run them all.

data/data/config/tlm_extractor.yaml

@@ -1,109 +0,0 @@
----
-DELIMITER:
-  summary: Specify an alternative column delimiter over the default tab character
-  parameters:
-    - name: Delimiter
-      required: true
-      description: Character or string to use as a delimiter. For example ','.
-      values: .+
-FILL_DOWN:
-  summary: Insert a value into every row of the output
-  description: Telemetry Grapher produces an output file with columns for each
-    item name. If you are graphing items from different packets, only the columns
-    with items from that packet are populated with values. Fill down causes a
-    particular item column to be populated with the previous value so every column
-    is 'filled'. This makes it easier to graph multiple values across packets in Excel.
-DOWNSAMPLE_SECONDS:
-  summary: Downsample data to only output a value every X seconds of time
-  parameters:
-    - name: Seconds
-      required: true
-      desription: Number of seconds to skip between values output
-      values: \d+
-MATLAB_HEADER:
-  summary: Prepend the Matlab comment symbol of '%' to the header lines in the output file
-UNIQUE_ONLY:
-  summary: Only output a row if one of the extracted values has changed
-  description: This keyword is useful to extract telemetry items over a large time
-    period by only outputting those values where items have changed
-UNIQUE_IGNORE:
-  summary: Used in conjunction with UNIQUE_ONLY to control which items should be checked
-    for changing values
-  description: This list of telemetry items (not target names or packet names)
-    always includes the COSMOS metadata items named RECEIVED_TIMEFORMATTED and RECEIVED_SECONDS.
-    This is because these items will always change from packet to packet which would
-    cause them to ALWAYS be printed if UNIQUE_ONLY was used. To avoid this,
-    but still include time stamps in the output, UNIQUE_IGNORE includes these items.
-    Use this keyword if you have a similar telemetry item that you want to display
-    in the output but not be used to determine uniqueness.
-  parameters:
-    - name: Item Name
-      required: true
-      description: Name of the item to exclude from the uniqueness criteria.
-        Note that all items with this name in all target packets are affected.
-      values: .+
-SHARE_COLUMNS:
-  summary: Export telemetry items with the same name into the same column
-  description: Normally items from different packets are put in their own column
-    in the output. If this keyword is used, items with the same name in different
-    packets will now share one column in the output. This applies to all telemetry
-    items with identical names. If you want to share columns for only specific items,
-    use the SHARE_COLUMN keyword instead.
-SHARE_COLUMN:
-  summary: Export telemetry items with the same name into the same column
-  description: Normally items from different packets are put in their own column
-    in the output. This keyword is used to specify specific items that are from different
-    packets but should share one column in the output. This applies to all telemetry
-    items with identical names. If you want to share columns for all duplicate item
-    names in different packets, use the SHARE_COLUMNS keyword instead.
-  since: 3.9.2
-  parameters:
-    - name: Item Name
-      required: true
-      description: Name of the telemtry item
-      values: .+
-    - name: Item Type
-      required: false
-      description: Type of the telemetry item
-      values: ['CONVERTED', 'RAW', 'FORMATTED', 'WITH_UNITS']
-FULL_COLUMN_NAMES:
-  summary: Use TARGET PACKET ITEM as the column header for each column
-  description: Normally just the item name is used as the column header but this
-    adds the target and packet name. Note that the TARGET and PACKET columns
-    are not generated when this mode is active since the items are fully qualified.
-DONT_OUTPUT_FILENAMES:
-  summary: Don't output the list of input filenames at the top of each output file
-TEXT:
-  summary: Insert arbitrary text in the Telemetry Extractor output
-  description: Text also allows you to dynamically create Excel formulas using a special syntax
-  parameters:
-    - name: Header
-      required: true
-      description: The column header text
-      values: .+
-    - name: Text
-      required: true
-      description: Text to put in the output file. The special character '%' will
-        be translated to the current row of the output file. This is useful for
-        Excel formulas which need a reference to a cell. Remember the first two
-        columns are typically the TARGET and PACKET and telemetry items start in
-        column 'C' in Excel.
-ITEM:
-  summary: Specify a telemetry item to extract
-  parameters:
-    - name: Target Name
-      required: true
-      description: Name of the telemetry target
-      values: <%= System.targets.keys %>
-    - name: Packet Name
-      required: true
-      description: Name of the telemetry packet
-      values: .+
-    - name: Item Name
-      required: true
-      description: Name of the telemetry item
-      values: .+
-    - name: Item Type
-      required: false
-      description: Type of the telemetry item
-      values: ['CONVERTED', 'RAW', 'FORMATTED', 'WITH_UNITS']

data/data/config/tlm_grapher.yaml

@@ -1,78 +0,0 @@
----
-# Require data_object to access the COLOR_LIST
-<% require 'cosmos/tools/tlm_grapher/data_objects/data_object' %>
-POINTS_SAVED:
-  summary: Number of points saved in the plot history
-  warning: The larger the number the more memory Telemetry Grapher will use.
-    Eventually you will run out of memory!
-  parameters:
-    - name: Points
-      required: true
-      description: Number of points saved
-      values: \d+
-SECONDS_PLOTTED:
-  summary: Number of seconds plotted on each graph
-  parameters:
-    - name: Seconds
-      required: true
-      description: Number of seconds plotted
-      values: \d+
-POINTS_PLOTTED:
-  summary: Number of points plotted on each graph
-  warning: The larger the number the more performace is affected
-  parameters:
-    - name: Points
-      required: true
-      description: Number of points plotted per graph
-      values: \d+
-REFRESH_RATE_HZ:
-  summary: Telemetry Grapher refresh rate
-  parameters:
-    - name: Rate
-      required: true
-      description: Refresh rate in Hertz
-      values: '[0-9]*\.?[0-9]+'
-CTS_TIMEOUT:
-  summary: Timeout when trying to connect to the Server
-  parameters:
-    - name: Seconds
-      required: true
-      description: Timeout in seconds
-      values: '[0-9]*\.?[0-9]+'
-TAB:
-  summary: Create a new tab in the Telemetry Grapher GUI
-  parameters:
-    - name: Tab Text
-      required: false
-      description: Text to display on the tab
-      values: .*
-  modifiers:
-    PLOT:
-      summary: Create a new plot
-      parameters:
-        - name: Plot Type
-          required: true
-          description: Type of plot to create
-          values: ['LINEGRAPH', 'SINGLEXY', 'XY']
-      modifiers:
-        <%= MetaConfigParser.load('linegraph_plot.yaml').to_meta_config_yaml(8) %>
-        <%= MetaConfigParser.load('xy_plot.yaml').to_meta_config_yaml(8) %>
-        DATA_OBJECT:
-          modifiers:
-            COLOR:
-              summary: Color of the Data object
-              parameters:
-                - name: Color
-                  required: true
-                  description: Line color to draw the Data Object
-                  values: <%= DataObject::COLOR_LIST %>
-            <%= MetaConfigParser.load('housekeeping_params.yaml').to_meta_config_yaml(12) %>
-            <%= MetaConfigParser.load('linegraph_params.yaml').to_meta_config_yaml(12) %>
-            <%= MetaConfigParser.load('xy_params.yaml').to_meta_config_yaml(12) %>
-          summary: Type of data object on the plot
-          parameters:
-            - name: Data Object Type
-              required: true
-              description: Describes how the telemetry item is stored.
-                Typically matches the Plot Type.
-              values: ['LINEGRAPH','HOUSEKEEPING','SINGLEXY','XY']