On Thu, Jan 23, 2020 at 11:37 AM Guyer, Jonathan E. Dr. (Fed) via fipy
wrote:
>
> I'm not sure why you are skeptical. FiPy does not use VTK internally, so the
> fact that the FiPy mesh is defined appropriately for its own use has nothing
> to do with whether we export it correctly as VTK. It
.
From: A A
Sent: Thursday, January 23, 2020 6:10 AM
To: Guyer, Jonathan E. Dr. (Fed); FIPY
Subject: Re: Some questions on the viewer
Hi Jon,
It looks like pyvista does support VTK_CONVEX_POINT_SET. Please take a look at
the discussion I started on
https://github.com/pyvista
ll type intentional or important here? If so it
> might be worth convincing those libraries to add cell type 41 plotting and
> i/o capabilities.
> > -- Forwarded message -
> > From: A A
> > Date: Wed, Jan 22, 2020 at 12:22 PM
> > Subject: Re: Some
I've added comments to your https://github.com/usnistgov/fipy/issues/693, but
the short answer is that FiPy's not exporting a VTK cell type that pyvista
understands. FiPy should put out VTK_PIXELs or VTK_QUADs in this case.
> On Jan 22, 2020, at 6:22 AM, A A wrote:
>
> On another note, I've
Amine -
The n is effectively a power, or how many times the operator
$\nabla\cdot\Gamma\nabla$ should be applied. The index i runs from 1..n to
denote that each operator gets its own coefficient.
If n=1, then apply the operator $\nabla\cdot\Gamma_1\nabla$ to the argument
$\phi$ and you get
ing fipy's choice
> of cell type 41.
>
> Is the choice of the cell type intentional or important here? If so it might
> be worth convincing those libraries to add cell type 41 plotting and i/o
> capabilities.
> -- Forwarded message -
> From: A A
> Date: We
of cell type 41.
Is the choice of the cell type intentional or important here? If so it
might be worth convincing those libraries to add cell type 41 plotting and
i/o capabilities.
-- Forwarded message -
From: A A
Date: Wed, Jan 22, 2020 at 12:22 PM
Subject: Re: Some questions
Hi Jonathan,
The lines do remain dashed on successive calls. I guess the viewer keeps
pointing to the right objects even if their properties are retroactively
modified.
Here's what I mean about the diffusion term:
[image: Untitled.png]
On another note, I've posted some stuff on github which
I'm curious. Do the lines remain dashed on successive calls to plot()?
As to the third question, where are you seeing exponent n and subscript i? I'm
not suggesting we don't use them, just that I don't know where.
Is the discussion at
Dear Amine,
In the end, my suggestion does not work... Instantiation of Viewer() in
the Jupyter notebook always generates a spontaneous plot. We will have
to live with it. (I do not know the equivalent of 'silent 1;
pauseupdate" in Python Jupyter notebook).
Also, on first Viewer() instantiation
Hi Martin,
Thanks for your response. That's strange that such a "dummy" command would
be necessary.
I was able to answer the second question myself. It is possible to
*retroactively
*change line and axis properties. For the mesh1D example I did the
following:
viewer = Viewer(vars=(phi,
Dear Amine,
Concerning your second question, I think that this a normal (but in this
case, annoying) feature of the Jupyter notebook.
You might trying adding an extra (dummy) command to the cell, after the
line in which the Viewer() is instantiated. For example: ``print('Ready')``.
Best,
Martin
mathematical
rigour... Thanks!
-- Forwarded message -
From: A A
Date: Mon, Jan 20, 2020 at 5:01 PM
Subject: Some questions on the viewer
To:
Dear All,
I'm just getting back into using fipy after a few months hiatus. I'm
getting more familiar with how it works, but I have a couple
Dear All,
I'm just getting back into using fipy after a few months hiatus. I'm
getting more familiar with how it works, but I have a couple of questions
about the viewer:
- Is it possible to control linestyle (specifically dashes) of the
cellVariable objects tied to each specific viewer?
14 matches
Mail list logo
