Hello Ma’am/Sir,
Hope you doing well.
Have you any requirement in Translation or Interpretation?
We are an ISO certified and Crisil Rated Translation Company and we actually
deal with Multilingual Translation, Content writing, Interpretation and Content
Moderation Services.
We
On Thu, Feb 15, 2018 at 7:40 PM, Danyang Su wrote:
> Hi Matt,
>
> I have a question on DMPlexCreateFromCellList and DMPlexCreateFromFile.
> When use DMPlexCreateFromFile with Gmsh file input, it works fine and each
> processor gets its own part. However, when use
Oh! Thanks for your help! I am currently looking at the test examples. I would
definitely try your method. In the first impression, I thought it was
DMPlexDistribute() problem.
From: Matthew Knepley [mailto:knep...@gmail.com]
Sent: Friday, February 16, 2018 6:51 AM
To: Mohammad Hassan
On Thu, Feb 15, 2018 at 5:43 PM, Mohammad Hassan Baghaei <
mhbagh...@mail.sjtu.edu.cn> wrote:
> Hi Matt
>
> In fact, I created a routine for my specific mesh generation. I firstly,
> create the DMPlex object at first, then setting the chart, then doing
> symmetrize and interpolate. Next, I
Hi Matt
In fact, I created a routine for my specific mesh generation. I firstly, create
the DMPlex object at first, then setting the chart, then doing symmetrize and
interpolate. Next, I created coordinate section and giving the coordinates.
After finishing giving the coordinates, I declare
On Thu, Feb 15, 2018 at 4:40 PM, Mohammad Hassan Baghaei <
mhbagh...@mail.sjtu.edu.cn> wrote:
> Hi
>
> I am using DMPlex as interface for mesh generation. On single core, I got
> around 3 mesh cells. Whenever, I run on multiple core, say 3, in the
> output file for DM, VTK, I got 3 times mesh
Hi
I am using DMPlex as interface for mesh generation. On single core, I got
around 3 mesh cells. Whenever, I run on multiple core, say 3, in the
output file for DM, VTK, I got 3 times mesh cell and point numbers. Does it
mean that DMPlexDistribute() does not work properly!
Thanks
Amir
HeeHo Park writes:
> Yes, this works.
>
> u = da.getVecArray(U)
> for i in range(mstart, mend):
> u[i] = np.sin(np.pi*i*6.*h) + 3.*np.sin(np.pi*i*2.*h)
>
> The code above also worked without restoreVecArray. I guess the u just
> points at the array U.
It won't be
Yes, this works.
u = da.getVecArray(U)
for i in range(mstart, mend):
u[i] = np.sin(np.pi*i*6.*h) + 3.*np.sin(np.pi*i*2.*h)
The code above also worked without restoreVecArray. I guess the u just
points at the array U.
I think your code is clearer to understand what is happening.
Thank
Hello Matt,
Le 15/02/2018 à 00:41, Matthew Knepley a écrit :
On Tue, Jan 23, 2018 at 11:14 AM, Yann Jobic > wrote:
Hello,
I'm trying to understand the numbering of quadrature points in
order to solve the FEM system, and how
Thanks again Barry. I figured it out. My SNESView was called before
SNESSetFromOptions and hence was showing the default value.
Regards,
Bikash
On Wed, Feb 14, 2018 at 11:28 PM, Smith, Barry F.
wrote:
>
> I stuck the line
>
> PetscOptionsSetValue(NULL,"-snes_qn_m",
11 matches
Mail list logo