-
Notifications
You must be signed in to change notification settings - Fork 41
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
Low-level API Poisson equation #71
Conversation
* Added that HEX_AXIS will create n-cubes * Fixed minor typo
Dev tutorials
0.15 Documentation comments still pending to be adapted.
…p#master * Updated Manifest, among other, to point to Gridap#master
Hi @fverdugo ... I went over all your comments in regards to this PR. See #71 (comment) for more details. I had the following issues:
|
Thanks! I'll take a look. |
Simply by adding an empty comment line between them. I.e., DomainStyle(Qₕ) == ReferenceDomain()
#
DomainStyle(Qₕ) == PhysicalDomain()
To simplify things (for us and for the reader), I would write the tutorial assuming that the reader will do it by executing the cells in the notebook (just like the other tutorials). If you need to show intermediate results, you can split the cells as commented above. I would recommend to use a debugger just as an optional step.
I have never seen this error, but by looking at the implementation of It should be
The issue about spurious memory allocation still has to be further investigated... |
Hi @amartinhuertas! please find my replay to your last questions above ☝️ |
Regarding the bug in |
trying to address without success
Rewrote the first passages taking into account the following remark " To simplify things (for us and for the reader), I would write the tutorial assuming that the reader will do it by executing the cells in the notebook (just like the other tutorials). "
corresponding to Gridap.jl git repo #master branch so that we have access to the following bug-fix: gridap/Gridap.jl#563
Ok, I do not know why, but I though this was a dirty hack, and I was expecting a more sophisticated solution (e.g., an special markdown tag). I already followed this approach in 83f986d.
Yes. it should be stdout. I am now leveraging your bug-fix in this branch. Let us see whether this solves the problem.
Yes, but apart from this, there are still two additional comments without solution yet. |
This solves the issue in the tutorials CI ! Great! |
The definition of
This is just a minor comment. |
Ok ... so the pull request can be accepted, right? |
By looking at the Manifest, it seems that this PR relies on an unregistered version of Gridap. I'd wait until we release Gridap 0.15.3 with the patch related to the print_op_tree and change the Manifest here accordingly. |
Yeah, true. I should remove the Manifest.toml from the github repo.
Ok. Let us wait until then. Are we waiting for a particular event in order to release Gridap 0.15.3? If not, I can help to prepare this new release. |
Perfect if you can release this! The only part missing is to add a couple of entries in the NEWS.md related with the last PRs, move to 0.15.3 in the Project.toml, check that all tests pass and release. See also https://github.com/gridap/Gridap.jl/wiki/How-to-register-a-julia-package#specific-steps-to-registering-gridap |
Looking at the PRs accepted since the last release (0.15.2), I see (ordered by PR id, not chronologically): #553, #555, #556, #559, #563, #564. If this is the case, we should add 6 entries to the NEWS.md file (not actually a couple), right? On the other hand ... are all these minor release patches? |
Yes, sorry. We usually only include the most relevant changes in NEWS.md, it is not needed to include all PRs. In this case, I would mention that 1) we have fixed a bug in print_op_tree and 2) that the cell map in meshes of linear simplices is now an array of affine maps, which allows one to compute laplacians of the shape functions among other things. |
Ok, thanks! PR requested in gridap/Gridap.jl#566 |
@fverdugo ... all tests passed with Gridap 0.15.3 (new release). I think the PR is ready to merge. |
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.
A couple of minor comments and we are ready to go!
.vscode/launch.json
Outdated
@@ -0,0 +1,17 @@ | |||
{ |
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.
Perhaps we can add this file to .gitignore
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.
It was already in .gitignore. Possible added accidentally into the repository before was in gitignore. I have removed the file.
@@ -15,7 +16,6 @@ Printf = "de0858da-6303-5e67-8744-51eddeeeb8d7" | |||
Random = "9a3f8284-a2c9-5f02-9a11-845980a1fd5c" | |||
|
|||
[compat] | |||
Gridap = "0.15" |
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.
Please, do not remove Gridap from the compat section. Use Gridap 0.15.3 since this is the version that has the bugfix we need.
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.
Ok, Added. But I was not aware that I had removed it ... perhaps it was the package manager automatically or something like that?
Hi @amartinhuertas. Thanks for the changes. Just a question, what is |
I dont think so. Removed. You have 100 eyes! |
Hi @fverdugo, @santiagobadia,
after some final touches (see issue #60 for more details), I think the Low-Level tutorial is ready to merge!
The only thing which is missing is the following observation:
https://github.com/gridap/Tutorials/blob/dev-tutorials/src/poisson_dev_fe.jl#L368
for which I do not have an answer yet. We can leave it there, remove it, or try to find the reason, answer and solve it if necessary.
What do you think?