cosmos 4.5.0 → 5.0.2.pre.beta2

data/data/config/screen.yaml

@@ -33,8 +33,7 @@ GLOBAL_SETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet values.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -67,8 +66,7 @@ GLOBAL_SUBSETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet values.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -85,8 +83,7 @@ SETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet values.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -114,8 +111,7 @@ SUBSETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -146,8 +142,6 @@ NAMED_WIDGET:
       required: true
       description: The unique parameters for the given widget type
       values: .+
-STAY_ON_TOP:
-  summary: Force a screen to stay on top of all other windows
 # Even though these are technically SCREEN modifiers we load them at the top_frame
 # level so they appear as available keywords
 <%= MetaConfigParser.load('widgets.yaml').to_meta_config_yaml(0) %>

data/data/config/table_manager.yaml

@@ -49,21 +49,19 @@ TABLE:
       values: ['BIG_ENDIAN', 'LITTLE_ENDIAN']
     - name: Display
       requires: true
-      description: Indicates the table is a ONE_DIMENSIONAL table which is a two
-        column table consisting of unique rows, or a TWO_DIMENSIONAL table with
-        multiple columns and identical rows with unique values
+      description: Indicates the table contains KEY_VALUE rows (e.g. each row is unique),
+        or a ROW_COLUMN table with identical rows containing different values.
       values:
-        ONE_DIMENSIONAL:
-          summary: Declare a key value two column table with unique rows
+        KEY_VALUE:
+          summary: Table rows will be unique items (previously ONE_DIMENSIONAL, now deprecated)
           parameters:
             - name: Description
               requires: true
               description: Description of the table in quotes. The description is
                 used in mouseover popups and status line information.
               values: "['\"].*['\"]"
-        TWO_DIMENSIONAL:
-          summary: Declare a table with multiple columns and identical rows with
-            unique values
+        ROW_COLUMN:
+          summary: Table rows will be indentical with multiple columns (previously TWO_DIMENSIONAL, now deprecated)
           parameters:
             - name: Rows
               requires: true
@@ -80,4 +78,12 @@ SELECT_TABLE:
     - name: Table
       required: true
       description: The name of the existin table
-      values: .*
+      values: .*
+DEFAULT:
+  summary: Specify default values for a SINGLE row in a multi-column table.
+    If you have multiple rows you need a DEFAULT line for each row.
+    If all your rows are identical consider using ERB as shown in the COSMOS demo.
+  parameters:
+    - name: Default values
+      required: false
+      description: A STATE value or data value corresponding to the data type

data/data/config/target.yaml

@@ -1,92 +1,72 @@
 ---
-REQUIRE:
-  summary: Requires a Ruby file
-  description: Ruby files must be required to be available to call in other code.
-    Files are first required from the target's lib folder. If no file is found the
-    Ruby system path is checked which includes the base COSMOS/lib folder.
-  example: REQUIRE limits_response.rb
+TARGET:
+  summary: Defines a new target
+  example: TARGET INST
   parameters:
-    - name: Filename
+    - name: Folder Name
       required: true
-      description: Filename to require. For files in the target's lib directory
-        simply supply the filename, e.g. "REQUIRE my_file". Files in the base COSMOS
-        lib directory also should just list the filename. If a file is in a folder
-        under the lib directory then you must specify the folder name, e.g. "REQUIRE
-        folder/my_file". The filename can also be an absolute path but this is not
-        common. Note the ".rb" extension is optional when specifying the filename.
-      values: .+
-IGNORE_PARAMETER:
-  summary: Ignore the given command parameter
-  description: Hint to other COSMOS tools to hide or ignore this command parameter
-    when processing the command. For example, Command Sender and Command Sequence
-    will not display the parameter (by default) when showing the command and Script
-    Runner code completion will not display the parameter.
-  example: IGNORE_PARAMETER CCSDS_VERSION
-  parameters:
-    - name: Parameter Name
-      required: true
-      description: The name of a command parameter. Note that this parameter will
-        be ignored in ALL the commands it appears in.
-      values: .+
-IGNORE_ITEM:
-  summary: Ignore the given telemetry item
-  description: Hint to other COSMOS tools to hide or ignore this telemetry item
-    when processing the telemetry. For example, Packet Viewer will not display the
-    item (by default) when showing the packet.
-  example: IGNORE_ITEM CCSDS_VERSION
-  parameters:
-    - name: Item name
-      required: true
-      description: The name of a telemetry item. Note that this item will be ignored
-        in ALL the telemetry it appears in.
-      values: .+
-COMMANDS:
-  summary: Process the given command definition file
-  description: This keyword is used to explicitly add the command definition file
-    to the list of command and telemetry files to process.
-  warning: Usage of this keyword overrides automatic command and telemetry file
-    discovery. If this keyword is used, you must also use the TELEMETRY keyword
-    to specify the telemetry files to process.
-  example: |
-    COMMANDS inst_cmds_v2.txt
-    TELEMETRY inst_tlm_v2.txt
-  parameters:
-    - name: Filename
-      required: true
-      description: Name of a command definition file in the target's cmd_tlm directory, e.g. "cmd.txt".
-      values: '.*\.txt'
-TELEMETRY:
-  summary: Process the given telemetry definition file
-  description: This keyword is used to explicitly add the telemetry definition
-    file to the list of command and telemetry files to process.
-  warning: Usage of this keyword overrides automatic command and telemetry file
-    discovery. If this keyword is used, you must also use the COMMAND keyword to
-    specify the command files to process.
-  example: |
-    COMMANDS inst_cmds_v2.txt
-    TELEMETRY inst_tlm_v2.txt
-  parameters:
-    - name: Filename
+      description: The target folder
+      values: .*
+    - name: Name
       required: true
-      description: Name of a telemetry definition file in the target's cmd_tlm
-        directory, e.g. "tlm.txt".
-      values: '.*\.txt'
-AUTO_SCREEN_SUBSTITUTE:
-  summary: Automatically substitute the target's name in screen definitions
-  description: Targets can be renamed when they are declared which would break
-    any screen definitions using the explicit target name. This keyword automatically
-    replaces the target name in the screen definitions with the actual target name.
-  warning: Replaces ALL target names in a screen definition file, so this is not
-    suitable for screens with multiple targets.
-CMD_UNIQUE_ID_MODE:
-  summary: Flags that commands to this target are identified in a mixed variety of ways
-  description: Ideally all commands for a target are identified using the exact same fields in a header
-    for each command.  If  this target identifies packets using different fields for some commands than others,
-    then this flag must be set to force a brute force identification method.
-  warning: Using this mode significantly slows packet identification
-TLM_UNIQUE_ID_MODE:
-  summary: Flags that telemetry to this target are identified in a mixed variety of ways
-  description: Ideally all telemetry for a target are identified using the exact same fields in a header
-    for each packet.  If  this target identifies packets using different fields for some telemetry packets than others,
-    then this flag must be set to force a brute force identification method.
-  warning: Using this mode significantly slows packet identification
+      description:
+        The target name. While this is almost always the same as Folder Name
+        it can be different to create multiple targets based on the same target folder.
+      values: .*
+  modifiers:
+    CMD_LOG_CYCLE_TIME:
+      summary: Command binary logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    CMD_LOG_CYCLE_SIZE:
+      summary: Command binary logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+
+    CMD_DECOM_LOG_CYCLE_TIME:
+      summary: Command decommutation logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    CMD_DECOM_LOG_CYCLE_SIZE:
+      summary: Command decommutation logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+
+    TLM_LOG_CYCLE_TIME:
+      summary: Telemetry binary logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    TLM_LOG_CYCLE_SIZE:
+      summary: Telemetry binary logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+
+    TLM_DECOM_LOG_CYCLE_TIME:
+      summary: Telemetry decommutation logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    TLM_DECOM_LOG_CYCLE_SIZE:
+      summary: Telemetry decommutation logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+

data/data/config/target_config.yaml

@@ -0,0 +1,94 @@
+---
+REQUIRE:
+  summary: Requires a Ruby file
+  description:
+    Ruby files must be required to be available to call in other code.
+    Files are first required from the target's lib folder. If no file is found the
+    Ruby system path is checked which includes the base COSMOS/lib folder.
+  example: REQUIRE limits_response.rb
+  parameters:
+    - name: Filename
+      required: true
+      description: Filename to require. For files in the target's lib directory
+        simply supply the filename, e.g. "REQUIRE my_file". Files in the base COSMOS
+        lib directory also should just list the filename. If a file is in a folder
+        under the lib directory then you must specify the folder name, e.g. "REQUIRE
+        folder/my_file". The filename can also be an absolute path but this is not
+        common. Note the ".rb" extension is optional when specifying the filename.
+      values: .+
+IGNORE_PARAMETER:
+  summary: Ignore the given command parameter
+  description:
+    Hint to other COSMOS tools to hide or ignore this command parameter
+    when processing the command. For example, Command Sender and Command Sequence
+    will not display the parameter (by default) when showing the command and Script
+    Runner code completion will not display the parameter.
+  example: IGNORE_PARAMETER CCSDS_VERSION
+  parameters:
+    - name: Parameter Name
+      required: true
+      description:
+        The name of a command parameter. Note that this parameter will
+        be ignored in ALL the commands it appears in.
+      values: .+
+IGNORE_ITEM:
+  summary: Ignore the given telemetry item
+  description: Hint to other COSMOS tools to hide or ignore this telemetry item
+    when processing the telemetry. For example, Packet Viewer will not display the
+    item (by default) when showing the packet.
+  example: IGNORE_ITEM CCSDS_VERSION
+  parameters:
+    - name: Item name
+      required: true
+      description:
+        The name of a telemetry item. Note that this item will be ignored
+        in ALL the telemetry it appears in.
+      values: .+
+COMMANDS:
+  summary: Process the given command definition file
+  description:
+    This keyword is used to explicitly add the command definition file
+    to the list of command and telemetry files to process.
+  warning: Usage of this keyword overrides automatic command and telemetry file
+    discovery. If this keyword is used, you must also use the TELEMETRY keyword
+    to specify the telemetry files to process.
+  example: |
+    COMMANDS inst_cmds_v2.txt
+    TELEMETRY inst_tlm_v2.txt
+  parameters:
+    - name: Filename
+      required: true
+      description: Name of a command definition file in the target's cmd_tlm directory, e.g. "cmd.txt".
+      values: '.*\.txt'
+TELEMETRY:
+  summary: Process the given telemetry definition file
+  description: This keyword is used to explicitly add the telemetry definition
+    file to the list of command and telemetry files to process.
+  warning: Usage of this keyword overrides automatic command and telemetry file
+    discovery. If this keyword is used, you must also use the COMMAND keyword to
+    specify the command files to process.
+  example: |
+    COMMANDS inst_cmds_v2.txt
+    TELEMETRY inst_tlm_v2.txt
+  parameters:
+    - name: Filename
+      required: true
+      description: Name of a telemetry definition file in the target's cmd_tlm
+        directory, e.g. "tlm.txt".
+      values: '.*\.txt'
+CMD_UNIQUE_ID_MODE:
+  summary: Command packet identifiers don't all share the same bit offset, size, and type
+  description:
+    Ideally all commands for a target are identified using the exact same bit offset, size,
+    and type field in each command. If ANY command identifiers differ then this flag must be set
+    to force a brute force identification method.
+  warning: Using this mode significantly slows packet identification
+  since: 4.4.0
+TLM_UNIQUE_ID_MODE:
+  summary: Telemetry packets identifiers don't all share the same bit offset, size, and type
+  description:
+    Ideally all telemetry for a target are identified using the exact same bit offset, size,
+    and type field in each packet. If ANY telemetry identifiers differ then this flag must be set
+    to force a brute force identification method.
+  warning: Using this mode significantly slows packet identification
+  since: 4.4.0

data/data/config/telemetry.yaml

@@ -1,5 +1,7 @@
 ---
 TELEMETRY:
+  # Prevent prettier from removing the newline after modifiers:
+  # prettier-ignore
   modifiers:
     <%= MetaConfigParser.load('telemetry_modifiers.yaml').to_meta_config_yaml(4) %>
   summary: Defines a new telemetry packet
@@ -8,39 +10,43 @@ TELEMETRY:
     - name: Target
       required: true
       description: Name of the target this telemetry packet is associated with
-      values: <%= System.targets.keys %>
+      values: .+
     - name: Command
       required: true
-      description: Name of this telemetry packet. Also referred to as its mnemonic.
+      description:
+        Name of this telemetry packet. Also referred to as its mnemonic.
         Must be unique to telemetry packets in this target. Ideally will be as short and clear as possible.
       values: \D\S*
     - name: Endianness
       required: true
       description: Indicates if the data in this packet is in Big Endian or Little Endian format
-      values: ['BIG_ENDIAN', 'LITTLE_ENDIAN']
+      values: ["BIG_ENDIAN", "LITTLE_ENDIAN"]
     - name: Description
       required: false
       description: Description of this telemetry packet which must be enclosed with quotes
-      values: "['\"].*['\"]"
+      values: '[''"].*[''"]'
 SELECT_TELEMETRY:
+  # prettier-ignore
   modifiers:
     <%= MetaConfigParser.load('telemetry_modifiers.yaml').to_meta_config_yaml(4) %>
   summary: Selects an existing telemetry packet for editing
-  description: Typically used in a separate configuration file from where the original
+  description:
+    Typically used in a separate configuration file from where the original
     telemetry is defined to override or add to the existing telemetry definition
   example: SELECT_TELEMETRY SYSTEM LIMITS_CHANGE
   parameters:
     - name: Target Name
       required: true
       description: Name of the target this telemetry packet is associated with
-      values: <%= System.targets.keys %>
+      values: .+
     - name: Command Name
       required: true
       description: Name of the telemetry packet to select
       values: .+
 LIMITS_GROUP:
   summary: Defines a group of related limits Items
-  description: Limits groups contain telemetry items that can be enabled and disabled together.
+  description:
+    Limits groups contain telemetry items that can be enabled and disabled together.
     It can be used to group related limits as a subsystem that can be enabled or disabled
     as that particular subsystem is powered (for example). To enable a group call the
     enable_limits_group("NAME") method in Script Runner. To disable a group call the
@@ -55,7 +61,8 @@ LIMITS_GROUP:
       values: .+
 LIMITS_GROUP_ITEM:
   summary: Adds the specified telemetry item to the last defined LIMITS_GROUP
-  description: Limits group information is typically kept in a separate configuration
+  description:
+    Limits group information is typically kept in a separate configuration
     file in the config/TARGET/cmd_tlm folder named limits_groups.txt. If you want to
     configure multiple target items in a particular group you should put this information
     in the config/SYSTEM/cmd_tlm/limits_groups.txt file. The SYSTEM target is processed
@@ -69,7 +76,7 @@ LIMITS_GROUP_ITEM:
     - name: Target Name
       required: true
       description: Name of the target
-      values: <%= System.targets.keys %>
+      values: .+
     - name: Packet Name
       required: true
       description: Name of the packet

data/data/config/tool.yaml

@@ -0,0 +1,57 @@
+---
+TOOL:
+  summary: Defines a new tool
+  example: TOOL DEMO Demo
+  parameters:
+    - name: Folder Name
+      required: true
+      description: The folder where the tool is located relative to the tools folder in the plugin
+      values: .*
+    - name: Name
+      required: true
+      description: The tool name displayed in the Nav bar
+      values: .*
+  modifiers:
+    URL:
+      summary: Url to reach the tool relative to the tools Folder Name, or absolute
+      parameters:
+        - name: URL
+          required: true
+          description: URL
+          values: .*
+    INLINE_URL:
+      summary: Single SPA url to reach the tool
+      example: js/app.js
+      parameters:
+        - name: URL
+          required: true
+          description: URL
+          values: .*
+    ICON:
+      summary: Icon used to display the tool link
+      parameters:
+        - name: Name
+          required: true
+          description: Material design icon name (https://materialdesignicons.com/)
+          values: .*
+    WINDOW:
+      summary: How the tool should be displayed
+      parameters:
+        - name: Mode
+          required: true
+          description: Tool display mode
+          values: ["INLINE", "IFRAME", "NEW"]
+    CATEGORY:
+      summary: Category to place the tool into
+      parameters:
+        - name: Category
+          required: true
+          description: Name of a category to organize a tool into
+          values: .*
+    SHOWN:
+      summary: Is the Tool Shown in the Nav Bar
+      parameters:
+        - name: Shown
+          required: true
+          description: Is Shown?
+          values: ["true", "false"]