Updated widgets.py Changing all T's to temprature

[pokwer]

Description
Updated widgets.py Changing all T's to temprature

Motivation and context
solving issue #1600

How has this been tested?

• Testing pipeline.
• Other.

Examples

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[codecov]

Codecov Report

Merging #1675 (eab66bc) into master (c47a3df) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1675   +/-   ##
=======================================
  Coverage   61.89%   61.89%           
=======================================
  Files          62       62           
  Lines        5732     5732           
=======================================
  Hits         3548     3548           
  Misses       2184     2184           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c47a3df...eab66bc. Read the comment docs.

[andrewfullard]

Thanks for your first contribution! It looks like I need to clarify my issue, because the T I meant was the variable, not the labels on plots. Furthermore, you misspelled Temperature in your contribution.

[pokwer]

Thanks for your first contribution! It looks like I need to clarify my issue, because the T I meant was the variable, not the labels on plots. Furthermore, you misspelled Temperature in your contribution.

can you tell me what files these variables are in so that I can change them?

[andrewfullard]

You should search the files to find them :)

[tardis-bot]

Before a pull request is accepted, it must meet the following criteria:

• Is the necessary information provided?
• Is this a duplicate PR?
  • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
  • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
• Does it pass existing tests and are new tests provided if required?
  • The test coverage should not decrease, and for new features should be close to 100%.
• Is the code tidy?
  • No unnecessary print lines or code comments.

[jaladh-singhal]

We no longer support tardis/gui since we now have tardis/visulaization/widgets for the same.

@andrewfullard should we close it?