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

Improve documentation for MultigridTransfer::copy_to_mg #5104

Merged
merged 1 commit into from Sep 19, 2017

Conversation

masterleinad
Copy link
Member

Clarify that copy_to_mg only acts on active degrees of freedoms. The current documentation led to the assumption that this function would do similar things as restrict_add for the MultigridTransfer classes.

@@ -154,7 +154,9 @@ class MGLevelGlobalTransfer : public MGTransferBase<VectorType>

/**
* Transfer from a vector on the global grid to vectors defined on each of
* the levels separately, i.a. an @p MGVector.
* the levels separately, i.e. a @p MGVector, for the active degrees of
Copy link
Member

Choose a reason for hiding this comment

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

You can go further and say that in a globally refined mesh without renumbering, it is a one-to-one copy to the finest level vector.

@@ -154,7 +154,9 @@ class MGLevelGlobalTransfer : public MGTransferBase<VectorType>

/**
* Transfer from a vector on the global grid to vectors defined on each of
* the levels separately, i.a. an @p MGVector.
* the levels separately, i.e. a @p MGVector, for the active degrees of
Copy link
Member

Choose a reason for hiding this comment

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

What are you trying to say with MGVector? I don't think this exists as a type? Do you mean "multilevel vector"?

@masterleinad
Copy link
Member Author

@tjhei Here you go.

Copy link
Contributor

@davydden davydden left a comment

Choose a reason for hiding this comment

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

LGTM. @tjhei maybe we should add one of those 2D pictures you showed me that explains what copy_to_mg actually does w.r.t. each level and its dofs.

@tjhei
Copy link
Member

tjhei commented Sep 19, 2017

@tjhei maybe we should add one of those 2D pictures you showed me that explains what copy_to_mg actually does w.r.t. each level and its dofs.

Yes. I should also add that to the in-progress paper. See #5110.

@tjhei
Copy link
Member

tjhei commented Sep 19, 2017

Here you go.

typo in "untouched". Nitpicking: It only is a plain copy if you did not renumber the DoFs. (but I don't care if you want to fix this).

@masterleinad
Copy link
Member Author

Fixed the typo.

@tjhei tjhei merged commit 4a2ac69 into dealii:master Sep 19, 2017
@masterleinad masterleinad deleted the doc_copy_to_mg branch October 16, 2017 14:42
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.

None yet

3 participants