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

DPW visualization #74

Merged
merged 2 commits into from
Oct 23, 2020
Merged

DPW visualization #74

merged 2 commits into from
Oct 23, 2020

Conversation

lassepe
Copy link
Member

@lassepe lassepe commented Oct 23, 2020

The D3tree visualization of the DPW includes duplicate state nodes even if check_repeat_state = true is passed. This is due to the fact that the visualization method uses tree.transitions even if tree.unique_transitions is available.

@lassepe
Copy link
Member Author

lassepe commented Oct 23, 2020

@zsunberg BTW: I would have expected that detect_repeat = true of D3Trees.jl takes care of this. So maybe there is another bug to fix.

@lassepe lassepe requested a review from zsunberg October 23, 2020 13:40
@codecov
Copy link

codecov bot commented Oct 23, 2020

Codecov Report

Merging #74 into master will increase coverage by 0.19%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
+ Coverage   83.68%   83.87%   +0.19%     
==========================================
  Files          11       11              
  Lines         423      428       +5     
==========================================
+ Hits          354      359       +5     
  Misses         69       69              
Impacted Files Coverage Δ
src/visualization.jl 96.70% <100.00%> (+0.19%) ⬆️

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 d336772...2a57ed9. Read the comment docs.

@zsunberg
Copy link
Member

@zsunberg BTW: I would have expected that detect_repeat = true of D3Trees.jl takes care of this. So maybe there is another bug to fix.

That option is just to keep the D3Tree constructor from getting into an infinite loop if there are cycles, so it is a slightly different concept from detecting whether two children are the same. I think we should allow people to display D3Trees with two child nodes that are the same if they want to for some reason. So we should not fix that.

Copy link
Member

@zsunberg zsunberg left a comment

Choose a reason for hiding this comment

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

Looks good - thanks!

@zsunberg zsunberg merged commit 4e35227 into master Oct 23, 2020
@zsunberg
Copy link
Member

@lassepe do you think we should tag a new bugfix version, or just let this live in master for a while

@lassepe
Copy link
Member Author

lassepe commented Oct 23, 2020

@lassepe do you think we should tag a new bugfix version, or just let this live in master for a while

I'm a fan of "tag early and often" but for me this is not urgent. I just came across this bug when using DPW-MCTS for a toy project.

@lassepe lassepe deleted the DPWVisualization branch October 23, 2020 20:50
@zsunberg
Copy link
Member

zsunberg commented Oct 24, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants