On 05/07/2018 02:20 PM, Zhao Yidong wrote:
2.Iterate on every quadrature point in every cell, store them. (These points
are in real space right?)
|
for(unsignedq=0;qpoint =fe_values.quadrature_point(q);
|
3. Use fe.shape_value() to get shape value at every degree of a cell,
store_point is
Thank you very much!
My fe is FE_Q(1) type:
FE_Q(1)
I make comparison like this:
1.Create fe_values like this:
FEValues fe_values(fe, quadrature,
update_values |
update_quadrature_points |
update_gr
On 05/06/2018 09:05 AM, Zhao Yidong wrote:
Indeed, my problem is this:
1. I have fe which is a FiniteElement class, and I have fe_values which is a
FEValues class. I also have QGauss quadrature to create fe_values.
2. I iterate on every quadrature point in a iteration on every cell, store the
Dear all,
Over the weekend we made some progress rooting out quite a number of
bugs. The current release candidate is now v9.0.0-rc3.
It would be great if you could test it on your machine with your typical
configuration. For this update your git repository and switch to the
release branch:
On 05/05/2018 09:11 AM, Zhao Yidong wrote:
The Point I send into the function locates in the reference space ( [-1,
1]x[-1, 1] ),
By the way, in deal.II the reference cell is [0,1]x[0,1]. So even bilinear
shape functions will be negative if you evaluate them at (-1,-1), for example.
Best
Sorry. The address is the following:
https://github.com/dealii/dealii/releases/v9.0.0-rc2
Luca
> Il giorno 06 mag 2018, alle ore 11:30, luca.heltai ha
> scritto:
>
> Dear all,
>
> I have just uploaded a new package for deal.II-9.0.0-rc2 here:
>
> https://github.com/dealii/dealii/releases/e
Dear all,
I have just uploaded a new package for deal.II-9.0.0-rc2 here:
https://github.com/dealii/dealii/releases/edit/v9.0.0-rc2
This was compiled with Apple clang 9.1.0, and gfortran from gcc 7.3.
Please test, and let me know if everything is ok.
Best,
Luca.
--
The deal.II project is loc
Success?
I'd love to tell you how I did it, but I'm not entirely sure! So many
buttons have been clicked at this point.. HOWEVER, a few things any
lurkers can try are this:
1.) On the 2017 Visual Studio Task Bar: TEST>TEST SETTINGS> DEFAULT
PROCESSOR ARCHITECTURE> X64
2.) My error logs seem
