Got it. Thank you for your explanation!
Best wishes,
Zongze
On Mon, 15 May 2023 at 23:28, Matthew Knepley wrote:
> On Mon, May 15, 2023 at 9:55 AM Zongze Yang wrote:
>
>> On Mon, 15 May 2023 at 17:24, Matthew Knepley wrote:
>>
>>> On Sun, May 14, 2023 at 7:23 PM Zongze Yang
>>> wrote:
>>>
On Mon, May 15, 2023 at 9:55 AM Zongze Yang wrote:
> On Mon, 15 May 2023 at 17:24, Matthew Knepley wrote:
>
>> On Sun, May 14, 2023 at 7:23 PM Zongze Yang wrote:
>>
>>> Could you try to project the coordinates into the continuity space by
>>> enabling the option
>>>
On Mon, 15 May 2023 at 17:24, Matthew Knepley wrote:
> On Sun, May 14, 2023 at 7:23 PM Zongze Yang wrote:
>
>> Could you try to project the coordinates into the continuity space by
>> enabling the option
>> `-dm_plex_gmsh_project_petscdualspace_lagrange_continuity true`?
>>
>
> There is a
On Sun, May 14, 2023 at 7:23 PM Zongze Yang wrote:
> Could you try to project the coordinates into the continuity space by
> enabling the option
> `-dm_plex_gmsh_project_petscdualspace_lagrange_continuity true`?
>
There is a comment in the code about that:
/* XXX FIXME Requires
Could you try to project the coordinates into the continuity space by
enabling the option
`-dm_plex_gmsh_project_petscdualspace_lagrange_continuity true`?
Best wishes,
Zongze
On Mon, 15 May 2023 at 04:24, Matthew Knepley wrote:
> On Sun, May 14, 2023 at 12:27 PM Zongze Yang wrote:
>
>>
>>
>>
On Sun, May 14, 2023 at 12:27 PM Zongze Yang wrote:
>
>
>
> On Sun, 14 May 2023 at 23:54, Matthew Knepley wrote:
>
>> On Sun, May 14, 2023 at 9:21 AM Zongze Yang wrote:
>>
>>> Hi, Matt,
>>>
>>> The issue has been resolved while testing on the latest version of
>>> PETSc. It seems that the
On Sun, 14 May 2023 at 23:54, Matthew Knepley wrote:
> On Sun, May 14, 2023 at 9:21 AM Zongze Yang wrote:
>
>> Hi, Matt,
>>
>> The issue has been resolved while testing on the latest version of PETSc.
>> It seems that the problem has been fixed in the following merge request:
>>
On Sun, May 14, 2023 at 9:21 AM Zongze Yang wrote:
> Hi, Matt,
>
> The issue has been resolved while testing on the latest version of PETSc.
> It seems that the problem has been fixed in the following merge request:
> https://gitlab.com/petsc/petsc/-/merge_requests/5970
>
No problem. Glad it is
Yes, you are correct. I have conducted tests using high-order 3D meshes of
a unit cube, and regrettably, the tests have failed. I have attached the
files for your reference.
Kindly review the output provided below: ( The volume should be 1)
```
$ mpiexec -n 3 ./ex33 -coord_space 0
Good to hear this works for you. I believe there is still a problem with high
order tetrahedral elements (we've been coping with it for months and someone
asked last week) and plan to look at it as soon as possible now that my
semester finished.
Zongze Yang writes:
> Hi, Matt,
>
> The issue
Hi, Matt,
The issue has been resolved while testing on the latest version of PETSc.
It seems that the problem has been fixed in the following merge request:
https://gitlab.com/petsc/petsc/-/merge_requests/5970
I sincerely apologize for any inconvenience caused by my previous message.
However, I
On Sat, May 13, 2023 at 6:08 AM Zongze Yang wrote:
> Hi, Matt,
>
> There seem to be ongoing issues with projecting high-order coordinates
> from a gmsh file to other spaces. I would like to inquire whether there are
> any plans to resolve this problem.
>
> Thank you for your attention to this
Hi, Matt,
There seem to be ongoing issues with projecting high-order coordinates from
a gmsh file to other spaces. I would like to inquire whether there are any
plans to resolve this problem.
Thank you for your attention to this matter.
Best wishes,
Zongze
On Sat, 18 Jun 2022 at 20:31, Zongze
Thank you for your reply. May I ask for some references on the order of the
dofs on PETSc's FE Space (especially high order elements)?
Thanks,
Zongze
Matthew Knepley 于2022年6月18日周六 20:02写道：
> On Sat, Jun 18, 2022 at 2:16 AM Zongze Yang wrote:
>
>> In order to check if I made mistakes in the
On Sat, Jun 18, 2022 at 2:16 AM Zongze Yang wrote:
> In order to check if I made mistakes in the python code, I try to use c
> code to show the issue on DMProjectCoordinates. The code and mesh file is
> attached.
> If the code is correct, there must be something wrong with
>
I tried the projection operation. However, it seems that the projection
gives the wrong solution. After projection, the bounding box is changed!
See logs below.
First, I patch the petsc4py by adding `DMProjectCoordinates`:
```
diff --git a/src/binding/petsc4py/src/PETSc/DM.pyx
On Thu, Jun 16, 2022 at 12:06 PM Zongze Yang wrote:
>
>
> 在 2022年6月16日，23:22，Matthew Knepley 写道：
>
>
> On Thu, Jun 16, 2022 at 11:11 AM Zongze Yang wrote:
>
>> Hi, if I load a `gmsh` file with second-order elements, the coordinates
>> will be stored in a DG-P2 space. After obtaining the
> 在 2022年6月16日，23:22，Matthew Knepley 写道：
>
>
>> On Thu, Jun 16, 2022 at 11:11 AM Zongze Yang wrote:
>
>> Hi, if I load a `gmsh` file with second-order elements, the coordinates will
>> be stored in a DG-P2 space. After obtaining the coordinates of a cell, how
>> can I map the coordinates
On Thu, Jun 16, 2022 at 11:11 AM Zongze Yang wrote:
> Hi, if I load a `gmsh` file with second-order elements, the coordinates
> will be stored in a DG-P2 space. After obtaining the coordinates of a cell,
> how can I map the coordinates to vertex and edge?
>
By default, they are stored as P2,
19 matches
Mail list logo
