Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling virtual_packet_logging by default in the visualization folder #1693

Merged
merged 2 commits into from
Aug 19, 2021

Conversation

atharva-2001
Copy link
Member

This PR removes the symbolic link to tardis_example.yml in the visualization folder, and adds it with virtual_packet_logging enabled.

Description

To build the SDEC plot and the Line Info widget, one needs to enable virtual_packet_logging from the run_tardis function or edit the tardis_example.yml file in the docs folder. This enables virtual_packet_logging by default just for the visualization folder, easing the process for the user.

Motivation and context

#1665 (review)

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
Copy link
Contributor

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.

1 similar comment
@tardis-bot
Copy link
Contributor

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.

@codecov
Copy link

codecov bot commented Jul 7, 2021

Codecov Report

Merging #1693 (4c5b405) into master (2c47baa) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1693   +/-   ##
=======================================
  Coverage   61.88%   61.88%           
=======================================
  Files          63       63           
  Lines        5851     5851           
=======================================
  Hits         3621     3621           
  Misses       2230     2230           

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 2c47baa...4c5b405. Read the comment docs.

@isaacgsmith
Copy link
Member

Because of how we do things with symlinks, I think you should either:

  • rename that file to something else besides tardis_example.yml

  • add virtual packet logging to docs/tardis_example.yml and keep the file in docs/io/visualization as a symlink

@MarkMageeAstro
Copy link
Contributor

We can probably change to something like tardis_example_SDEC? I guess this would also mean some notebooks need updated too

Copy link
Contributor

@MarkMageeAstro MarkMageeAstro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See previous comment...

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@atharva-2001 atharva-2001 force-pushed the sdec_vpl_file branch 2 times, most recently from f551356 to de8244f Compare July 8, 2021 05:48
@yuyizheng1112
Copy link
Contributor

just a suggestion: I used to add virtual_packet_logging option to run_tardis() function (see this pr). It seems that few people know this... Maybe you can set this option to True instead of adding new file.

@atharva-2001
Copy link
Member Author

That sounds good to me too, maybe we could just set virtual_packet_logging to True in both notebooks in #1665?

Copy link
Member

@jaladh-singhal jaladh-singhal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think instead of adding new file, enabling virtual packet logging in run_tardis call will be better as suggested by @yuyizheng1112 .

And if you want to keep the new config file, name it as tardis_example_virt_logging.yml instead since it's not only for SDEC but also for Line info widget.

@andrewfullard
Copy link
Contributor

Is this PR still relevant?

@andrewfullard andrewfullard merged commit 0275b71 into tardis-sn:master Aug 19, 2021
DhruvSondhi pushed a commit to DhruvSondhi/tardis that referenced this pull request Aug 21, 2021
tardis-sn#1693)

* set virtual_packet_logging to True in notebooks

* [build docs]
DhruvSondhi pushed a commit to DhruvSondhi/tardis that referenced this pull request Aug 21, 2021
tardis-sn#1693)

* set virtual_packet_logging to True in notebooks

* [build docs]
atharva-2001 added a commit to atharva-2001/tardis that referenced this pull request Oct 1, 2021
tardis-sn#1693)

* set virtual_packet_logging to True in notebooks

* [build docs]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants