Tutorial: Create a new MET wire diagram that grays out non-used tools and if possible, find a way to animate the diagram

[j-opatz]

Describe the Task

While the wire diagram is overwhelmingly seen as helpful, it can be daunting to a new user. If we can “eliminate” the unused tools for each session by graying them out, it should help users better visualize what will be used without distractions. This could be taken to another level if the wire diagram is made into a short clip that transitions from the full wire diagram (to show context within and complexity of the entire system) to just the path(s) the session will use (to make it easier to understand for beginners).

Time Estimate

1-2 days

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

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE 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, 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) and Linked 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 and merge your changes.
• Delete your fork or branch.
• Close this issue.

[j-opatz]

The latest image of the MET wire diagram is attached

[briannen]

Here is a rough attempt at making a clearer wire diagram for session 4 of the tutorial (in PowerPoint).