-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add inline documentation for the DagMC and dagmcmetadata classes. #945
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
8b041b2
Adding documentation to DAGMC header. Needs review
pshriwise 04ba4c4
Corrections/updates to the documentation
pshriwise 72fd3f7
Updating/adding inline documentation for the metadata class
pshriwise 0d6fe7e
Applying style guide
pshriwise dabcd73
Updating changelog
pshriwise e8656f1
Remove redundant method signature line
pshriwise b485a43
Addressing comments in PR review
pshriwise 19b7faf
Adding docs for dagmcmetadata constructor and remove duplicat props
pshriwise d97c300
Apply suggestions from @ahnaf-tahmid-chowdhury
pshriwise eb30c20
Adding more information on private parse_ methods
pshriwise 3142099
Fix format
pshriwise bc6241a
Improvements to get_angle docs and other small updates.
pshriwise 9a74ad6
Style fixes
pshriwise File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it fair to say that this method is more robust? That is, should we provide some indication about when/why to use a slower method?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a sense that it is more robust, but am not terribly familiar (or am no longer terribly familiar) with it myself. Do you recall in what situations we should use it over the
point_in_volume
method? I'd be happy to add them if so.For now, I'll include where the method originates so a developer can make a decision based on the publication.