I need the incremental formulation for the normal force in the contact
law. Could you tell me how to do that?
What is the problem exactly? You have the equation but you don't know
how to implement it, or you have no equation?
Why do you need the incremental formulation? Do you have
Do you have irreversible non-linearities?
I would need the incremental formulation because I need to make
distinction between loading and unloading stage.
If the law is picewise linear, it is still possible to write it with
total Un (e.g. storing an internal Un_max). If not, you are in
message:
Re-write of CohesiveFrictionalMat with YADE_BASE... macro.
It is not one of my files but I wanted to use it with Python, so I did it.
I hope noone will be offensed.
modified:
pkg/dem/DataClass/Material/CohesiveFrictionalMat.cpp
Václav Šmilauer a écrit :
Do you think other classes will go the same way if I keep doing nothing? ;)
I thought you had already started with TT related classes, when I was
in Grenoble? I doubt though that it will do itself by itself ;-)
Oh, yes, I fixed and commited a few classes
BTW anyone still using PositionOrientationRecorder?!
I don't know if somebody ever used that. Nobody here for sure.
Bruno
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsubscribe :
Global sounds more appropriate for boundary conditions for me, but it
is just matter of taste.
A difference between partial engines and TSController is that TSC is
looping on all interactions and bodies for some tasks (defining
boundaries stiffness, computing unbalanced force,...), even if it
: https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
potential problems in CFCL, but I didn't fix
them in CFPM). It also result in naming conflicts : how to reflect the
difference between a CF contactLaw and a CF particleModel?
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9
Please fix that.
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
___
Mailing list: https://launchpad.net/~yade-dev
Sorry, I didn't notice revno in the original post. It is fixed now
except for preprocessors.
Bruno
Bruno Chareyre a écrit :
Only CohesiveTriaxialTest and TriaxialTestWater do not register.
Perhaps I need to remove the other ones? I though they were removed
already (renamed
Hi,
I was wondering recently why we need a forceReseter just to reset forces...
Can't we do that in Newtons law? Or maybe interaction dispatcher?
Bruno
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Fix unchanged name (Bruno, do you use scripts/rename-class.py, right?
https://www.yade-dem.org/sphinx/prog.html#renaming-class)
Yes, I used the script (thanks for it btw). Appart from the
HydraulicForceEngine conflicts (I though I fixed them but not all
apparently), I don't understand
Hi Luc,
I just fixed (r2168) your comment pointing to yade/extra for the
capillary files. The files are not in trunk, they have to be downloaded
from the website, as explained in (btw, a LOG_ERROR would be better than
cout) :
cout WARNING: cannot open files used for capillary law, all
://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
___
Mailing list: https://launchpad.net
I do not see this bool doing anything in the code atm,
You are right. I removed it.
The 2D is doing something though. I never used that and I'm not sure
how it works, but Janek did IIRC.
Bruno
___
Mailing list: https://launchpad.net/~yade-dev
It is fixed in this class and others too.
equilibriumDistance is completely removed in the same commit.
Bruno
Please fix hyperlink syntax in docstrings (see e.g.
https://www.yade-dem.org/sphinx/yade.wrapper.html#yade.wrapper.TriaxialTest.autoUnload ).
The :yref: etc roles (as they call it)
No symbol info in current context...
I suspect a missing virtual in a cpp, I'll check later. Thanks for
notifying.
Bruno
Franck Lominé a écrit :
** Attachment added: log.txt
http://launchpadlibrarian.net/45045660/log.txt
--
___
Bruno Chareyre
Associate Professor
___
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
Grenoble INP
Lab
))//plastic
disp.
What will happen if two threads increment the value at the same time?
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
: https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
___
Mailing list: https
FOREACH is not hiding any OPENMP?
B.
Václav Šmilauer a écrit :
Thank you, I'll look at this template.
I realize using the FOREACH macro by default everytime we have a loop is
perhaps not a good idea. What about this loop in GSTimeStepper, with
stiffnesses a class member?
FOREACH(const
I get it. So, it would be a good idea perhaps to reduce damping effects
on DOF i if vel[i] is close to 0 (perhaps using some sort of
non-dimensional proportionality factor)?
It also suggests applying damping separately on each DOF (not like in
Hentz) is better, regarding this feature, since the
I have a bunch of compile errors in r2184. A short part is below
(starting from the beginning).
Bruno
g++ -o /home/bruno/YADE/build-last-opt/plugins7.os -c -pipe -Wall
-frounding-math -O3 -fopenmp -O3 -march=native -fPIC -DMINIWM3
-DYADE_CGAL -DYADE_LOG4CXX -DYADE_OPENGL -DYADE_OPENMP
is it THAT difficult to check that? (what I read recently, using
typeid(Sphere)==typeid(*b-shape) might be faster than dynamic_cast).
Where sphere is a pointer to an existing Sphere?
typeid replaces getCLassIndex?
Not THAT difficult, but given my number of not-so-difficult TODO's, with
is it THAT difficult to check that? (what I read recently, using
typeid(Sphere)==typeid(*b-shape) might be faster than dynamic_cast).
Where sphere is a pointer to an existing Sphere?
typeid replaces getCLassIndex?
Ah, no... it must be the class Sphere itself obviously?
Is there really
There is some nonsense being compiled. As is
InteractionDispatcher::action() were missing the closing brace, creating
local class InteractionDispatchers::action()::GenericSpheresContact,
which should be separate. Are you use you have clean source?
You found it man! Thanks a lot.
It was a
To be more precise, we could compute incrementally the work done by
the springs in the systems more than the elastic energy. Almost in the
same way as we get the dissipated energy due to friction (it is not
too difficult to make distinction between work and energy if we think
that work is
Hi,
I've been looking into OpenMPAcumulator.
Questions :
- Can I register the attribute OMPAc plasticDissipation?
- Assuming the answer is no : I need to register a storage variable Real
plasticDissipation2 for initialisation, so that saving/loading will not
reset plastic energy. The problem
Wouldn't it help registration if OpenMPAccumulator was inheriting from
template type T?
B.
Bruno Chareyre a écrit :
Hi,
I've been looking into OpenMPAcumulator.
Questions :
- Can I register the attribute OMPAc plasticDissipation?
- Assuming the answer is no : I need to register a storage
No, the accumulator is not serializable (and is not meant to be, it is
just a special increment-only variable). You could, though add a private
bool doReset, which would be an additional (optional) parameter to the
ctor (True by default) which would prevent reset() from doing anything.
That
Real bar=foo;
Does that solve your problem?
No, I don't think so. I know implicit conversion is the way to get the
sum of threads, but the problem is there is nowhere to type such
bar=foo. It can't be done in functor::go or functor::ctor, obviously.
It should be somewhere
You can also define functor member function which will get the value on
request. (wrap it in python if you need)
Yes, this is what I did for now (not commited). Using callbacks would be
complex in that case and it would imply performance hit (impossible to
use local variables defined in
Corresponding output (after fix). It looks better :
trialFs.norm(): 36.0967 vs. maxFs: 24.6416 Fn: 281.663 ks: 341874
tanFric: 0.0874861
displacementT() before slip: 0.000105585
displacementT() after slip: 7.2078e-05
corrected trialFs: 12.4187 -15.884 -14.1663
Bruno Chareyre a écrit
Do you confirm Vaclav, so I can I commit?
B.
Bruno Chareyre a écrit :
Corresponding output (after fix). It looks better :
trialFs.norm(): 36.0967 vs. maxFs: 24.6416 Fn: 281.663 ks: 341874
tanFric: 0.0874861
displacementT() before slip: 0.000105585
displacementT() after slip: 7.2078e-05
: https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
There is no Eigen/Core* on my system, I think I can't compile the
current trunk since wm3 feature doesn't skip the check below.
B.
Bruno Chareyre a écrit :
scons :
Checking for C++ header file Eigen/Core... no
Should I install something (no libeigen2-dev in my distro), give a
path, forget
Václav Šmilauer a écrit :
Do you confirm Vaclav, so I can I commit?
OK, I double-checked on paper and you're right. I makes me feel a little
uneasy; don't dare to ask a question on this at the defense ;-)
Huh!!? what is the problem? You used those equations in cpm law too?
Thanks
Yeah, I got a banana too, and compilation went to plugin24 in the
meantime... (matter of days before I get a decent pc).
the answer while staring at a banana: since the stress _is_ right after
the slip (as it is computed independently), the force is right as well.
COOL!
Yes, I wouldn't have
2) Why do we need to continue if fn==0?
IIRC Bruno told me that was to avoid contacts that transmit no force,
even if they have non-zero nominal stiffness. Exact zero will be there
for interactions that really had no force at all.
I am not completely persuaded on that, since most likely
I have one big guess. How can this formulation being incremental
using trialForce? Let's take a simple case: normal force is set to
a constant value. Then say that trialForce will increase. In this
case shearForce is the same since normal force is as well (like
maintaining
If you agree could you commit it, please? Thanks.
Oh, sorry, I forgot that point... :-/
I'm sending you the sources, because I have also diffs for the OPenMP
plastic accumulator and I need to compile before commiting (I'm already
compiling another trunk and it will take time).
I will commit
I don't get why you changed this, just for the norm()?. It breaks my
code.
It's ok. Unless I made a mistake it doesn't change anything in you code since I didn't
modify the original function. The new function has the only puprpose to be faster, it is
consistent to remove this norm().
I'm worrying about that too. It needs some discussion, as we put weights
a bit differently sometime, when we define what is better. :)
For instance, I fear oversplitting because it is so hard for somebody to
read the code.
PS I think the way both Dem3DofGeom and ScGeom currently work is not
Oh, you are right. It is a problem. I'll think about it.
You wrote the throw in the function in Dem3DofGeom; I assume you know
what it does... Unless you did cutpaste of the code, which you know
what I think about.
throw means throw, and implies it has to be implemented in derived
(btw, a general question : why computing distances for energy?
can't we
simply use cross products between force and disp. vectors?).
distance*|F|=work (|F| is already known, it is radius of
plasticzone for
given sigmaN)? If you do cross product, then you have to
Regardless whether someone uses it or not now, that's the API you have
to implement, or don't put it in the API at all (make it a method of
Dem3DofGeom_SphereSphere and cast to that type in your Law2 thing).
Casting was what I wanted to avoid, it was the (bad but temporary)
reason for the
Don't you refer to a months-old version of ScGeom? ScGeom has members!
If you mean updateShearForce...
Speaking about that...
I was about to document ScGeom a bit more when I realized I don't
understand what updateShear is for. I thought it was for total
formulation but it is not
For me, there preferred way would be to add the new method (everywhere),
while keeping the old one at least for some time. (I use it in code
which is not in trunk, and it should stay compatible until I update it
everwhere as well).
Ok, I'll do that then.
I'm glad to hear you worry about
No sorry I found it.
But timeStepOutputInterval is useless.
True. Could you remove it please? :)
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
1. Bruno: fix CohesiveTriaxialTest and TriaxialTestWater, it is still
not registered properly. Last time I told you there was no hurry, now I
think that is not true anymore.
https://bugs.launchpad.net/yade/+bug/544857
Ok.
Bruno
___
Mailing
Oh dear, TTWater segfaults now, without any change on my side. :(
It is not the same problem as in CFTest unfortunately...
B.
Bruno Chareyre a écrit :
1. Bruno: fix CohesiveTriaxialTest and TriaxialTestWater, it is still
not registered properly. Last time I told you there was no hurry, now
Fixed! It was the same undefined scene, but in ElasticContactLaw, not
in capillaryLaw.
B.
Bruno Chareyre a écrit :
Oh dear, TTWater segfaults now, without any change on my side. :(
It is not the same problem as in CFTest unfortunately...
B.
Bruno Chareyre a écrit :
1. Bruno: fix
___
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
Grenoble INP
2. everybody: test yade without wm3 and see if all computations are
performed correctly. I can confirm this for myself, but not for others.
https://bugs.launchpad.net/yade/+bug/577581 (solved??)
For me it seems ok.
I'd feel better if I could hear there is no problem with clumps.
By the
?
Thanks for advices.
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
___
Mailing list: https://launchpad.net/~yade
I also changed updateShearForce to rotateAndGetShear (it does almost
the same, except that the last fs+=... line is moved to Law2.
Note that it would make sense to split this function into rotate and
getShear...
B
___
Mailing list:
also the function updateShearForce needs the positions of the
particles (which are accessed throughout the State pointer). Why would
be working there and not in applyForceAtContactPoint?
updateShearForce doesn't need positions, only velocities, except if
avoidGranularRatcheting=false.
I'll
other functors.
v
___
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
://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
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
- [4]: 0.0
Yade [5]: refstrain=triax.strain[1]
- [4]: -0.026189869682630321
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
.
___
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
Grenoble INP
Lab
will go from 0 to .2 output).
print refstrain,phase
: 0.0 0
Thanks for help.
Bruno
Anton Gladky a écrit :
Put your code in f separate file and start with YADE.
If it does not work - please, send the script here.
__
Anton Gladkyy
2010/5/26 Bruno Chareyre
and used it many times, but not in the last weeks. I made
no recent change either IIRC.
I'm going to test it with and without Eigen in order to try to find out.
Wm3 should compile now.
ps: was the bug you fixed related to the moment computation?
Not really.
Bruno
2010/5/26 Bruno Chareyre
Hi Chiara,
I see that in ElasticContactLaw if one wants to use the function
updateShear of ScGeom, velocities are not shifted there so eventually
it would not be compatible with pbc.
Any reason why you did not shift the velocities also there? I ask that
because I need the total shear
Anton Gladky a écrit :
Ok, returning to this message.
Try to create the file:
test.py
...
That is what you asked?
Yes, exactly.
I tried this simple test of course, and it returned correct results (I
tried that with ./yade test.py, not just ipython, to be really sure).
I got to make the same
Report that bug to Python, then, not to yade. Read the documentation on
python and its scopes, the fact that it doesn't do what you expect it to
do is not qualifiable as bug, IMHO.
I was hesitating. Doesn't the fact that the behaviour depends on where
run() is typed (script or console)
a little bit at MD, but I have lost myself into atoms,
molecules and so on and I guess this is not helping me at all. If you
have some more specific reading, I would appreciate it if you could
let me know.
Thanks, Chiara
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab
revno: 2270
committer: Janek Kozicki cosu...@berlios.de
branch nick: trunk
timestamp: Thu 2010-06-03 02:02:23 +0200
message:
was not compiling with wm3
modified:
pkg/dem/Engine/GlobalEngine/PeriIsoCompressor.cpp
Wow, you almost disabled the full periodicity thing. It will be hard to
.
___
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
It will be hard to make comparisons.
which comparisons?
wm3 vs. eigen.
I'm sure there are other q.normalize() needed here and there... (btw,
I'd be glad to understand why it is needed in eigen, two rotations
multiplied do not give another rotation?).
are you sure that you
errors.
The differences look preety big for something supposed to be just
rounding errors, but I was initiating simulations with loose clouds.
Maybe that is the reason.
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33
As already explained (search the archive), if you use cundall's damping,
the rounding errors can propagate infinitely quickly.
I agree that damping discontinuity can make the difference grow faster
in general. But in special cases where you can proove damping has no
effect on the result,
But I saw that many Law2 are still in GlobalEngine
So, what's the rule (if there is one ?)
This is mostly for backward compatibility, you don't have to do the
same. Looping in global engines is used less and less.
There are a few cases where global engines help a lot though, like using
attention to do this without
breaking anything !!)
Jerome
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
In fact I just found an use to this initialKn for me !!! So forget my
question : I'd prefer that it still exists...
Are you using it as initial? If not, you can rename it (Vaclac wrote
a python script for renaming).
Bruno
___
Mailing list:
I just used bodies generated from
triax-basic-with-clups.py and pasted them into .xml file generated
from FileGenerator.
By the way, this is probably why you have instabilities during the
transition.
B.
___
Mailing list:
Hi,
The only annoying thing I found with python scripting (compared with
complex routines in c++ engines) is that you can't really _save_ the
simulation.
By save, I mean stop a simulation and write it to a file, and later
restart Yade, reload it and continue as if it had never been stopped.
I think you can save all variables, what you need, with self-defined
function. It is about 10 strings of code.
Then you can load both files.
You mean writing some variables in a separate text file? Of course, but
I'd put this in workarounds, since there will be different variables
names
/Manual/latest/doc_html/cgal_manual/Triangulation_3_ref/Chapter_intro.html
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
Václav Šmilauer a écrit :
https://www.yade-dem.org/sphinx/user.html#saving-python-variables
Very interesting. For functions, I guess modules are the only way.
Thanks.
Bruno
___
Mailing list: https://launchpad.net/~yade-dev
Post to :
Vaclav, I am using Ubuntu 9.04 (Jaunty). My colleague Boon is using
the same version as well.
Please try to compile it for the relase I am using, I am not sure if
and when I will be able to update it.
It is already compiled, go to
https://launchpad.net/~yade-users/+archive/external ,
://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
___
Mailing list: https://launchpad.net/~yade-dev
You said your new computer would arrive in a few days about a month ago.
Still not the case?
No. It's been ordered a while ago but they need that much time to sell a
pc apparently... crazy.
For the upgrade to 10.04, it is fairly easy and now,
2 months after the release, also thoroughly
Improve wiki design and clean/update the content?
Big karma-maker for sure. Feel free to suggest changes if you find
annoying features in the website configuration, I'm sure Remi will be
glad to help fix them.
Bruno
We have to do something with that, as old wiki makes troubles for
Hi,
I made some changes in wiki home.
- I removed some pages (well, the pages are still there, I removed only
the links).
- I listed a few of them for pending erase when I was not sure (bottom
of page, removed soon if no one complains).
I think should be kept :
- Yade community
- Yade
Hi,
I have no more time today to go through that. After a quick look at last
update, one remark : I think the items in move to sphinx should be
kept in the wiki, since it is general information relevant for people
interested in Yade but not interested in reading its documentation. It
can be
://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
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56
Václav Šmilauer a écrit :
It is already implemented and used for CohFric and derived class. There
is no difference between incremental and total for relative rotations,
only shear disp. can be incremental.
That is an implementation inside a constitutive law; unless someone will
use the
a Yade misfeature.
I can fix that in the doc (together with the paragraph on
GlobalStiffnessTimeStepper I already mentioned) if you confirm this part
of doc is commitable already.
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9
What I realized is that Dem3DofGeom and ScGeom give different results
(which is https://bugs.launchpad.net/yade/+bug/399963) . I didn't pay
close attention to https://bugs.launchpad.net/yade/+bug/585771 (why is
it marked invalid?), that one looks real.
I marked it invalid when you suggested
And is the local coordinate system then (what axes?)?
The axes are what you like. Let you define the principal axis Xinit of
you beam section in reference coordinate system (which we don't do
usually, just because we don't need). Then apply
ScGeom::rotateAndGetShear(X) on it (I should
(We could order by
deleted lines, that is more important than lines added.)
hehe. I object ;-) You wouldn't need to delete anything if I didn't
write it first ;-P
Commits then? (https://www.ohloh.net/p/yade/contributors - funny website!)
Bruno
() is not good either, since it
would result in those quantities being computed twice at least.
Bruno
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
All I would need is the relativeVelocity to compute incidentVn and
incidentVs, having the normal. If I inherit from ScGeom,
relativeVelocity is not a member of it. So how would you access it?
class ScGeomWithVel: public ScGeom: {
...
/~yade-dev
More help : https://help.launchpad.net/ListHelp
--
___
Bruno Chareyre
Associate Professor
Grenoble INP
Lab. 3SR
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
___
Mailing
In fact, this will be a problem for me. Capillary law is one specific
case and has been computed, if I get it right, as a separate
constitutive relationship. However, there are laws where fn can be
zero and a stiffness has to be consider since the contact still
remains as the contact area
___
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
___
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
Grenoble INP
Lab. 3SR
BP 53
Yes, sure in fact my question is still valid. Can I say that into the
contact law? I mean, that if one of the two contact bodies is
non-dynamic, then assign the mass equal to the one of the dynamic body..
I'd say yes. :)
Bruno
___
Mailing
201 - 300 of 1689 matches
Mail list logo
