Hi,
I have done the mex-coupling with dealii before. As Bruno said, it is easiest
to mex with cmake. Example in attached zip. Hope it helps.
Best,
Simon Sticko
On 15/08/2022 15:05, Bruno Turcksin wrote:
Simon
Le lun. 15 août 2022 à 08:52, Simon Wiesheier mailto:simon.wieshe...@gmail.com>>
On 8/13/22 11:20, M. Bänsch wrote:
*** Caution: EXTERNAL Sender ***
On Wednesday, August 10, 2022 at 1:06:58 AM UTC+2 Wolfgang Bangerth wrote:
It's hard to say what the reason is without having a small test case that
shows the issue. Since the issue happens during solution transfer,
Hi Wolfgang,
No, I didn't check. I was just running a few example programs that were
compiled during the installation process.
However, I believe it is a good exercise for me to see if I can find the
bug :). So, I will give it a try and report back if I find anything or get
stuck.
Marco
On
On 8/15/22 00:50, Marco Nawijn wrote:
Just for information, when you run the example with MPI on 1 processor (so -np
1), the process runs fine. Any value >1 results in this error. The error
itself makes sense because it requests a massive amount of memory (I am
running on a laptop at the
Simon
Le lun. 15 août 2022 à 08:52, Simon Wiesheier a
écrit :
>
> I also thought about transferring the data by reading from/writing to a
> file.
> But I was looking for a more general approach without having to create
> files.
>
> Writing files is no less general than coupling directly Matlab
Dear Bruno,
I also thought about transferring the data by reading from/writing to a
file.
But I was looking for a more general approach without having to create
files.
I was also pondering if it is possible to compile the mex file like a
normal dealii program (by adding a few Matlab macros to
Simon,
You could just write/read files to transfer the data and you can launch
your deal.II code from Matlab using
https://www.mathworks.com/help/matlab/ref/system.html This way Matlab does
not need to know anything about deal.II. You just write and read files, and
you execute a bash command.
Hi Jean-Paul,
I can confirm that the patch works like a charm. Thanks!
I now run into another issue, when running step-17. It fails with the
following message:
***Memory allocation failed for SetupCtrl: maxvwgt. Requested size:
137438953480 bytes
I did a quick search on the internet and
