Mr. Simon
thank you for your response, It was exactly what I was looking for.
On Tuesday, September 22, 2020 at 5:01:42 PM UTC+9 simon...@gmail.com wrote:
> Hi,
> I would do it like this:
>
> // Setup two DoFHandlers, one for the heat and one for Allen-Cahn
> DoFHandler
Dear Bruno,
Sorry for the late reply. Here is flooding, I was driving home hours
before. You are right, in the linux version of gmsh, it always gives the
error message that cannot find the corresponding vertex, but actually I do
nothing on the cell. It is the 1e-7 rounding error that makes the
https://dealii.org/developer/readme.html#configuration-options says to call
cmake with -DPETSC_DIR=/path/to/petsc -DPETSC_ARCH=architecture.
I normally just set the environment variable PETSC_DIR and configure
deal.II with -DDEAL_II_WITH_PETSC=ON
Best,
Daniel
Am Di., 22. Sept. 2020 um 12:29 Uhr
Hi,
I would do it like this:
// Setup two DoFHandlers, one for the heat and one for Allen-Cahn
DoFHandler heat_dof_handler(triangulation);
DoFHandler allen_cahn_dof_handler(triangulation);
// Solve for this first
Vector heat_solution;
// Lots of things in between here...
// When
Dear all,
I have one problem when I try to input the .msh file with grid_in
function. The error message is :
*
Exception on processing:
An error occurred in line <3139> of
If he’s running from the deal.II terminal, he should have the module command
(it is part of the spack installation).
The deal.II terminal exports the paths so that the module command is there.
What version of the deal.II package is he using? On my system, this is the
output I get:
Malhar,
the template arguments for DataOut are dim and DoFHandlerType where
DoFHandlerType defaults to DoFHandler
since you are using a DoFHandler<2, 3> object you need to specify the
second template argument explicitly, i.e.
DataOut<2, DoFHandler<2,3>> data_out;
You could have a look at
Dear Bruno,
Thank you for your help! I added physical groups for volume, surfaces,
curves, and points. But the problem remains the same. The modified geo
file is attached below.
Best regards,
Yuesu
On Tue, Sep 22, 2020 at 7:55 AM Bruno Turcksin
wrote:
>
> Yuesu,
>
> I had the same problem
I'm using version 9.0.0 of deal.ii. I have an older MacBook and it won't
update past iOS 10.13.6. I downloaded the .dmg file and opened it/moved it
into my applications but I haven't done anything else besides try to run
the first example.
On Tuesday, September 22, 2020 at 6:05:23 AM UTC-6
Dear Malhar,
just as you did for the Triangulation and the DoFHandler, also DataOut should
be instantiated with <2,3>, i.e.,
not
DataOut<2> …
but
DataOut<2,3> …
Best,
Luca.
> On 22 Sep 2020, at 7:37, Malhar T. wrote:
>
> Hello All,
> I hope you are doing well !
>
> I am working
Yuesu,
I had the same problem recently. Our gmsh reader assumes that the user has
set boundary id and material id to the mesh. It looks like you don't have
those and so the file is read incorrectly.
Best,
Bruno
On Tuesday, September 22, 2020 at 2:04:17 AM UTC-4 jinyu...@gmail.com wrote:
>
On 9/22/20 10:41 AM, Paras Kumar wrote:
As can be seen in figures 7 & 8 of the attached report, a further refinement
results in relatively smoother contours, but the irregularities are still not
eliminated.
OK, that's good to know at least as a check that your program is doing
something
On 9/22/20 4:27 PM, Wolfgang Bangerth wrote:
I wished every student project were as comprehensively explored! :-)
I tacitly assumed that Maurice Rohracker is your student. I didn't mean to
imply that the work you're doing is at the "student level" -- quite the
contrary: What your reports
On 9/22/20 11:09 AM, Paras Kumar wrote:
In order to verify if the "improper" modeling of the curved particle surface
due to the reason you explained above, is the cause for this irregularities,
we tried with a cubic particle, thereby eliminating the above issue, but still
observe
Hi Ray,
I’m happy to see that Simon has already given a great explanation as to how to
solve your problem. It’s probably more on point than the code that mentioned
that I would direct you towards. So it really was worthwhile asking the
question again here :-)
Best,
Jean-Paul
> On 22 Sep
Hello everyone!
This is deal.II newsletter #135.
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:
#10949: Replace __restrict by DEAL_II_RESTRICT (proposed by
Honestly I don't know. I wonder if the terms -1e-07 are the problem. I
told you to remove SetFactory("OpenCASCADE") because it was the only
difference with my .geo files.
Bruno
Le mar. 22 sept. 2020 à 11:20, yuesu jin a écrit :
>
> Dear Bruno,
> The problem was solved after I removed the
Hello,
I tried to run step-18 and initially received the following error message:
Error! This tutorial requires a deal.II library that was configured with
the following options:
DEAL_II_WITH_MPI = ON
DEAL_II_WITH_PETSC = ON
DEAL_II_PETSC_WITH_COMPLEX = OFF
However, the
Dear Bruno,
I did some modification according to your suggestion :
*Physical Volume("4") = {1};//+Physical Surface("0") = {4, 3, 2, 5, 1, 6};*
I add all external surfaces in one
You don't want to set the physical groups for the curves and the
points. This means nothing in deal.II. A vertex does not have a
boundary ID. You need all the external surfaces and the volume to have
a physical group. That's it.
Bruno
Le mar. 22 sept. 2020 à 10:24, yuesu jin a écrit :
>
> Dear
Hmmm. Can you try without the SetFactory("OpenCASCADE"); and can you
send me your .msh
Bruno
Le mar. 22 sept. 2020 à 10:45, yuesu jin a écrit :
>
> Dear Bruno,
>I did some modification according to your suggestion :
>
> Physical
Hello Luca,
I am sorry, I should have mentioned it in the question, I had tried it
earlier, but it leads to argument mismatch because, as Daniel has posted,
the second argument is DofHandlerType rather than spacedim. But, thank you
for your help. Appreciate it.
Best Regards,
Malhar
On Tue, Sep
22 matches
Mail list logo