Hello everyone!
This is deal.II newsletter #121.
It automatically reports recently merged features and discussions about the
deal.II finite element library.
## Below you find a list of recently proposed or merged features:
#10470: Fix more issues found by AddressSanitizer (proposed by masterle
Thanks Luca it works.
Regards,
Heena
On Fri, Jun 5, 2020 at 6:19 PM luca.heltai wrote:
> Dear Heena,
>
> unfortunately, we failed in cherry picking a default value in the
> parameter file.
>
> The generated parameter handler tries to write output files in a `results`
> directory (as indicated i
Yes. On it.
L.
> On 5 Jun 2020, at 18:21, Wolfgang Bangerth wrote:
>
> On 6/5/20 10:19 AM, luca.heltai wrote:
>> Wolfgang, it seems that indeed the default parameter file in 9.2 still
>> contains `set Output directory = results`.:(
>
> Want to move that to the 9.2.x branch in case we create a
Brilliant! Thanks a lot. -Lei Li
On Friday, June 5, 2020 at 4:49:56 AM UTC-7, Simon Sticko wrote:
>
> Hi,
> I suspect that the condition you have would be easier to enforce weakly by
> adding terms to the weak formulation, as is done in e.g. discontinuous
> Galerkin.
>
> Nevertheless, if you sti
On 6/5/20 10:19 AM, luca.heltai wrote:
Wolfgang, it seems that indeed the default parameter file in 9.2 still contains
`set Output directory = results`.:(
Want to move that to the 9.2.x branch in case we create a .1 release?
Best
W.
--
---
Dear Heena,
unfortunately, we failed in cherry picking a default value in the parameter
file.
The generated parameter handler tries to write output files in a `results`
directory (as indicated in the default parameter file `set Output directory =
results`), which however is not created by th
Hi,
I suspect that the condition you have would be easier to enforce weakly by
adding terms to the weak formulation, as is done in e.g. discontinuous
Galerkin.
Nevertheless, if you still want the normals at the nodes you can create a
"dummy" quadrature which has the nodes on the face as quadrat
Hi Peter,
thank you for the answer. Actually i did put the fe_series.h.
I forgot to mention that the problem arise when i use template
specialization by the end the implementation
#include
#include
#include
#include
using namespace dealii;
namespace hpfe{
template
class HPSolver
{
public
Dear Ihsan,
I have no problem to compile the following code (your code with minor
adjustments):
#include
#include
#include
#include
using namespace dealii;
template
class HPSolver
{
public:
HPSolver(
const unsigned int max_fe_degree);
//virtual ~HPSolver();
const hp::FE
Hi All,
I am trying to implement hp-fem into my problem according to the step-27.
But, i have an error when i am trying to compile,
error: no matching function for call to 'dealii::FESeries::Fourier<3,
> 3>::Fourier(std::vector&, dealii::hp::FECollection<3, 3>&,
> dealii::hp::QCollection<3>
10 matches
Mail list logo
