PSTD statistics can't be plotted because n_thresh value is too big

[TatianaBurek]

Describe the Problem

I found a problem with the usage of PCT data in METviewer.
Please take a look at jattached job.
plot_20220304_143105.xml.txt

I plot PSTD_BASER using PCT Agg stat.
The reason that this job is unsuccessful - n_thresh value is too big : n_thresh=101.
When we retrieve the data from DB we create a query that joins n_thresh-number tables. In this case it is 101 tables.
MySQL (MariaDB) throws the error:
ERROR 1116 (HY000): Too many tables; MariaDB can only use 61 tables in a join
This means that we have to restrict n_thresh value or come up with better SQL query.

Expected Behavior

• Display an error message and detail explanation why the plot can't be created
  OR
• create a query that would not use table joins and create a plot
  OR
• use a simple query to just get the data from DB and move data reordering to Java or Python and create a plot

To Reproduce

Describe the steps to reproduce the behavior:
1. Use dakota
2. load attache XML
3. try to create a plot

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

• Select Organization level Project for support of the current coordinated release
• Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

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

Bugfix 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 main_<Version>.
  Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• Fix the bug 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 main_<Version>.
  Pull request: bugfix <Issue Number> main_<Version> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Linked issues
  Select: Organization level software support Project for the current coordinated release
  Select: Milestone as the next bugfix version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Complete the steps above to fix the bug on the develop branch.
  Branch name: bugfix_<Issue Number>_develop_<Description>
  Pull request: bugfix <Issue Number> develop <Description>
  Select: Reviewer(s) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.