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

Optionally return graph object from cello_probs #22

Merged
merged 1 commit into from
May 18, 2022
Merged

Optionally return graph object from cello_probs #22

merged 1 commit into from
May 18, 2022

Conversation

LustigePerson
Copy link
Contributor

First of all, thank you for your great tool.
This PR adds the possibility to let cello_probs optionally return the graph object. The parameter return_graph is used for this. This is by default Falseand therefore does not change the original behavior. If it is set to True the graph is returned as the third object in addition to fig and ax.

The background is that I would like to save the graph object in a different format, as well as recolor it if necessary. Also it allows to output all terminal nodes easily, for example.

Copy link
Member

@mbernste mbernste left a comment

Choose a reason for hiding this comment

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

Thank you very much for adding this feature!

@mbernste mbernste merged commit 77d33e9 into deweylab:master May 18, 2022
@LustigePerson
Copy link
Contributor Author

Thanks for merging @mbernste.

What is the cello policy for new releases, so that this and the bugfix before come to life on pypi and can be easily managed in conda environments?

@mbernste
Copy link
Member

Hi, there's no strict policy for new releases, it is mostly just me maintaining CellO. I have incorporated this bug fix into the latest release (v2.0.4), which has now been uploaded to PyPI.

@LustigePerson
Copy link
Contributor Author

Great! Thank you so much!

@LustigePerson LustigePerson deleted the return_graph branch May 31, 2022 09:27
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