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
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
**
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
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
** 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:
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
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
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
___
Mailing
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
** 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
** 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:
** 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:
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
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:
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
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.
Merge commits
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
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
it is the case. :)
Thanks
Bruno
Best,
Robert
On Fri, Feb 23, 2018 at 7:56 AM Bruno Chareyre
<bruno.chare...@3sr-grenoble.fr
<mailto:bruno.chare...@3sr-grenoble.fr>> wrote:
Hi Robert,
Still a small thing to fix following [1] it seems, although it may
only impact
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;/
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
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 /
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 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
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
On Mon, Feb 12, 2018 at 1:22 AM Bruno Chareyre
<bruno.chare...@grenoble-inp.fr
<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+
...@gmail.com
<mailto:gladky.an...@gmail.com>> napisał(a):
Yes, it should be OK.
Anton
2018-02-09 16:06 GMT+01:00 Bruno Chareyre
<bruno.chare...@grenoble-inp.fr
<mailto:bruno.chare...@grenoble-inp.fr>>:
What is an appropriate system to try thi
-- Message transféré --
De : "Bruno Chareyre" <bruno.chare...@3sr-grenoble.fr>
Date : 9 févr. 2018 21:24
Objet : Re: [Yade-dev] Yade for LTS Ubuntu 18.04
À : "Anton Gladky" <gladky.an...@gmail.com>
Cc :
The current state is that Janek's patch
source/cgal
Anton
2018-02-08 18:45 GMT+01:00 Bruno Chareyre
<bruno.chare...@grenoble-inp.fr>:
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 (approximat
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 <bruno.chare...@grenoble-inp.fr>:
On 02/07/2018 05:35 PM, Janek Kozicki (yade-d
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
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:
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
** 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
** 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:
** 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
"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
** 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
** 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:
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: "<
** 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:
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:
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
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
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
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
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.
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
** 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
>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
> 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
>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]
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
multi-threaded oedometer.py with compressible flow on/off to show
incorrect pressure) :
# -*- coding: utf-8 -*-
#*
# Copyright (C) 2010 by Bruno Chareyre *
# bruno.chareyre_at_g
On 11/29/2017 07:31 PM, Anton Gladky wrote:
The question is, how long does Yade want to support Ubuntu 14.04 LTS,
where QT5 version of libqglviewer does not exist. Another option is to
provide backport of libqglviewer-qt5-dev for Ubuntu 14.04, document it
as a mandatory package for Yade and
On 11/29/2017 03:25 PM, Janek Kozicki wrote:
I hope that you have, Bruno, among those tests some related to PFV
and CGAL :)
Hi Janek,
Yes we have, thanks. :)
DEM-PFV-check.py depends on pfv+cgal+TesselationWrapper+openblas+cholmod
(at least...). You can use it as a test if it helps.
I
--
___
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 list: https
Public bug reported:
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 fact that
On 11/07/2017 06:47 PM, Janek Kozicki wrote:
I just feel a little uneasy about cross_product of two
(sphere-sphere) pairs ;)
Well... after admitting that spheres can be mutually orthogonal (which
is really the case) cross product is fine... :)
But you are right, here cross product is
I can confirm my previous message: all the changes should compile with
older CGAL.
The only place where an ifdef is needed maybe is when including
"constructions_on_weighted_points_cartesian_3.h".
Bruno
On 11/07/2017 11:04 AM, Bruno Chareyre wrote:
Awesome.
Whenever implicit conve
Awesome.
Whenever implicit conversion from wp (weighted point) to bp (bare point)
is used in current code it is just because there is no reason to type
v->point().point() when we can write simply v->point(). However, what we
need is really a bp, so the v->point().point() syntax reflects more
On 11/03/2017 09:13 PM, Anton Gladky wrote:
I will probably remove libcgal-dev dependency from the package right now
not to block CGAL migration. If we find a solution, it can easily be resumed
later.
Sounds good. Thank you Anton.
B
___
Mailing
Hi Janek,
I don't think I'll be able to test this very quickly myself. Based on
the compile logs the evident problem is [1].
Which sounds like a trivial issue. However, it may be the case that they
really changed the design of the so-called geometry kernel (as suggested
by [2]) and that it
fail if new warnings were introduced in the last commits.
Something like:
cmake -DCMAKE_CXX_FLAGS="-Werror -Wall" ../src/to/yade
Of course one need to fix all warnings before switching it on hardly.
Anton
2017-11-02 13:38 GMT+01:00 Bruno Chareyre <bruno.chare...@3sr-grenoble.fr
n yade-dev.
Cheers
Bruno
--
_______
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://emailc
Hi there,
Just to let you know, there was an interesting failure of a regression
test [1] after William fixed the labels of matrices [2].
The improvement was interpreted as a regression because the doctest
string of the function addData() has an expected output hardcoded (see
[3]), and it did
#ifdef CHOLMOD_GPU should do the trick, I find it False after cmake.
B
On 09/28/2017 05:24 PM, Robert Caulk wrote:
Oh yes, I will fix this today. Thank you for pointing this out!
On Thu, Sep 28, 2017 at 1:53 AM Bruno Chareyre
<bruno.chare...@3sr-grenoble.fr
<mailto:bruno.chare.
And no, Pages & Years is not the issue (the ordering of items is
completely arbitrary, if that's what you suggest).
I'm checking the problem, no worries (missing comma or forbidden symbol,
most likely).
Bruno
On 09/28/2017 11:22 AM, Bruno Chareyre wrote:
You are absolutely right, I also
l
*Phone*: (+31) 030 2532497
*Website*: http://www.uu.nl/staff/TSweijen/0
----
*From:* Bruno Chareyre [bruno.chare...@grenoble-inp.fr]
*Sent:* Wednesday, September 27, 2017 7:40 PM
*To:* yade-dev
*Subject:* Fwd: [Yade-dev] buildbot fail
to compile this line optionally.
What do you think?
FlowBoundingSphereLinSolv.ipp:98:6: error: ‘cholmod_common’ has no
member named ‘useGPU’
com.useGPU=1; //useGPU;
Bruno
p.s. Thanks a ton for discovering and implementing this GPU thing!
--
_______
Bruno Chareyre
Associate Professor
ENSE³
Hi Thomas,
The buildbot was down for a couple days, and now back to work.
It found a problem in your recent revision it seems, could you please
have a look (you can see compilation outputs by following the link)?
You need to cancel your PhD defense if the code will not compile. ;)
Cheers
Bruno
367
*From:* Yade-dev
<yade-dev-bounces+jerome.duriez=ucalgary...@lists.launchpad.net> on
behalf of Bruno Chareyre <bruno.chare...@grenoble-inp.fr>
*Sent:* July 20, 2017 5:08 AM
*To:* yade-dev@lists.launchpad.net
*Subject:* Re: [Yad
Thanks!! :)
Bruno
On 08/21/2017 01:58 PM, Rémi Cailletaud wrote:
Hi,
should be fixed now. Sorry for the delay !
++
rémi
Le 07/08/2017 à 09:38, Bruno Chareyre a écrit :
A server error most likely, failures started without any change in
the sources. Grenoble univ is closed (yes...) for two
A server error most likely, failures started without any change in the
sources. Grenoble univ is closed (yes...) for two weeks, and Rémi is
probably in exotic situations. We'll need a bit more patience.
Bruno
Le 7 août. 2017 02:17, "Robert Caulk" a écrit :
> Does anyone
Hello,
No, I'm not announcing the next yade workshop. :-/
Following the 1st workshop in Grenoble, we have been considering the
possibility of having a second workshop in Freiberg (Anton's place).
With Anton flying to a different sky this will not happen.
I am writing this message as a call for
On 06/28/2017 05:58 PM, Jerome Duriez wrote:
Now, it's clear this list is just not perfectly updated (if already
existing) at compilation time.
There is simply no list. It goes through the files in lib/.../checks and
run them one by one.
In your case removing from source dir did not
Hi,
I would also call the comment in ViscoFrictPhys "irrelevant", no problem
to remove it.
Bruno
On 06/28/2017 12:13 AM, Jerome Duriez wrote:
Hi,
As said elsewhere, I'm removing
Law2_ScGeom6D_NormalInelasticityPhys_NormalInelasticity from trunk.
The latter is mentionned in the doc of
Hello Jérôme,
What is in the Git trunk and what is/not in your build folders are
independant things.
As soon as the file is removed from trunk nobody will check it out, then
of course nobody will have to remove it from a fresh build.
The behavior you got is that of cmake, independently of git.
On 06/16/2017 11:02 AM, Bruno Chareyre wrote:
@Anton, you are the branch owner on launchpad, I'm not sure I have
rights to fix this problem, at least I don't find anything related to
setting the git import.
Wait a sec. I have enough rights it seems.
I just created a new branch to try the git
On 06/16/2017 11:02 AM, Bruno Chareyre wrote:
@Anton, you are the branch owner on launchpad, I'm not sure I have
rights to fix this problem, at least I don't find anything related to
setting the git import.
Wait a sec. I have enough rights it seems.
I just created a new branch to try the git
Hi,
Thanks for mentionning this, I didn't realize.
This discussion [1] suggests that the import is corrupted by a gpg
signed push. Consistently, the first failed import appears as a
"verified" push on github[2], unlike every others.
There is apparently no solution to this bug. Now we have a gpg
Hello,
The import has been approved and an import will start shortly.
--
https://code.launchpad.net/~yade-pkg/yade/git-trunk
You are receiving this email as you are subscribed to the branch.
___
Mailing list: https://launchpad.net/~yade-dev
Post to
Hello,
Thank you for detailed reply. Indeed, I understand the periodic annulus
does not need to be zero-based in principle. I'll consider removing the
clamping (after triple-checking that it is effectively harmless... it
was hard enough to spot the bug previously).
On 06/01/2017 05:30 PM,
iling list of yade but I do not know if you prefer that I send the
flyer to you and later you send it to the community. The first call will
be sent in few days.
Merci bien,
[...]
Scientific committee
[...]
[...]
...
--
_______
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
B
of Thu, 4 May 2017 10:05:33 +0200)
Hi,
For now, the buildbot compile with all the default options, only
disabling qt5.
Should we change that ?
Bruno Chareyre said: (by the date of Wed, 3 May 2017 10:40:58 +0200)
(granted that we don't have the ressource to build every possible
combinations
Hi,
Every combination must compile and the error needed a fix (now fixed,
thx!), yet the question of which combination the buidlbot should build
(granted that we don't have the ressource to build every possible
combinations) is valid.
I would think it needs to include as many features as
ding: utf-8 -*-
#*
# Copyright (C) 2010 by Bruno Chareyre *
# bruno.chareyre_at_grenoble-inp.fr *
#*
# This program is free software; it
** Changed in: yade
Status: New => 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/1685735
Title:
Exception KeyError
Status in Yade:
Won't Fix
Bug description:
I run
Is there a problem apart from the "KeyError" message?
Do you get the expected results from the batched jobs?
There is usually no need to exit/stop yade scripts. You can simply use
"while(...): O.run(..)" if you have a conditional stop.
Bruno
--
You received this bug notification because you
.
Cheers.
Bruno
[1]
https://github.com/yade/trunk/commit/c7c8e6f62d452c81a31415f05a12587a6cc8c452
--
___
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
Hi Janek,
In super-super short, welcome back!! :)
More later.
Bruno
On 04/13/2017 09:10 PM, Janek Kozicki wrote:
Hello everyone,
I am going back to work on yade, and I have some interesting plans.
This also entails one question :)
Sorry for goofy subject, I hope it catches your attention.
In
it please
do it in one commit to have later an opportunity to revert it
by "git revert". Thanks!
Anton
2017-04-05 10:53 GMT+02:00 Bruno Chareyre <bruno.chare...@3sr-grenoble.fr>:
My impression was that isActive was used in these functors in relation with
some SPH coupling. Maybe not.
F
is used also in ViscoelasticPM and LudingPM and
ViscoelasticCapillarPM.
Best regards
Anton
2017-04-04 11:55 GMT+02:00 Bruno Chareyre <bruno.chare...@3sr-grenoble.fr>:
Dear Anton,
Could you tell us the status of the YADE_SPH feature and if there is a
chance to see it further develo
{
...
bool isActive;
--
___
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
and there was a
chance for yade to be dropped from the next stable Debian.
If it is fixed already, I will resurrect PDF file later after release.
Best regards
Anton
2017-03-28 17:50 GMT+02:00 Bruno Chareyre <bruno.chare...@3sr-grenoble.fr>:
Finally the buildbot is back and the doc is uploaded ([1],
out.
On Mon, Mar 27, 2017 at 9:30 AM, Bruno Chareyre
<bruno.chare...@3sr-grenoble.fr
<mailto:bruno.chare...@3sr-grenoble.fr>> wrote:
The issue should be fixed now, but there seem to be also
(again...) a problem with the buildbot now.
Hopefully we
uno Chareyre wrote:
Oooops. The link [1] is actually not the build coming after last
(Robert's) commit. It is the one after my initial commit of the EC2
guide. Blame me!
I'll have a look.
Bruno
On 03/27/2017 02:05 PM, Bruno Chareyre wrote:
Dear all,
Rémi just re-activated the email notificati
Oooops. The link [1] is actually not the build coming after last
(Robert's) commit. It is the one after my initial commit of the EC2
guide. Blame me!
I'll have a look.
Bruno
On 03/27/2017 02:05 PM, Bruno Chareyre wrote:
Dear all,
Rémi just re-activated the email notifications of compile
vices//You can read about some of the other codes we've analysed here //https://pop-coe.eu/target-customers/success-stories"/
Is there any volunteer for trying this?
It is probably interesting try on both standard desktops and HPC servers.
Cheers
Bruno
On 03/14/2017 03:50 PM, Bruno Char
Public bug reported:
The documentation of Ip2_JCFpmMat_JCFpmMat_JCFpmPhys contains a
reference [Duriez2016]_ this label does not exist. I found that through
the compile warnings. Can you please check Jerome?
** Affects: yade
Importance: Undecided
Status: New
--
You received this
201 - 300 of 1689 matches
Mail list logo