Awesome! Thank you! :-)
On 22 Feb 2018, 21:12 +0100, Anton Gladky , wrote:
> Dear Yade developers,
>
> the new minor Yade 2018.02b was released on 20-th of February.
> It allows us to compile Yade against CGAL_4.11 and fixes some
> bugs. Tarballs are available on GitHub
Dear Yade developers,
the new minor Yade 2018.02b was released on 20-th of February.
It allows us to compile Yade against CGAL_4.11 and fixes some
bugs. Tarballs are available on GitHub [1] and Launchpad [2].
Also the new version was uploaded to Debian [3] and even synced
into the Ubuntu LTS
On 02/16/2018 11:12 PM, Anton Gladky wrote:
thanks all for the effective and fast
contribution resolving CGAL issue!
Thank you for efficient scramble! :)
Bruno
___
Mailing list: https://launchpad.net/~yade-dev
Post to :
Hi Anton, I confirm that your latest commit fixes the polyhedra crush problem
:) Do you know what caused the freeze? best regards Janek
Dnia 16 lutego 2018 23:12 Anton Gladky
gladky.an...@gmail.com napisał(a):
Dear all, thanks all for the
Dear all,
thanks all for the effective and fast
contribution resolving CGAL issue!
I will try to fix polyhedron-crash test
as soon as possible and release
the new minor Yade version.
Best regards
Anton
On Feb 16, 2018 17:27, "Luc Scholtes" wrote:
Hi guys,
Just a
Hi Robert,
Congrats for finding the bug and thanks for fixing.
On 02/13/2018 11:55 PM, Robert Caulk wrote:
the issue was compiler related. GCC 5.4 on ubuntu 16.04 initialized
factorizeOnly to false by default, while GCC 7.2 on ubuntu 18.04 did
not do this.
That's a good example of
Ok, I pushed the fix for the DEM-PFV-check.py failure. I discovered the
issue was compiler related. GCC 5.4 on ubuntu 16.04 initialized
factorizeOnly to false by default, while GCC 7.2 on ubuntu 18.04 did not do
this. Therefore, the only necessary change ended up being the explicit
initialization
On 02/13/2018 10:12 AM, Robert Caulk wrote:
I’m running into deeper problems than I expected on this solver bug
fix. I need some more time to trouble shoot.
Let me know, I can also try some things. I have been able at least to
compile and run cholmod on 18.04 with simple c++ programs.
I
I’m running into deeper problems than I expected on this solver bug fix. I
need some more time to trouble shoot.
What’s our deadline? I read something about a freeze till March 1st?
Regarding standard gpus for yade: No, suitesparse depends on double
precision compute power and standard graphics
Awesome.
Years ago we were using cholmod without the eigen interface, it will be
a revert...
These cholmod/openblas issues make me nervous (not mentionning other
attempts with Pardiso and Taucs, which all worked at some point). It
still did not stabilize after 6+ years.
Do you think the GPU
Yes! We should be able to replace the Eigen cholmod interface entirely with
the existing direct cholmod solver (useSolver=4). Right now the #ifdefs are
configured for the special GPU build but I will generalize it today and
commit it so that it can be used without GPU compilation flags. Cholmod is
Thank you very much for help Janek.
I confirm that I could compile trunk on ubuntu18 with CGAL, without
special steps (not even dpkg, just cmake+make without options).
For DEM-PFV-check.py the problem is with the cholmod solver. I'll try
and fix that.
@Robert, you mentioned that by-passing
OK, so I did the initial commit for cgal 4.11, the most importatnt stuff is in
the commit message. I will repeat it here in short: 1. maybe the #ifdefs
that I added in lib/triangulation/RegularTrian are not necessary? 2. the
ALPHASHAPES changes inlib/triangulation/Tesselatio are not
13 matches
Mail list logo