Added New Interactive Plasma Displaying Widget for Notebook Simulation

[DhruvSondhi]

This PR aims to add a new interactive widget that can display the plasma stratification value (t_rad & w) for a particular iteration 🚀 . Allows to access values of all the iterations generated when running the simulation.

Description

This is feature request from @marxwillia, about the ability to see all the iteration values that were generated when running the simulation. Allows to infer the t_rad as well as w values.

Motivation and context

If the logger is set to log nothing, then the information cannot be inferred correctly. This widget aims to provide a way to access this without any changes to the code 😉

Screenshot

Wiget shows all the values for a particular iteration:

Wiget allows to select any iteration from the list & hence disply's value:

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.

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

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

[DhruvSondhi]

We need to figure out how to display the widget on the notebook. display() doesn't seem to be the way to go but it works never the less. I will try to find an alternative way for the same 😄

[DhruvSondhi]

Yes @andrewfullard , the # from tardis.simulation import Simulation part is important because I am actually using the create_table_widget() function present in the Util.py file. Because of this, it has circular imports. To address this situation, we need to remove this import or have it structured some other way.

[codecov]

Codecov Report

Merging #1640 (456f3ac) into master (575002c) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1640      +/-   ##
==========================================
+ Coverage   58.42%   58.45%   +0.03%     
==========================================
  Files          66       66              
  Lines        6684     6706      +22     
==========================================
+ Hits         3905     3920      +15     
- Misses       2779     2786       +7     

Impacted Files	Coverage Δ
tardis/tardis/simulation/base.py	81.85% <0.00%> (-1.40%)	⬇️

---

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 575002c...456f3ac. Read the comment docs.

[andrewfullard]

Converting to draft for now.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB