New Use Case: Space-time cross-spectra for S2S forecasts

[mgehne]

Replace italics below with details for this issue.

Describe the New Use Case

Compute and plot space-time cross-spectra for S2S forecasts

Use Case Name and Category

UserScript_fcstS2S_obsERAI_CrossSpectra.conf
category: s2s

Input Data

Input files are netcdf format for precipitation and zonal wind at 850hPa and 200hPa:
35M prate_avg_ufs_p5_2014040100.nc - UFS prototype 5 6-hourly average precipitation rate
35M prate_avg_ufs_p7_2014040100.nc - UFS prototype 7 6-hourly average precipitation rate
546M precip.erai.sfc.1p0.2x.2014-2016.nc - ERA Interim 6-hourly average precipitation rate
36M u200_ufs_p5_2014040100.nc - UFS prototype 5 6-hourly zonal wind at 200hPa
36M u200_ufs_p7_2014040100.nc - UFS prototype 7 6-hourly zonal wind at 200hPa
36M u850_ufs_p5_2014040100.nc - UFS prototype 5 6-hourly zonal wind at 850hPa
36M u850_ufs_p7_2014040100.nc - UFS prototype 7 6-hourly zonal wind at 850hPa
total input size: 760MB

Acceptance Testing

Describe tests required for new functionality.
As use case develops, provide a run time here
Run without error and output spectra netcdf files and plots

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.
About 3 days

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.
• Make a single user script for computing and plotting spectra. use configuration sections to add the ability to turn off one of these

Relevant Deadlines

List relevant project deadlines here or state NONE.
Projects ends 7/31. Plan to wrap up this Use Case addition by 5/31.

Funding Source

2785051

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)
• Select privacy

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

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

New Use Case 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.
• Add any new Python packages to the METplus Components Python Requirements table.
• 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) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept your changes. Merge branch into develop.
• Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
• Delete your fork or branch.
• Close this issue.