-
Notifications
You must be signed in to change notification settings - Fork 19
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
Added doc to MultiResolutionAnalysis.cpp #228
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #228 +/- ##
==========================================
+ Coverage 65.67% 65.70% +0.03%
==========================================
Files 185 185
Lines 10234 10232 -2
==========================================
+ Hits 6721 6723 +2
+ Misses 3513 3509 -4 ☔ View full report in Codecov by Sentry. |
|
* | ||
* @brief Contructs a MultiResolutionAnalysis object composed of computational domain (world) and a polynomial basis (Multiwavelets) from a pre-existing BoundingBox object | ||
* | ||
* @param[in] bb: BoundingBox object representing the computational domain |
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.
same here about adding the types to the parameter documentation
* @details Inequality operator for the MultiResolutionAnalysis class, returns true if both MRAs have the same polynomial basis represented by a BoundingBox object, computational domain (ScalingBasis object) and maximum depth (integer), and false otherwise. | ||
* Opposite of the == operator. | ||
* For more information about the meaning of equality for BoundingBox and ScalingBasis objets, see their respective classes. | ||
*/ | ||
template <int D> bool MultiResolutionAnalysis<D>::operator!=(const MultiResolutionAnalysis<D> &mra) const { |
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.
now that I see this, it seems duplicated... Usually either one implements operator==
or operator!=
in full then the other is simply return !(left == right)
@stigrj?
template <int D> bool MultiResolutionAnalysis<D>::operator==(const MultiResolutionAnalysis<D> &mra) const { | ||
if (this->basis != mra.basis) return false; | ||
if (this->world != mra.world) return false; | ||
if (this->maxDepth != mra.maxDepth) return false; | ||
return true; | ||
} | ||
|
||
/** @returns Boolean value |
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.
/** @returns Whether the two MRA objects are not equal.
* @brief TODO: Sets up the filters | ||
* | ||
* @details TBD | ||
* |
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.
you should fill these out.
@@ -117,6 +193,14 @@ template <int D> void MultiResolutionAnalysis<D>::setupFilter() { | |||
} | |||
} | |||
|
|||
/** @returns double (double-precision floating point number) |
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.
you should write down what the function returns, not its type. The type will be provided by doxygen.
* @details This function displays the attributes of the MRA in the using the Printer class. | ||
* By default, the Printer class writes all information in the output file, not the terminal. |
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.
this seems a copy-paste? Please check.
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.
left some comments to address
…o MultiResolutionAnalysis.rst
Thanks Roberto! Co-authored-by: Roberto Di Remigio Eikås <[email protected]>
Created a new branch fresh off the latest commit in the master in which I copied the doc I had written.
I had to do it because I mistakenly used "git add *" in the old one and that induced stupid errors.