uno Chareyre (bruno-chareyre)
** Changed in: yade
Importance: Undecided => Medium
** Changed in: yade
Status: New => Confirmed
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/17322
>It seems to be another compiler/cgal a-logical bug
Well... blame the a-logical programmer first.
A redundant and undefined FlowEngine::currentTess was floating around. It was
harmless until someone had the idea of using it in some code.
Fixed in [1].
Bruno
[1]
https://github.com/yade/trunk/com
> we should use directly crackAperture*crackArea as Vo in dV/Vo, no?
That's more or less what I wanted to suggest. I can't explain why I wrote that
strange formula.
However I also wanted to skip the calculation of crackAperture*crackArea,
namely because there can be multiple cracks, as you point
>I am particularly confused by [3]
A local crack is a polygonal face of the Laguerre graph. I did not find online
content showing a Laguerre graph in 3D but you can find inspiration by looking
at a Voronoi graph [1] (some polygonal faces are visible on the outer contour).
The code at [3] is loop
** Description changed:
In the basic PFV scheme the incremental change of density of a pore
fluid after a change of pore volume is dependent on dV/Vo where Vo is
the reference pore space within a tetrahedral cell [1], i.e.
V(tetrahedron)-V(spheres).
- In DFNFlow "V" should reflect the f
Q1 - I think it is possible to define a relevant geometry for multiple
cracks; it is just the intersection of one tetrahedron with multiple
polygonal faces. I think the problem of multiple fracture planes
crossing one edge is very special, I would escape it on the basis that
you can't break another
Hi Luc,
Please keep this discussion for the bug only.
Bruno
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1734653
Title:
DFN+fluid compressibility not using the correct reference volume
Status in
Hi Jan,
[1] was true at some point, but it is wrong now.
B
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1738232
Title:
Inconsistency in doc of Body::intrs and code
InteractionContainer::insert
I am unable to understand the bug. Please provide a way to reproduce, else we
will just close this bug.
Bruno
** Changed in: yade
Status: New => Incomplete
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchp
Hi Rémi,
It seems to me that the buildbot started failing between builds 4343 and
4344 (below) allthough it compiled exactly the same source in both cases.
Could it be a full HD or something server side?
Thx
Bruno
https://yade-dem.org/buildbot/builders/yade-full/builds/4343
https://yade-dem.org
Hi Jérôme,
Chained cylinders are considered deprecated, they should be replaced by PFacets
and friends - hence removed at some point (better NOT use them). No point
improving the doc then.
Besides, one of your comment overlooked the meaning of inheritance in c++ in
general and in Yade:
"Do we a
Hi Anton,
Thanks for notice.
I would suggest to release ASAP unless someone raises a solid reason not
to do so by - let's say - wednesday this week.
Cheers
Bruno
On 02/03/2018 05:49 PM, Anton Gladky wrote:
Dear Yade developers,
the freeze for the next 18.04 LTS version of Ubuntu
(stop sync fr
Hi Robert,
On 02/02/2018 07:37 PM, Robert Caulk wrote:
Hey Yade Devs,
I am wondering if we have the demand to create a Yade related white
paper publication. The publication would document very Yade specific
functionalities and I imagine some papers might even highlight pieces
code. I think t
On 02/05/2018 08:42 PM, Anton Gladky wrote:
I also want to ask everybody to have a look at the bug-tracker [1].
Good point. I'll check the one you mentioned at least.
It would be great to fix some more.
B
___
Mailing list: https://launchpad.net/~
** Changed in: yade
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1084454
Title:
Documentation deprecation
Status in Yade:
Won't Fix
Bug description:
S
No luck with the nullptr assumption. It segfaults on regular bodies.
I am unable to figure out what the problem is.
It is also not very reproducible, playing with the inspector can make the
script pass the segfault point...
Bruno
___
code:
cerr<<"BodyContainer::erase -> reset: "< reset: 1070 1
Se
** Changed in: yade
Status: Fix Committed => 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/1738747
Title:
ymport.unv - global name 'facets' is not defined
Status in Yade:
Fi
** Changed in: yade
Status: Fix Committed => 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/1671045
Title:
Missing reference [Duriez2016]
Status in Yade:
Fix Released
Bug de
"missing link" from [3] to [1] --> fixed a while ago it seems
closing the bug
** 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/1153629
Titl
** Changed in: yade
Status: Fix Committed => 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/1666339
Title:
DFNflow crashes for compiled trunk but not non-optimized debug
compi
** Changed in: yade
Status: Fix Committed => 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/1559098
Title:
Crash when Parallelization is used for O.bodies.replaceByClumps
Statu
** Changed in: yade
Status: Fix Committed => 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/1380103
Title:
polyhedral code, segmentation fault & memory leak
Status in Yade:
F
Fixed. Closing.
** Changed in: yade
Status: New => 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/1291977
Title:
Arithmetical error in documentation?
Status in Yade:
Fix Rel
The bug is not specific enough and getting old. Closed.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1084454
Title:
Documentation deprecation
Status in Yade:
Won't Fix
Bug description:
Some
On 02/07/2018 05:35 PM, Janek Kozicki (yade-dev) wrote:
Regarding compiling yade with CGAL 4.11, I can look into it on
Saturday, if my last patches didn't work for you?
I did not test it yet I'm afraid. :-/
It sounds like a critical issue for a 18.04 release. Is it?
Would that mean to skip t
Anton Gladky wrote:
Well, if we find a way to fix it within the next 2 weeks,
I think there is a chance to get it pushed into Debian->Ubuntu.
Regards
Anton
2018-02-08 15:23 GMT+01:00 Bruno Chareyre :
On 02/07/2018 05:35 PM, Janek Kozicki (yade-dev) wrote:
Regarding compiling yade with C
02-08 18:45 GMT+01:00 Bruno Chareyre
:
Hi Anton,
Thank you very much.
I'm not so sure what we are speaking about here.
Yade 2018.02a is the candidate source code for producing a binary
yade-stable in Ubuntu 18.04, correct (approximately)?
If yes, can we build yade-stable with CGAL at the mom
-- Message transféré --
De : "Bruno Chareyre"
Date : 9 févr. 2018 21:24
Objet : Re: [Yade-dev] Yade for LTS Ubuntu 18.04
À : "Anton Gladky"
Cc :
The current state is that Janek's patch may have problems for polyhedra. If
it's not fixed shortly my su
Gladky <mailto:gladky.an...@gmail.com>> napisał(a):
Yes, it should be OK.
Anton
2018-02-09 16:06 GMT+01:00 Bruno Chareyre
mailto:bruno.chare...@grenoble-inp.fr>>:
What is an appropriate system to try this? ubuntu 18.04 beta
is ok?
B
On
On Mon, Feb 12, 2018 at 1:22 AM Bruno Chareyre
<mailto:bruno.chare...@grenoble-inp.fr>> wrote:
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).
Fo
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 wanted
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 "undefined"
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 : yade-dev@lists.launchp
Hi Jérôme,
I am not in favor of removing some documentation, thank you for asking.
In my view such patch would be a regression. I don't understand the
motivation, see below.
On 02/21/2018 05:59 PM, Jerome Duriez wrote:
After seeing Yet Another Doubts on "young" meaning /
Ip2_FrictMat_FrictMat_
Hi Jérôme,
Thanks for pointing out what was missing. I tried to fix in [1].
Even though we all here are at ease with these models, I think the
"young questions" we still face (me, few days ago here) should
demonstrate there is room for improvement...
Hoping to avoid another
https://www.mail-a
Hi Robert,
Still a small thing to fix following [1] it seems, although it may only
impact old systems.
On ubuntu 14.04 with libsuitesparse-dev 1:4.2.1-3ubuntu1 it gives:
/FlowBoundingSphereLinSolv.ipp:100:6: error: ‘cholmod_common’ has no
member named ‘useGPU’//
// com.useGPU=1; //useGPU;/
O
the case. :)
Thanks
Bruno
Best,
Robert
On Fri, Feb 23, 2018 at 7:56 AM Bruno Chareyre
<mailto:bruno.chare...@3sr-grenoble.fr>> wrote:
Hi Robert,
Still a small thing to fix following [1] it seems, although it may
only impact old systems.
On ubuntu 14.04 with libsuites
Hi,
Every registered user of the wiki can upload on [1], I just accepted
your registration.
I suspect [2] can be accessed only via our intranet and cannot be open
for security reasons (Rémi may confirm).
It costs just a drag and drop for me to upload something there, feel
free to ask.
The m
Hi William,
Thanks for mentioning.
You can send compiler errors to yade-dev (are you member of yade-dev?
else I suggest you join) or even better to a bug report.
It is better to specificy revision numbers, to.
Your last revision [1] made it through the buildbot.
Do you still have the problem lo
Let us continue the discussion here on yade-dev, William is member.
Merge commits are painful, as you suggest Robert it applies the upstream
changes on the local trunk then it commits the merged code.
In the log it looks like reapplying the same changes, the problem is if
it's not reapplying exa
This being said I don't think the merge can be the cause of William's
compile error.
The question is why gcc can't find std::random_device.
Just weird.
B
/
/
On 03/09/2018 06:35 PM, Bruno Chareyre wrote:
Let us continue the discussion here on yade-dev, William is member.
Me
Hi Chao,
This is git's merge bubble, an expected behavior if you did not set
git's "autorebase" as indicated in yade install page.
I don't think it needs a revert, but please set autorebase for next commits.
Cheers
Bruno
On 04/07/2018 02:08 AM, Chao YUAN wrote:
Hi guys,
I guess I did something
Hi Jérôme,
It seems related to manipulating this python tuple as a c++ object.
First, I did not see any "[]" operator for tuples in boost documentation.
Second, even if it works I'm unsure it will automatically return the correct
type (a Vector3r), hence this syntax may not do what you think:
doub
Hi,
I agree to fix or remove.
I will not fix.
If no one else will you can remove. :)
B
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1625850
Title:
CapillaryTriaxialTest preprocessor broken
Statu
** Changed in: yade
Assignee: (unassigned) => Jérôme Duriez (jduriez)
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1625850
Title:
CapillaryTriaxialTest preprocessor broken
Status in Yade:
** Changed in: yade
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1474956
Title:
Clump::updateProperties discretization not defined robustly
Status in Yade:
Co
** Changed in: yade
Importance: Medium => Wishlist
** Changed in: yade
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1112689
Title:
ompThreads attribute not
Probably fixed by time.
** Changed in: yade
Status: New => 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/1383859
Title:
Some FlowEngine methods take points as tuple while othe
was not declared in this scope
--
___
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
Email too brief?
Here's why! http://emailcharter.org
__
So old that I didn't bother getting back to it, but if someone wants to
implement it... hence the wishlist :)
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1474956
Title:
Clump::updateProperties d
Recherche / Research Associate
Irstea, RECOVER
3275 route de Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE
+33 (0)4 42 66 99 21
On 22/05/2018 13:22, Bruno Chareyre wrote:
Hi there,
I see the buildbot fails to cmake/find those two libs. This is the
main reason of current failure. Of course m
** Changed in: yade
Status: New => Opinion
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1324191
Title:
boost::python::arg maybe a bit long?
Status in Yade:
Opinion
Bug description:
W
Closing: the doc is no longer a duplicate.
Actually it reads "Final version and documentation will come before the end of
2014."...
B
** Changed in: yade
Status: New => Fix Released
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to
Wishlist: make it more explicit in the doc (maybe even return a warning
when changing angular velocity of aspherical objects).
** Changed in: yade
Status: New => Opinion
** Changed in: yade
Importance: Undecided => Wishlist
--
You received this bug notification because you are a membe
Hi,
If solid volume is changed you should use
TriaxialStressController.updatePorosity [1]
It would not be good to recalculate solid volume everytime by default.
Bruno
[1] https://yade-
dem.org/doc/yade.wrapper.html?highlight=updateporosity#yade.wrapper.TriaxialStressController.updatePorosity
**
Hi,
I also browsed a little and could not find any big change (provided that
replacing "print 'hi'" by "print('hi')" can be automatic).
It doesn't mean no problem will emerge though, on needs to try. For a IT
student internship the problem would be that if things go well the job
could be do
Thanks for reporting.
The strange part is that numpy 1.14 is still supporting bz2 according to the
documentation.
Could someone confirm "ValueError: bz2 text files not supported in python2" on
his system with the following code:
from yade import plot
plot.reset()
plot.addData(a=1,b=11,c=21,d=31)
@Jérôme
And you have numpy 1.14?
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1774065
Title:
doctests fail with numpy 1.14
Status in Yade:
New
Status in Debian:
Confirmed
Bug description:
Bug Watch released a fix?... how?
B
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1774065
Title:
doctests fail with numpy 1.14
Status in Yade:
New
Status in Debian:
Fix Released
Bug descript
Thanks for firsthand information Václav, It should be very helpful.
I was not sure something like "str/bytes distinction" would be involved,
finally it is...
Bruno
On 06/05/2018 09:06 PM, Václav Šmilauer wrote:
Hi guys, for inspiration, you can check out commit
https://github.com/woodem/woo/c
Hi, just a comment (to yade-dev):
There is little inheritance between functors at the moment, mainly
because it is a bit less trivial (but not so difficult) to implement
than simple data inheritance. There is some type-casting involved if you
want to re-use parent::go() directly since it will n
re that no "file not found" will
occur. For instance, every mwe.py should be compatible with:
mkdir MWE
cp mwe.py ./MWE/mweTest.py
cd MWE
/path/to/yade mweTest.py
rm -rf ../MWE
Other suggestions?
Bruno
[1] https://answers.launchpad.net/yade/+question/670501
--
___
Brun
If there is it is very well hidden.
Bruno
Robert
Le ven. 29 juin 2018 à 12:33, Bruno Chareyre
<mailto:bruno.chare...@3sr-grenoble.fr>> a écrit :
Hi Yade devs,
When I try to save a few minutes to answer some questions I very ofen
find myself clicking here and there t
ds realistic to ask users to avoid
extra files in their MWE, and do not have any other suggestions..
Jérôme
--
Chargé de Recherche / Research Associate
Irstea, RECOVER
3275 route de Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE
+33 (0)4 42 66 99 21
In **my opinion**:
1) Shop functions should be C++ only, not returning or accepting
boost::python stuff. The python stuff (like converting std::vector to
python tuple/list or modifying input/output like [1]) is (should be)
the reason for py/_utils existence.
2) In the same way, there shou
-- Forwarded message -
From: Bruno Chareyre
Date: jeu. 19 juil. 2018 10:46
Subject: Re: [yade/trunk] remove pack.particleSD and variants, unmaintained
and deprecated by makeCloud (functions kept temporarily but returning
error) (d8d789f)
To: yade/trunk <
re
e-mpi
--
___
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
Email too brief?
Here's why! http://emailcharter.org
___
Mailing l
Hi Jérôme, I discover the situation with your email and I agree that it can
be improved (looks like).
A good fix would need to clarify the meaning (or is it already clear that
fixed == !dynamic everywhere?), then it is easy to make both accepted
through aliasing.
Removing one of the two seems awkwa
Hi,
You can impose the velocity of the piston as b.state.vel=(x,y,z) after
setting b.state.blockedDOFs='xyzXYZ'. You then make it zero in the begining
and change for something else at some point.
TranslationEngine makes this simple thing excessively complex in my
opinion. I would suggest to forget
Hi Jan, thx for reaction. I agree that on/off for multiple bodies is
convenient.
Then maybe only example should be touched? I wonder what leads users to
translation engine while iirc the general doc describes controlling DOFs
properly.
B
Le sam. 28 juil. 2018 09:19, Jan Stránský a
écrit :
> Hi
Hi Jérôme,
This change would be sensible, seems to me (especially regarding your
second bullet point).
Note that pair would make more sense than a vector<>.
I would point out that the implementation of this function looks sloppy in
various other ways:
- dereferencing body pointer without checking
will be successfull and can support the project a
> bit.
> Best regards
> Alex
>
> -Ursprüngliche Nachricht-
> Von: Yade-dev [mailto:yade-dev-bounces+alexander.eulitz=iwf.tu-
> berlin...@lists.launchpad.net] Im Auftrag von Bruno Chareyre
> Gesendet: Donnerstag, 19. Juli
Hi there,
An effective N-threads implementation of distributed memory parallelization
is achieved after minor changes in the source code and some refactoring of
the previous 2-threads script.
You can find the concrete example testMPIxN.py with comments in [1].
The 10x slow down I mentioned previou
Hi all,
Preliminary content here: https://yade-dem.org/wiki/Howtoask
Please feel free to improve, and paste the link in launchpad whenever it
applies.
Cheers
Bruno
On 29 June 2018 at 16:24, Bruno Chareyre
wrote:
> I did not mention it explicitly but I think improving "How to ask&quo
Hi Jan, I'm moving this to yade-dev for a particular point.
On 08/30/2018 04:08 PM, Jan Stránský wrote:
It is just implementation choice, the force acting on clump itself is
computed when needed from clump members [2,3], but is not stored..
[1] https://github.com/yade/trunk/blob/master/pkg/dem/
Hi Robert,
It sounds good, except that I would increment kNorm directly instead of
incrementing a counter.
Logic:
- two adjacent cracks cumulate their conductivity: Ktot = K1+K2
- if you accumulate aperture you get (a1+a2)^3 instead of (a1^3 +
a2^3), it will increase to much it seems.
I know
Random results (we are speaking of "yade -j1" right?) usually come from using
null pointers or uninitialized variables.
Running yade with valgrind (and debug symbols) would probably tell more.
In the case neverErase=true, I would double-check what happens if the
interaction becomes active again.
On 09/03/2018 11:34 AM, Luc Scholtes wrote:
This is a bit tricky but we have to keep in mind that stress induced
cracks are not "connected" one with another up until a fair amount of
them is present inside the medium (crack coalescence can be observed
sometimes only after 70% of the peak str
Hi Jérôme,
It sounds like a good idea to provide a pointer to CMakeLists.txt in
this paragraph(*) yet there is no reason to remove the current doc,
better update it.
Removing doc to show people they can read source code is not a very good
direction in general, 99% of yade users have no interest
> OK... We need neverErase=True for DFNFlow so what should we do? Create
a functor to erase the interactions?
No there is no need for an extra functor. The place where erasing is triggered
is Law2::action() (based on the bool returned).
I don't think we really need neverErase=True for DFNFlow.
>Can we have 2 interactions (in the interaction container") which
concerns the same particles pair?
Impossible.
> keep record of the crack aperture [...] during the whole duration of
the simulation.
Saying that we erase when distance > 10*radius would surely enough keep it
alive for the whole (
Hi there,
We were considering it recently with Rémi but I was unsure if it was
out-of-box or not, then we postponed (Rémi is no longer at 3SR,
thanksfully he did not disapear completely but he may be less available).
@Rémi, can you please set the repo? others can then test and fix.
On another
Yes, pleeease! :)
Don't you have commit rights anyway?
Bruno
On 10/11/2018 12:07 PM, Alexander Eulitz [Eugen] wrote:
I will prepare a pull request if you like.
Cheers
Alex
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@l
Hi Alex,
It sounds relevant indeed, however the possible "push_back" would have to be
done inside boost serialization, and I doubt we need to dig that deep to
understand the problem.
I can't reproduce the problem on ubuntu 16.04 actually (2018-09-26.git-0a2abea
or yadedaily), your script gives:
ted
** Changed in: yade
Assignee: (unassigned) => Bruno Chareyre (bruno-chareyre)
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1604266
Title:
yade not working prpoperly on Ubuntu/Kubuntu 16.04
Sta
Hi Raphaël,
Let's use yade-dev for this sort of things.
Sorry if I broke something, I was actually about to write to you when
commiting.
The check-script is apparently not using timeStepper since "yade
--check" still gives the expected result:
/###//
//running:
Hi Vasileios,
Periodicity is relatively easy to implement since it only has to deal
with periodicity of interactions.
You should grep variable "shift2" in the source code to see how
interactions are made periodic.
Bruno
___
Mailing list: https://l
Hi,
Disk space problem is indeed the (known) cause of current freezing.
Rémi mentioned that to me a few weeks back. Not sure he was aware of
this "too many subfolders" problem yet.
Sorry for inconvenience.
Please be patient. :)
Bruno
On 11/5/18 1:00 PM, Jerome Duriez wrote:
Hi Robert,
My unde
5. (The
script run well with viscEl = False as the damping is not fundamental
in this situation where the restitution coefficient is not too small).
Tell me if you can reproduce that, and if you see any possible reason
for such a big change.
Cheers,
Raphael
Le 17/10/2018 à 18:42, Bruno C
Hi Robert,
On 11/9/18 5:07 PM, Robert Caulk wrote:
You might also be unsurprised to find out that "error" is one of the
least commonly used words for launch pad questions ;-).
I thought it was a joke since I see the word appearing much too often,
then I checked the stats... and that's actual
Fixed, thanks!
https://github.com/yade/trunk/commit/af1f41906b6ccf077dee456bc8f3f8747c318b0a
** Changed in: yade
Assignee: (unassigned) => Bruno Chareyre (bruno-chareyre)
** Changed in: yade
Status: New => Fix Released
--
You received this bug notification because you are a
** Changed in: yade
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/599743
Title:
static class attributes are not documented by sphinx
Status in Yade:
Won't Fi
** Changed in: yade
Status: Incomplete => Invalid
--
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 registered
Fixed following either Vaclav's #3 (thanks) or 'isinstance' (recommended
method).
https://bugs.launchpad.net/yade/+bug/1455621
** Changed in: yade
Assignee: (unassigned) => Bruno Chareyre (bruno-chareyre)
** Changed in: yade
Status: New => Fix Released
--
No longer a bug, closing.
** Changed in: yade
Status: New => Invalid
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1267164
Title:
Fails to build from yade-daily sources
Status in Yade:
stable on recent years).
Bruno
On 11/12/18 12:50 PM, janek_li...@wp.pl wrote:
Wow, very interesting. Thank you! :)
On 12 Nov 2018, 10:44 +0100, Bruno Chareyre
, wrote:
Hi Robert,
On 11/9/18 5:07 PM, Robert Caulk wrote:
You might also be unsurprised to find out that "error"
Hi,
What would be a possible fix for this?
I wonder if it is something to fix system side or really on yade/cmake side.
Bruno
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1802913
Title:
Find Mod
> the choice of the python environment to use
> for generating and using Yade has to be defined in the option of cmake
That's what I think indeed. Either "export" variables before cmake, or define
system-wide priorities among the different versions of library (possible in
ubuntu, maybe not in op
Hi Jérôme,
I don't know, but I guess they were introduced independently by
different authors.
I actually don't know why we would need to define tolerance at all,
unless in very specific cases.
For instance I judge that a line like this (ViscoelasticPM.cpp) is not
only useless but actually wro
On 11/15/18 5:16 PM, Jerome Duriez wrote:
I'd thus propose to get rid of ZERO_TOLERANCE at least, replacing with
EPSILON where it is currently used.
Is it worth it?...
(As for me, tolerance would for instance be useful to know when an
increasing value (x, increasing from x0 < a) can be dete
101 - 200 of 2047 matches
Mail list logo
