Skip to content

Enhance Stat-Analysis to write the GO Index and CBS Index into a new SSIDX STAT line type. #1788

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

This enhancement is recommended for the DTCenter Air Force LIS project. The Stat-Analysis tool supports the skill score index and GO index job types. The GO Index is just a special version of the skill score index job. As of MET version 10.0.0, Stat-Analysis simply prints the output for this job to the screen or to an output file. This task is to create a new .stat line type to store the relevant output.

Still need to decide exactly what columns should be written to this new line type. Could be as little as the final score, or as complex, as the individual scores/weights for each component. So this may end up being a fixed number of columns or variable length and based on the number of user-defined components in the configurable Skill Score index.

Be sure to define related issues for METdatadb and METviewer, as noted below.

Time Estimate

3 days.

Sub-Issues

Consider breaking the enhancement down into sub-issues.
No sub-issues, but this work will also satisfy a related GitHub issue: #1031

Relevant Deadlines

October 2021

Funding Source

2712221

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: John HG
  • Select scientist(s) or no scientist required: Michelle and/or Tara

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
  • Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

Enhancement Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s), Project(s), Milestone, and Linked issues
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions