Public bug reported:
Instead of videos we have blank space at the moment:
https://yade-dem.org/wiki/Screenshots_and_videos
Maybe a change on youtube's side, or a bad change on our (server) side.
** Affects: yade
Importance: Undecided
Status: New
--
You received this bug notificat
koverflow.com/questions/15639779/what-determines-whether-different-python-processes-are-assigned-to-the-same-or-d?lq=1
>> answer#25
> ___
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev
___
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
>
&g
> https://yade-dem.org/wiki/Performance_Test
Wow! Speed x6 for 500k particules?!
It was definitely worth trying with larger numbers, it changes the
picture completely when the last points are included.
Very nice page.
Could you also give some absolute timings for completness? A convenient
value
(forwarding to yade-dev)
On 28/02/14 10:13, Klaus Thoeni wrote:
> Hi guys.,
>
> have a look at this:
>
> https://yade-dem.org/wiki/Performance_Test
>
> Feel free to add your own tests. If you want I can provide the scripts for
> the
> graphs.
>
> Cheers
> Klaus
>
>
>
>
___
On 27/02/14 15:50, Chen, Feng wrote:
> Is it possible for the workshop to offer some kind of live broadcast for
> remote attendance?
Good idea. I can't tell you it will be done but I'll try to keep that in
mind.
Bruno
___
Mailing list: https://launch
Thanks! Comments below.
On 26/02/14 13:33, Matthias Frank wrote:
>
>
> i have also some benchmark results:
>
> for 1 thread
> ---
>
> InsertionSortCollider 7
> 213143
> after running "make install" in my build folder I start yade using "python
> yadeparallel -j4 --performance"
Why "python" in the first place?! I would not be surprised if the number
of cores allocated to python was 1, which may cause "yade -j4" to run in
a single thread context.
B
___
>>> It is a good benchmark overall, the problem is that it is hardly
>>> reproducible. Each run can give a really different total time (more than
>>> a factor 2 between two measure time, didn't you see that to?
>> when i run the script with num_balls1D = 10 i get:
>>
> Mmmmh... I should try again
>
> yes, it is faster at -j1:
>
So this is an independent problem.
For me -j4 is always faster and effectively uses 4 cores, be it with the
old or the new collider.
I have no idea what can be wrong with your processor.
B
___
Mailing list: https://la
Is there any difference at all on this machine, between -j1 and -j4?
B
On 25/02/14 18:56, Bruno Chareyre wrote:
> There is apparently a problem with your computer/compilation option/other?
> If you run an ordinary simulation with -j4 and many particles do you see
> 4 cores used?
67 spheres, velocity= 4.86679881913 +- 0.487840014886 %
> 200813 spheres, velocity= 2.64490152313 +- 0.285084118261 %
>
>
> SCORE: 3402
> Number of threads 4
>
> ##
>
>
> For my computer it seems to have nearly no spe
> sorry for late reply. Feel free to share the pdf. Originally it was supposed
> to be transferred to the wiki, anyway.
> I'm thinking about a good way to measure performance for highly dynamic
> simulations, now. Maybe the script that martin-niehoff posted[1] would be
> useful. It is basicly a
On 25/02/14 10:17, Christian Jakob wrote:
>
>> It is a good benchmark overall, the problem is that it is hardly
>> reproducible. Each run can give a really different total time (more than
>> a factor 2 between two measure time, didn't you see that to?
>
> when i run the script with num_balls1D =
than today will not count!).
A more detailed agenda will follow, which will be open for discussion here on
yade-dev.
If you have suggestions regarding topics to discuss or special events that you
would like to see, feel free to suggest.
With best regards.
Bruno Chareyre
(*) Yet Another Dis
> I rotated the wall below a little bit to make it slightly aslope. This
> is the reason why columns can collapse (not because truncation error):
>
I see.
>
> As you mentioned in a previous post we should define two benchmarking
> scripts. One for quasi-static simulations and one for dynamic ones
14 16:36, Bruno Chareyre wrote:
> Hi there,
> I implemented a parallel version of the InsertionSortCollider. It is
> almost ready but not yet pushed to the main trunk, as I have a few
> things to check before that.
> It would be helpful if some of you could 1/ test that your scripts
Hi there,
I implemented a parallel version of the InsertionSortCollider. It is
almost ready but not yet pushed to the main trunk, as I have a few
things to check before that.
It would be helpful if some of you could 1/ test that your scripts work
correctly and 2/ benchmark this for N>100k and j>4.
If discretization<=0 don't integrate... it makes sense.
Moreover, discretization=0 should be the default IMO.
IntegrateInertia is a very good feature but it should be used on
purpose, not by default.
B
On 21/02/14 01:29, Klaus Thoeni wrote:
> Hi guys,
>
> is there a reason why we have two paramet
On 20/02/14 10:52, Christian Jakob wrote:
> Hi,
>
> I want to do some updates/improvements of PFV method.
Don't do anything yet! There is some code cleaning going on locally
(different variable names, removing useless functions, and so on). It
will mess up everything when I will commit if you have
Thanks a lot Christian.
@Chao
See, as I told you, opening a bug report is more efficient than looking for me
in the building. ;)
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1282634
Title:
Fail
> Ok, so we have two options:
> a) swap for Ig2 (as it is now) and therefore get rid of goReverse in Ig2, and
> call go/goReverse for Ip2
> b) get rid of swap for Ig2 and call go/goReverse in both cases (maybe more
> consistent?)
>
> What do you think?
a) sounds feasible
b) no advantage in doi
>> Maybe not removed. I think it is necessary, precisely because we can
>> have non-symmetric functors. If you swap ids in Ip2 you may break the
>> work of the Ig2.
>> The go reverse is here for this reason (handling non-symmetric cases
>> without forcing a specific ordering of id1/id2 and without
e
anything from ParallelEngine?
For the consistency of sources formatting in yade, please don't keep
blank lines between each lines of codes.
Thanks for the two example scripts and the clear comments. It makes the
pull request self consistent.
Bruno
On 17/02/14 17:48, Bruno
forwarding https://github.com/yade/trunk/pull/40
Bruno
__
Hi Mr. Chareyre/Gladky,
As we all already discussed at the topic here[1] I have created a
general integrator interface for both multistep and single step methods.
I think the interface is flexible for the integration purposes. It
inh
> the "kn=10"
> will be written in the MatchMaker object. It doesn't need to add a "kn"
> member to the functor itself.
More precisely, the Ip2 may have a "kn" member but it will be the
matchmaker itself (NULL pointer by default), not the value of kn.
B
_
On 17/02/14 12:28, Klaus Thoeni wrote:
>
>> I think this is also what Anton had in mind. Base types should be free
>> of capillary things, which are very specific.
> So you agree that the parameters should already be separated at material
> level, correct?
Yes, except that the capillary model has
On 17/02/14 12:07, Klaus Thoeni wrote:
> Hi Bruno
>
>> I think non-symmetric functors are rarely necessary since most
>> combinations can be dealt with via inheritance (e.g. Frict vs CohFrict
>> is interpreted as Frict vs. Frict since CohFrict inherits from Frict).
> Exactly, but what if you want i
On 16/02/14 04:55, Klaus Thoeni wrote:
> Sorry for late reply, but here my thoughts. I think a separation at material
> level would be better, i.e. FrictMat inherits ViscElastMat which inherits
> something like ViscElCapillarMat. I think it would make sense because not
> all
> visco-elastic ma
Hi Klaus,
I think non-symmetric functors are rarely necessary since most
combinations can be dealt with via inheritance (e.g. Frict vs CohFrict
is interpreted as Frict vs. Frict since CohFrict inherits from Frict).
However, I am like you, I don't see the reason why it is asserted
symmetric. I sugge
** Changed in: yade
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1019349
Title:
RuntimeWarning: to-Python converter for
boost::shared_ptr already register
Commit fae9180ff fixes the problem.
** Changed in: yade
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/806469
Title:
3D View (shift-click)
Status in Yet A
Closing the bug. Please re-open and provide example script if the problem
persists.
UnbalancedForce is defined exactly the same way with and without capillary
forces, since the input values are the total forces on each body independently
of their origin.
** Changed in: yade
Status: New
Absolutely.
Closing :)
** Changed in: yade
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1273775
Title:
Too much memory used at creation/removal of intera
Public bug reported:
sudo apt-get install yadedaily
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libyadedaily python-yadedaily
The following NEW packages will be installed
libyadedaily python-ya
https://github.com/yade/trunk/pull/39
https://github.com/yade/trunk/pull/38
https://github.com/yade/trunk/pull/37
https://github.com/yade/trunk/pull/36
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4 76
"please don't close the bug" -> reopening.
** Changed in: yade
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1273775
Title:
Too much memory used at crea
Thanks for reporting. Could you check if the following replacement fix
the problem?
scene->interactions->requestErase(contact->getId1(),contact->getId2());
>
scene->interactions->requestErase(contact);
I don't know if I failed some search/replace or if it has been commited
afterward, but the
if (parentErase and childErase) return false;
else return true;
}
The change is relatively easy to implement. Feel free to comment on this
solution before I (or somebody else) implement it.
Bruno
[1] https://answers.launchpad.net/yade/+question/242890
--
_______
Brun
On 28/01/14 14:10, Anton Gladky wrote:
> That is true. I actually moved an implementations into
> ViscoelasticCapillarPM [1], but parameters are still in the parent
> class. Any suggestions how to improve it are very welcome.
If I don't miss something, it could be just like CapillaryPhys, which
in
>> the main difference is that the contact stiffness kn and the ratio kt/kn are
>> defined in the IP2 functor as indicated in the commit massage via MatchMaker
MatchMakers is right, yet I'm not sure it is incompatible with defining
parameters in materials as usual.
>> IMO, there is a potential o
t visco-elastic and capillary parameters.
>
> Anyway, I am glad you asked because I see potential of improving on both
> sides. What do you think?
>
> BTW, any other news?
>
> Cheers
> Klaus
>
>
> On Monday 27 January 2014 16:03:19 Bruno Chareyre wrote:
>>
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
ENSE
st: https://launchpad.net/~yade-dev
> Post to : yade-dev@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
ENS
> 1. Why will adding a vector of zeros [1] helps resetting the forces of clumps?
Because the size of the force container is adjusted dynamically. Adding
a zero force to body "id" instructs the container that "id" is a valid
index, then it will be resetted, otherwise it is not known by the
container
addForce() is thread-safe because each thread is computing its own partial sum
of forces. The total is sync'ed only once a step by NewtonIntegrator.
getForceUnsynced(id)+= is not thread safe, OTOH, all threads would access the
same value. It should not be used except in a few exceptions.
--
Yo
he
>> same than for the FrictPhys, which seems essential.
>>
>> Do you agree with this ? Of course, all this modifications will be described
>> in the documentation.
>>
>> François
> ___
> Mailing list: https://launchpad.net/
No progress since #6.
It should not be a problem for users. Why are you asking?
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/923929
Title:
OMP force container fails to reset forces on clump membe
On 17/12/13 11:28, François wrote:
>
> If they all inherit from elastMat this problem will disappear, no?
>
> No. In fact ViscElPhys already inherits from FrictPhys. We can cast a
> ViscElPhys into a FrictPhys, but not the opposite so I must change
> something here.
Ok. Well. I guess you will fi
erence in what really happens:
"mat.young =" ... is simple assignement.
"ViscElMat(.,young=...)" is triggering postLoad().
Last possible difficulty, the kn/Young decision must be preserved if you
save and reload.
I'm not saying it is difficult. Just a few thin
?
> (Anton, Raphaël ...)
>
> Thanks,
>
> François
>
>
> ___
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https
You are right. Feel free to fix.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1261388
Title:
Wrong code comment
Status in Yet Another Dynamic Engine:
New
Bug description:
Hi,
I think the
And, as mentionned yesterday. It is not a velocity, it is a flux.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1260213
Title:
error in FlowEngine with imposed pressure and getCellFlux()
Status i
I think we should fix that quickly, else we will have a significant flux of
weird bugs/questions from people who don't realize they are not running what
they think they are running.
It will be extremely difficult for us (repliers) to understand the problems
since, as shown above, the "Welcome to
Not a bug, although the documentation could be more explicit.
Docstring:
imposePressure( (FlowEngine)arg1, (Vector3)pos, (float)p) -> int :
Impose pressure in cell of location 'pos'.
://launchpad.net/~yade-dev
> Post to : yade-dev@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
>
>
>
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble c
After removing Tetra, another error with numpy/boost (conflicting
namespace "detail").
Last successfull compilations were late august. In the meantime I was on
12.04 away from office.
I guess I have to give up 10.04. :(
--
You received this bug notification because you are a member of Yade
devel
Maybe also of interest:
http://doc.cgal.org/latest/Kernel_23/group__intersection__grp.html#ga66850ea839dafff504fbd39e141fcc79
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1257843
Title:
/pkg/dem/
I don't see any intersect(triangle, segment) in CGAL 4.3 (latest)
documentation.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1257843
Title:
/pkg/dem/Tetra.cpp:116: error: no matching function fo
Public bug reported:
This compile error occurs on lucid (10.04). I know it is an old ubuntu, but it
would be nice to keep compatibility.
I guess the intersection(segment,triangle) is not available on older CGAL,
though I'm a bit surprised.
Not compiling Tetra on old systems is an option.
** Af
> Raphael, there is something wrong with this commit.
> Check-tests are failing. Please, have a look.
Regression tests can be tested with the following commands [1]:
yade --test
yade --check
If they don't give exactly the same as before it is reported as a failure.
In your case the behavior is r
For the record, a similar problem found a solution in [1]. The fix
mentioned there (see below) doesn't work in our case unfortunately, but
it may ring a bell for someone.
import sys
flags = sys.getdlopenflags()
import pybel
sys.setdlopenflags(flags)
import scipy.linalg
[1] http://grokbase.com/t/s
** Changed in: yade
Status: New => Triaged
** Changed in: yade
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1183402
Title:
Segmentation fault by importing
ools (4.0.0-1build1) ...
Setting up python-envisage (4.0.0-1build1) ...
Setting up mayavi2 (4.0.0-3build1) ...
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4
Invalid is correct.
Yes, there are additional prerequisites. If you google with the above
keywords you will find a few other threads where the question was raised.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpa
You are right. It is not the same but it is also bad.
I can include that, no problem.
B
On 29/11/13 07:18, Anton Gladky wrote:
> 2013/11/28 Bruno Chareyre :
>> I will update, however it seems to me that the pages you are quoting are
>> not the most relevant.
>> Jerome d
(yade-dev)
> For the broken link, I spoke about the page you (?) refer to :
> http://stevenharman.net/git-pull-with-automatic-rebase. Where we can not
> let display the image supposed to explain what is to be avoided..
Yes, me. :)
I can see the image on this page. Maybe a problem with your browser.
e authors:
>> Anton Gladky (gladky-anton)
>> Anton Gladky (gladky-anton)
>> Bruno Chareyre (bruno-chareyre)
>> Jan Stránský (honzik)
>>
>> revno: 3752 [merge]
>> committer: Jerome Duriez
v.
It still has to be checked versus the libs of the "main" archive
(suitesparse-dev, metis-dev).
On 14.04, it's a little bit slower. I think it needs to tune and
recompile some of the libs to achieve good performances.
Bruno
On 26/11/13 14:51, Bruno Chareyre wrote:
> (to yade-dev
: yade-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-users
> More help : https://help.launchpad.net/ListHelp
>
>
>
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 5
** Changed in: yade
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1254708
Title:
start-script picks wrong yade libraries in ubuntu 14.04
Status in Yet Another
Public bug reported:
If yade is compiled on 14.04 where yade stable is also installed, yade-mine
executable will import the stable libraries present in /usr/lib/python2.7.
It makes it impossible to use compiled version (maybe also problems to expect
if different binary packages are installed).
Took me a while to figure out the problem. The reason is the split of yade
package into different subpackages I think. Not sure about best solution.
Should it be fixed on the packaging side or code side?
--
You received this bug notification because you are a member of Yade
developers, which is
I checked version numbers Klaus, they are the same.
It seems we will never know what exactly the problem was.
Bruno
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1250928
Title:
Compilation from s
@Klaus
If you don't have them installed at all it means you did not read the install
manual.
How is it supposed to work? :)
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1250928
Title:
Compilatio
So. I tried a fresh 12.04 in chroot. Followed the documentation strictly to
install prerequisites, then compiled. Without the ppa and without metis.
I am a bit disappointed: nothing happens. Compiled normally, and runs the
fluid-coupling example script without problems (just extremely slow, as
e
Hi Anton,
Do you know why yade-daily on launchpad (8+3759+64~ubuntu12.04.1)
doesn't match the version I see with apt (5+3730+52~ubuntu12.04.1)?
Thanks
Bruno
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Uns
> Wait a little bit. Our private-discussed builds are almost ready.
>
> [1] https://launchpad.net/~yade-pkg/+archive/snapshots/+packages
> <https://launchpad.net/%7Eyade-pkg/+archive/snapshots/+packages>
>
> Anton
>
>
> 2013/11/21 Bruno Chareyre <mailto:
I'm curious to know what versions you have for the following
things: openblas, suitesparse, metis, lapack. Could you make keyword
searches on them [1]?
This set of libraries was difficult to use with combined packaged
versions in the recent years but it should be ok >=12.04. There seem to
be a few
And, by the way, launchpad can build for 12.04 without trouble. So,
reproducing the same steps should succeed for everyone, shouldn't it?
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1250928
Title:
-trunk-bin#
apt-get install yade
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package yade
On 21/11/13 16:29, Bruno Chareyre wrote:
> Hi Anton,
> Do you know why yade-daily on launchpad (8+3759+64~ubuntu12.04.1)
> does
precise main universe multiverse/
>
> Anton
>
>
> 2013/11/21 Bruno Chareyre <mailto:bruno.chare...@hmg.inpg.fr>>
>
>
>>
>> 12.04 has 0.70.0 as an "official" package [1]. Is "universe"
>> repository
>> enabled in your
>
> 12.04 has 0.70.0 as an "official" package [1]. Is "universe" repository
> enabled in your /etc/apt/sources.lists?
>
Ok. sources.list is one line here...
/deb http://archive.ubuntu.com/ubuntu precise main//
/
TYVM.
Bruno
___
Mailing list: https://la
@Klaus
Is it with yade-users ppa available?
In that case it should work like a charm in my experience.
Bruno
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1250928
Title:
Compilation from source p
@Klaus
It works for you because you have enough packages installed. This is why this
type error is not very easy to spot. If you install a fresh 12.04 however, it
will not work, whatever the compilation options.
@Alexender
Thanks for mentionning that. You are right it is the same problem.
I repl
Public bug reported:
It seems the instructions for installing prerequisites [1] will fail on ubuntu
12.04 if yade-users ppa is not enabled first.
Trying to compile anyway leads to a few cmake warnings but it will let one
build. Then boot failure because of missing lib (didn't do the build mysel
Hi Anton,
>
> We should, probably, consider creating our own build-server for
> Ubuntu/Debian
> daily builds.
I was also thinking about that recently. Thanks for investigating the
problem and suggesting this.
What do we need to setup a build server?
Also a question. The version number of yade-dai
Resending to the correct adresses...
B
Original Message
Subject:Re: [Yade-dev] yade-daily is not so daily
Date: Fri, 08 Nov 2013 12:59:07 +0100
From: Bruno Chareyre
Reply-To: bruno.chare...@hmg.inpg.fr
To: yade-dev@lists.launchpad.net
Hi Ehsan, Thomas
l try to fix that.
>
> Anton
>
>
> 2013/11/6 Bruno Chareyre :
>> Hi (Anton),
>> It seems yade-daily is slow generating for ubuntu 13.10, and I know a
>> few guys waiting for it (see e.g. [1]).
>> Is there something blocking? (sorry for dumb question, I cou
/yade/+question/238031
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4 76 82 70 43
___
Mailing list: https://launchpad.net/~yade-dev
Po
launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
>
>
>
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4 76 82 70 4
scribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4 76 82 70 43
_
For your question, you can check trunk/CMakeLists.txt and grep
"triangulation" in there. You will see how to compile something
conditionaly.
However, tetgen is available in ubuntu repositories, so there is no need
to compile it. It is quite often that some libraries are packaged
without any note o
Thanks for comments Anton.
> Well, we do really use bzip2 and gz compressors in some parts
> of the code [1], so the dependency on both of them should be there.
We surely use them. The question was more to know if the "-dev" packages
were needed.
I understand from your message that the "-dev" pack
> with libbz2-dev there is no problem.
Fine, but strictly speaking this is not needed for compilation. libbz2
is enough (since it was working correctly before).
Couldn't we avoid this new dependency?
Bruno
___
Mailing list: https://launchpad.net/~yad
>
> Why is there a underline after the code for the link ...
>
> `bla`_ ?
This is a convention of Sphinx, which we use to build the documentation.
http://openalea.gforge.inria.fr/doc/openalea/doc/_build/html/source/sphinx/rest_syntax.html#internal-and-external-links
>
> And why does a wrong link
>
>> Apparently it was Christian who added the /user/ in a
>> TesselationWrapper's docstring.
>
> sorry, i just wanted to make the link working...
>
No worries. I just wanted to be sure nobody would go for changing all
the links in the documentation.
B
__
Apparently it was Christian who added the /user/ in a
TesselationWrapper's docstring.
This is the problem with git merges, all confusing...
Bruno
On 08/10/13 11:44, Bruno Chareyre wrote:
> Hi there,
> After Jerome, Jan also got the idea of changing hyperlinks in the doc,
> from do
have been changed with "/current" in the meantime they will fail.
Cheers
Bruno
p.s. Please Jan, could you check if you have setup auto-rebase? For some
reason you are still triggering some merges.
--
___
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab.
>
>
>> Thanks Christian for comments.
>> Is that possible to use the same method as before, where the inertia was
>> just the total inertia of members? We should really keep that option
>> even if the default is now to compute inertia automaticaly. Reasons are
>> that sometimes we want something f
701 - 800 of 2047 matches
Mail list logo
