Not yet. But "CGAL needs 1.4sec for 100k spheres" is very good. This
is what CPU?
1.3sec in average for triangulate() with the script lines commited
earlier :-) (the other test was out-of-yade program).
This is on intel Xeon. Let me know what it gives on your laptop if you
give it a try.
No
> > reason (experimental, might change without notice etc).
> Heh, that's why I asked. :)
Oh, sorry, I overlooked the postscriptum. Never mind. There is no proper
solution currently, if you want to use multiple scene objects
You should make the default shared_ptr(), then test it, and if it
is
> tt=TriaxialTest()\ntt.generate('test.xml')\nO.load('test.xml')
>
TriaxialTest().load()
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://h
revno: 2527
committer: Bruno Chareyre
branch nick: yade
timestamp: Tue 2010-11-02 18:40:46 +0100
message:
- add example commands in docstring.
modified:
pkg/dem/TesselationWrapper.hpp
--
lp:yade
https://code.launchpad.net/~yade-dev
Example is in header + docstring now (docstring is hardly readable in hpp).
reason (experimental, might change without notice etc).
Heh, that's why I asked. :)
You should pass
no argument to triangulate, instead use Omega::instance().getScene() in
the function.
In typical situations, TW
> Sorry, I live in relations of my 2 cores laptop :-) but still overall speedup
> for 8 cores is 5.5x (page 66 of Vaclav's thesis), so this, depending on
> engine, is not "of no use" yet, at least from my point of view.. but yes,
> parallel 4+4 at the same time would be better than 8 and then 8.
> Check revno2526. Example in the header :
Can you put that to the docstring instead?
> TW.triangulate(O._sceneObj()) //compute regular Delaunay triangulation,
Just to reming you that O._sceneObj has the leading underscore for a
reason (experimental, might change without notice etc). You should pa
Awesome! Thanks for pointers.
B.
yes/yes/no.
see
https://yade-dem.org/sphinx/yade.wrapper.html#yade.wrapper.ParallelEngine&;
https://yade-dem.org/sphinx/prog.html#parallel-execution
v
___
Mailing list: https://launchpad.net/~yade-dev
Post to
Not yet. But "CGAL needs 1.4sec for 100k spheres" is very good. This
is what CPU? And couldn't you give a some working script, such as
calculate the volume of Voronoi cells for spheres (like voro++)? It
would be useful not only for me, I think.
Check revno2526. Example in the header :
tt=T
Hello,
>We know that parallelized engines have usually no use of more than ~4-5
>threads currently.
>Here, I have easily 10 proc. available for routine jobs. Which means I
>could solve my linear system on, say, 4 procs while interactions are
>dispatched on 4 other procs (also applies if only o
Václav Šmilauer said: (by the date of Tue, 26 Oct 2010 18:58:32 +0200)
> I think it should be fixed in eigen, if that is a pure numerics problem.
> That's why we use libs, to not do everything ourselves.
Vaclav, could comment a bit in that thread?
http://forum.kde.org/viewtopic.php?f=74&t=91
revno: 2526
committer: Bruno Chareyre
branch nick: yade
timestamp: Tue 2010-11-02 17:23:44 +0100
message:
- Add python wrapping for python use of TesselationWrapper (+ a few fixes and
formating)
modified:
lib/triangulation/Tesselat
> I've been trying to parallelize some loops with openMP in some code used
> by FlowEngine (independant compilation out of Yade). I could get
> no-so-bad speedup with little efforts. Now I'm wondering how to get even
> better speedup and I have a few general questions.
> - Is there already a mec
Is it possible to run FlowEngine in parallel and InteactionsDispatcher in
parallel? (I don't know it :-) If it is possible, I think it would be better to
run firstly one engine in parallel and then the second one in parallel rather
then both at the same time (before continuing, the program (m
Hi Bruno,
>- Is there already a mechanism in Yade to run more than one engine in
>parallel? For instance, flow engine and interactionsDispatcher are doing
>two independant things and could be run at the same time without
>interfering. It implies nested omp directives.
Is it possible to run Flo
Hi,
I've been trying to parallelize some loops with openMP in some code used
by FlowEngine (independant compilation out of Yade). I could get
no-so-bad speedup with little efforts. Now I'm wondering how to get even
better speedup and I have a few general questions.
- Is there already a mechani
02.11.2010 15:32, Bruno Chareyre:
By the way, Sergei, did you find how to use this
TesselationW->Volume(id) in Yade?
No.
Did you try, and are you still interested? I see it needs a few py
functions defined in order to do it all from python.
Not yet. But "CGAL needs 1.4sec for 100k spheres
By the way, Sergei, did you find how to use this
TesselationW->Volume(id) in Yade?
No.
Did you try, and are you still interested? I see it needs a few py
functions defined in order to do it all from python.
B.
___
Mailing list: https://launchpad
Have you tested it? Normalizing I mean.
Yes, I just tested. Same problem.
B.
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://help.launc
revno: 2525
committer: Václav Šmilauer
branch nick: trunk
timestamp: Tue 2010-11-02 13:02:13 +0100
message:
1. Fix intiialization problem in Shop::kineticEnergy (thanks, Anton)
2. Several enhancements of the post2d module
3. Fix a
Anton Gladky píše v Út 02. 11. 2010 v 12:53 +0100:
> Hi,
>
> there are some warnings in compilation, Eigen-related:
> is it our fail?
Ah, that's right. Good warning. The non-diagonal elements might not be
zero. I will fix that. Thanks.
Vaclav
___
Mai
Hi,
there are some warnings in compilation, Eigen-related:
C /home/gladk/dem/yade/current/build-current/plugins11.cpp
In file included from
/home/gladk/dem/yade/current/build-current/plugins11.cpp:3:
/usr/include/eigen2/Eigen/src/Core/Product.h: In static member function
'static Real Shop::kineti
Have you tested it? Normalizing I mean.
Anton
2010/11/2 Bruno Chareyre
>
>
>
>
>
>
> Question sent to Eigen forum (
> http://forum.kde.org/viewtopic.php?f=74&t=91129).
>
>
> Quoting the Eigen guy's answer below. What do you think?
>
> *
> "I've enabled auto-normalization for this function.
>
Question sent to Eigen forum
(http://forum.kde.org/viewtopic.php?f=74&t=91129).
Quoting the Eigen guy's answer below. What do you think?
/
"I've enabled auto-normalization for this function.
For the record, it is line 179 in src/Geometry/AngleAxis.h:
m_angle = Scalar(2)*std::acos(q.w
> In flow coupling, we need triangulations updated at run-time, which
> makes CPU time a major issue. I forget using Voro++ for this reason.
> For post-processing applications like this, we don't need tesselation,
> but only triangulation : https://yade-dem.org/wiki/Triangulation.
> I agree that
CGAL needs 1.4sec for 100k spheres (regular triangulation, probably less
for simple Delaunay).
In flow coupling, we need triangulations updated at run-time, which
makes CPU time a major issue. I forget using Voro++ for this reason.
For post-processing applications like this, we don't need tessela
26 matches
Mail list logo
