Restructure the "Conf interval" dropdown list

[TatianaBurek]

Describe the Task

*Reorganize "Conf interval" dropdown list. New "Conf interval" options:
std -the same
norm - rename to met_prm (MET parametric CIs). Use _ncl and _ncu columns, generated by MET. Display ONLY for if there is data for the single point - 1 data row for a point. Log a warning message otherwise - "No CIs has been displays because there is more then one data value found"
boot - the same. Consider using different column name for CIs calculated during the bootstrap to differentiate from other methods. For example, _btcl and _btcu
brier - remove
met_boot - Use _bcl and _bcu columns, generated by MET. Display ONLY for if there is data for the single point - 1 data row for a point. Log a warning message otherwise - "No CIs has been displays because there is more then one data value found"
Linked issues:
dtcenter/METviewer#255
dtcenter/METcalcpy#79
*

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 4h of work.

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

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.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

Task 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.