Thanks a lot for the helpful advice.
If I pass a custom max_num_threads to the constructor of mpi_init, then I
get
the following behavior:
- Segmentation violation, when max_num_threads = 3, 4,
numbers::invalid_unsigned_int
- Normal execution, when max_num_threads = 1, 2, 5, 6, 7, 8
On 12/02/2016 08:09 PM, Peng Ding wrote:
I met the following error after make,
/home/ztdep/Downloads/dealii-8.4.1/source/fe/mapping_q_eulerian.cc:100:79:
warning: ‘dealii::MappingQEulerian::MappingQEulerian(unsigned int, const EulerVectorType&, const
dealii::DoFHandler&) [with int dim = 3
Dear friends:
I met the following error after make,
/home/ztdep/Downloads/dealii-8.4.1/source/fe/mapping_q_eulerian.cc:100:79:
warning: ‘dealii::MappingQEulerian::MappingQEulerian(unsigned int, const EulerVectorType&, const
dealii::DoFHandler&) [with int dim = 3; VectorType =
dealii::T
Chris,
I used the following command successfully to build dealii (note Trilinos and
p4est are OFF)
|
rm -rf *&&\
cmake \
-DDEAL_II_WITH_MPI:BOOL=ON \
-DDEAL_II_WITH_PETSC:BOOL=ON \
-DDEAL_II_WITH_TRILINOS:BOOL=ON \
-DDEAL_II_WITH_METIS:BOOL=ON \
-DDEAL_II_WITH_P4EST:BOOL=OFF \
So you expli
On 12/02/2016 07:01 AM, Bruno Turcksin wrote:
2 - Are there facilities of some kind that can help in generating the
assembly code? In Fenics I just specified the weak formulations.
You need to write the code in C++ and loop over cells, quadrature points, and
basis functions yourself. So
Hi Wolfgang,
I know that the typical treatment of the interface matching conditions is
along the lines that you noted. However, it is not clear to me how to
follow these guidelines in the particular case that I am working on, which
is described in the file that I attached to my previous e
On 12/02/2016 09:30 AM, benhour.amiria...@gmail.com wrote:
Thanks very much for your help and support. I do really appreciate your time
and know you are really busy. The fact is that my code ran just for the first
time step and can not solve for the other time step. when I refine the global
mesh
On 12/02/2016 01:13 PM, Oded Yaakobi wrote:
Now I encounter another aspect of my problem that I don’t know how to tackle –
the matching conditions on the interface between the domains of the Stokes
flow in the droplet and around it.
Attached is a description of the problem in detail. I would b
Dear Jean,
Thanks very much for your help and support. I do really appreciate your
time and know you are really busy. The fact is that my code ran just for
the first time step and can not solve for the other time step. when I
refine the global mesh twice, this problem happened, however, with
in
Franco,
2016-12-02 10:57 GMT-05:00 Franco Milicchio :
> So can I use solvers as in Tutorial 3, for instance, and I'll be safe and
> sound?
Yes.
> However, is someone planning some additions to deal.II to make it less
> verbose, as in, for example, providing a DSL for that?
There are no plan to ad
Thank you Bruno for your answers, I failed to mention that I use Fenics
with C++, not with Python, sorry about that. I just have few points to ask,
if you can bear with me.
1 - Is it truly thread-safe? As in running a single analysis, or running
>> several (no data sharing), without problems.
I think you're right about my p4est build, there is something wrong with
how it's linking to and/or using Lua, see attached. I will have to
investigate this further.
On Fri, Dec 2, 2016 at 3:44 PM Bruno Turcksin
wrote:
> 2016-12-02 9:36 GMT-05:00 Chris Coutinho :
> > What do you think, is this
Hi Giulia,
I used deal.II in my thesis to do model reduction (Wolfgang was kind enough
to include a link), but I used POD and not RB. Let me know if you have
questions about the thesis :)
Thanks,
David Wells
On Thursday, December 1, 2016 at 8:18:56 AM UTC-5, Giulia Deolmi wrote:
>
> Dear Jean-
On 12/02/2016 04:12 AM, JxW wrote:
The following code reproduces this problem for me
(The CMakeLists.txt simply calls the DEAL_II_INVOKE_AUTOPILOT() macro):
#include
#include
intmain (int argc, char *argv[]) {
dealii::Utilities::MPI::MPI_InitFinalize mpi_init (argc, argv);
std::cout << "
2016-12-02 9:36 GMT-05:00 Chris Coutinho :
> What do you think, is this a p4est build error? It's not immediately clear
> from the build output if this is an issue or not.
Yes, it is hard to say but I don't think that these errors are really
a problem but now I remember one time I installed p4est a
Howdy Bruno,
Thanks for the quick reply.
Something could have gone wrong when building p4est, but I'm not 100%
certain because the config file is full of contradictory messages. For
example, when checking c compiler validity, it uses some options that work
and others that produce errors, but I
Franco,
I'll try to answer your questions but be aware that deal.II is a C++
library and that there are no python wrappers unlike Fenics:
On Friday, December 2, 2016 at 6:59:16 AM UTC-5, Franco Milicchio wrote:
>
> 1 - Is it truly thread-safe? As in running a single analysis, or running
> sever
Chris,
I don't know why it doesn't work :-( Here is what you can try:
- reinstall p4est and check that there are no error during the
compilation. The most probable reason for your error is that something
went wrong during the compilation of p4est.
- use candi to install everything (https://githu
Dear all,
after a couple of years developing with Fenics on MacOS X, I stumbled upon
two dreary problems: it won't provide binaries anymore, and it does not
play well with multithreading. I was then thinking about switching to
deal.II, but I hope you can help me in dispelling some doubts.
My
I encountered this problem on my linux machine. Everything works fine in
debug mode; however, as soon as I switch to release mode using
-DCMAKE_BUILD_TYPE=Release, the code still compiles, but bumps into a
segmentation violation when it runs.
The following code reproduces this problem for me
(
Hi Bruno,
Setting p4est_dir to the entire p4est-x.x.x.x directory doesn't change
anything - it still fails with variables undefined in the current scope.
See attached cmake and make logs for detailed output, but I don't noticed
any difference.
Regards,
Chris
On Thursday, December 1, 2016 at
21 matches
Mail list logo
