-
Notifications
You must be signed in to change notification settings - Fork 84
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
{find->get}_dofs in examples #776
Conversation
Comments on style welcome. Setting out a nice idiom is an important part of |
What's the right way to get all the boundary dofs as in scikit-fem/docs/examples/ex13.py Lines 43 to 47 in dea7871
Simple replacement of find with get looks wrong. I do get the correct answer with boundary_dofs = np.concatenate([basis.get_dofs(b) for b in mesh.boundaries]) but is that required? |
I interpret "all DOFs" to mean the set of all DOFs on the boundary of the domain which is boundary_dofs = basis.get_dofs("ground") | basis.get_dofs("positive") work? Another option would be to add support for boundary_dofs = basis.get_dofs(["ground", "positive"]) as suggested in #764. |
Added support for |
Right, i do mean union rather than concatenation. Either proposed syntax is good (union of get-dofs of str or get-dof of collection of str). I'll try that. |
O. K., thanks, yes, #778 is nice. i'll use that. Ta. |
I'll fix the bugs in #778 asap. |
Now it should be fixed but I'll wait for the tests to pass. |
This reverts commit d3b1787.
This just leaves ex36. scikit-fem/docs/examples/ex36.py Lines 163 to 180 in 9ee89ba
|
Alright, the last one is slightly complicated, let's see if I can do something about it. |
Here is something:
|
I'm pretty sure we can get rid of the |
Following merger of #775 as discussed in #764.