revno: 1883
committer: Anton Gladky
branch nick: trunk
timestamp: Thu 2009-12-10 08:08:03 +0100
message:
ymport.gmsh function was renamed to ymport.mesh one
modified:
py/ymport.py
scripts/test/regular-sphere-pack.py
--
lp:yade
ht
> Just found out it is only that way in InteractionDispatchers... (bug,
> should behave the same). It might be better to put this to
> Collider::mayCollide,
there is no objection.
--
Best regards,
Sergei D.
___
Mailing list: https://launchpad.net/~y
> Bitmasks are used in InteractionGeometryDispatcher; if (mask1 &
> mask2)==0 and the masks are not zero (IIRC), then the bodies will not
> enter interaction. (I will document it properly in the doc I am writing,
> but that will take some time).
Just found out it is only that way in InteractionDi
> >If you do, is it be enough to use Body::groupMask in
> > the functor to avoid those?
> Hm, I have not thought about it until this moment. May be...
> How do you use the groupMask in general?
Bitmasks are used in InteractionGeometryDispatcher; if (mask1 &
mask2)==0 and the masks are not zero (II
09.12.2009 22:27, Václav Šmilauer пишет:
>>> IIRC Sega was adding the noBound parametr for utils.facet, he probably
>>> had some use for that... Ping?
>>>
>>
>> This is to specify the region of placing spheres.
>> Example is scripts/test/ResetRandomPosition.py
> Fine, but do you need _bodies_ for t
> > IIRC Sega was adding the noBound parametr for utils.facet, he probably
> > had some use for that... Ping?
> >
>
> This is to specify the region of placing spheres.
> Example is scripts/test/ResetRandomPosition.py
Fine, but do you need _bodies_ for that (rather than just parameters to
the engi
revno: 1882
committer: Václav Šmilauer
branch nick: trunk
timestamp: Wed 2009-12-09 20:09:45 +0100
message:
1. Enable search engine in doxygen.
modified:
doc/Doxyfile
--
lp:yade
https://code.launchpad.net/~yade-dev/yade/trunk
Your
>
> IIRC Sega was adding the noBound parametr for utils.facet, he probably
> had some use for that... Ping?
>
This is to specify the region of placing spheres.
Example is scripts/test/ResetRandomPosition.py
--
Best regards,
Sergei D.
___
Mailing
revno: 1881
committer: Sergei D.
branch nick: trunk
timestamp: Wed 2009-12-09 21:53:59 +0300
message:
Update ResetRandomPosition
modified:
pkg/common/Engine/GlobalEngine/ResetRandomPosition.cpp
scripts/test/ResetRandomPosition.py
> The Scene functor sounds powerful.
> dt was used to be assesed through dt=Omega::getTimeStep() now it can
> be assesed through Scene->dt.
> What other paramters are affected. All can be assessed through Scene?
> I haven't got it...
Yes, everything, but it shouldn't be abused (functors should n
revno: 1880
committer: Václav Šmilauer
branch nick: trunk
timestamp: Wed 2009-12-09 19:24:09 +0100
message:
1. Finish renaming DeusExMachina -> PartialEngine
renamed:
pkg/common/DataClass/BoundingVolume/ => pkg/common/DataClass/Bound
> What is happened with GravityEngine in last rev?
Just commited, sorry. Omission on my part.
v
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-dev
More help :
Thanks Vaclav for informing us about the changes.
The Scene functor sounds powerful.
dt was used to be assesed through dt=Omega::getTimeStep() now it can be assesed
through Scene->dt.
What other paramters are affected. All can be assessed through Scene? I haven't
got it...
Yours,
CWBoon
What is happened with GravityEngine in last rev?
It is can not be found:
s...@think:~/work/yade/trunk/scripts/test> yade-trunk
clump-hopper-viscoelastic.py
Welcome to Yade bzr1879
WARNING: class DeusExMachina not defined
/usr/lib64/python2.6/site-packages/pytz/tzinfo.py:5: DeprecationWarning:
th
revno: 1879
committer: Václav Šmilauer
branch nick: trunk
timestamp: Wed 2009-12-09 18:11:51 +0100
message:
1. Renames as discussed on yade-dev: NewtonsDampedLaw -> NewtonIntegrator,
StandAloneEngine -> GlobalEngine, DeusExMachina ->
revno: 1878
committer: Václav Šmilauer
branch nick: trunk
timestamp: Wed 2009-12-09 17:43:25 +0100
message:
1. Add Scene* Functor::scene, update it from all dispatchers at every step.
2. Add NewtonsDampedLaw::homotheticCellResize (0,
> If I understand correctly, DeusExMachina (DExM) and StandAloneEngine (SAE)
> differ only with one virtual class (hold by DExM).
> What about making the supplementary virtual function of DExM an empty
> function (without =0). Then
> remove SAEs and change the mother class of each class that in
> 3. BoundFunctor is currently 2d, dispatching on Shape and Bound. It
> however forces you to decide what collider you use by setting the bound
> type beforehand. I would prefer that BoundFunctor would dispatch only
> based on Shape, but there would have to be a way to specify regular
> bodies (no
Le 9 déc. 2009 à 16:49, Václav Šmilauer a écrit :
> Hi, I am in the process of writing programmer's manual to yade and some
> idiosyncracies are showing up.
>
> 1. I will rename StandAloneEngine -> GlobalEngine (since it describeds
> what it really does, globally affecting the scene). But what
1. I will rename StandAloneEngine -> GlobalEngine (since it describeds
what it really does, globally affecting the scene). But what about
DeusExMachina? BodyEngine (since it usually operates on a set of
bodies)?
For me, Standalone and Deus could be merged, and Global is a good name
for this
Thanks! Works now.
** Changed in: yade
Status: In Progress => Fix Released
--
yade-multi is not working
https://bugs.launchpad.net/bugs/493686
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
Status in Yet Another Dynamic Engine
Hi, I am in the process of writing programmer's manual to yade and some
idiosyncracies are showing up.
1. I will rename StandAloneEngine -> GlobalEngine (since it describeds
what it really does, globally affecting the scene). But what about
DeusExMachina? BodyEngine (since it usually operates on
revno: 1877
committer: Anton Gladky
branch nick: trunk
timestamp: Wed 2009-12-09 16:38:28 +0100
message:
Some syntax fixes: moveTo has been renamed to shift in utils.py and ymport.py
modified:
py/utils.py
py/ymport.py
scripts/tes
Agree, r1877
Thanks for suggestions!
2009/12/9 Václav Šmilauer
>
> > + if (((extents[0]==0) and (extents[1]==0)) or ((extents[0]==0)
> > and (extents[2]==0)) or ((extents[1]==0) and (extents[2]==0))):
> > + raise TypeError("Please, specify at least 2 none-zero
> > dimension
revno: 1876
committer: Václav Šmilauer
branch nick: trunk
timestamp: Wed 2009-12-09 16:30:25 +0100
message:
Hopefully fix yade-multi https://bugs.launchpad.net/yade/+bug/493686 now?
Please confirm.
modified:
py/plot.py
--
lp:yade
> + if (((extents[0]==0) and (extents[1]==0)) or ((extents[0]==0)
> and (extents[2]==0)) or ((extents[1]==0) and (extents[2]==0))):
> + raise TypeError("Please, specify at least 2 none-zero
> dimensions in extents!");
Should be RuntimeError, not TypeError (has nothing to do wi
> if you impose a deplacement to each grains like you propose to do,
> grains will move like you want; i mean that they will move from a
> position to another
> one imposed by J. This does not really correspond to want we want...
> Grains must
> have a degree of freedom...It seems that it is not
revno: 1875
committer: Anton Gladky
branch nick: trunk
timestamp: Wed 2009-12-09 14:48:23 +0100
message:
1. Added moveTo und scale parameters for ymport.gmsh function
modified:
py/ymport.py
--
lp:yade
https://code.launchpad.net/~ya
Václav Šmilauer a écrit :
I am little lost in the H notation (generic linear transformation,
right?), but I think the point is very clear. Is it "better" to change
positions or velocity?
I'll reply to that in details after discussion here in Grenoble.
if we have imposed stress along x axis
Bruno Chareyre a écrit :
When I wrote : "If the displacement (resp. velocity) at the boundary
is "u", then the displacement (vel) at the center should be "u/2",
they ran to my office and told me no-no-no. ;-)
Let's start again.
H is in fact defined by 3 vectors. Say X=[X1 X2 X3], Y=[Y1 Y2 Y3]
** Changed in: yade
Status: Fix Released => In Progress
--
yade-multi is not working
https://bugs.launchpad.net/bugs/493686
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
Status in Yet Another Dynamic Engine: In Progress
Bug d
revno: 1874
committer: Anton Gladky
branch nick: trunk
timestamp: Wed 2009-12-09 10:52:15 +0100
message:
1. In utils.facetBox added 'Defence from zero dimensions'
2. regular-sphere-pack.py is updated due to new names
modified:
py/u
Line in plot.py also makes some problem:
45if not plotDataCollector:
plotDataCollector=o.labeledEngine('plotDataCollector') # will raise
RuntimeError if not found
when I start simple YADE simulation, it works just fine.
But when I do yade-multi, I get a very strange result:
Traceback (most r
revno: 1873
committer: Anton Gladky
branch nick: trunk
timestamp: Wed 2009-12-09 10:24:52 +0100
message:
Very trivial fix in utils.py
modified:
py/utils.py
--
lp:yade
https://code.launchpad.net/~yade-dev/yade/trunk
Your team Yade
Sorry, have just done it :)
__
Anton Gladkyy
2009/12/9 Václav Šmilauer
> Anton Gladky píše v St 09. 12. 2009 v 09:39 +0100:
> > I have a problem with this line in utils.py:
> > 540 o.tags['line']='l!'
>
> should be O.tags['line']='l!' (capital O); can you fix
Anton Gladky píše v St 09. 12. 2009 v 09:39 +0100:
> I have a problem with this line in utils.py:
> 540 o.tags['line']='l!'
should be O.tags['line']='l!' (capital O); can you fix that for yourself
and commit next time you commit? There might be more omissions like that
in the codepaths I di
> De : Vincent Richefeu
> Date : 9 décembre 2009 09:35:42 HNEC
> À : boon chiaweng
> Objet : Rép : [Yade-users] Questions on equations (contact laws, velocity,
> libraries)
>
>
> Le 9 déc. 2009 à 03:06, boon chiaweng a écrit :
>
>> Q3. The position/velocity integration follows the 2nd order
I have a problem with this line in utils.py:
540 o.tags['line']='l!'
File
"/home/gladk/dem/yade/currentMono/build/lib/yade-currentMono/py/yade/utils.py",
line 540, in readParamsFromTable
o.tags['line']='l!'
NameError: name 'o' is not defined
What is it for?
___
Thanks, it works!
But I have a small problem with yade.plot.addData, while using yade-
multi.
I have following error:
Traceback (most recent call last):
File "", line 1, in
File "uniaxialCylinderTest.py", line 169, in myAddPlotData
yade.plot.addData(Eps=Eps_calc,Sigma=Sigma_calc)
File
39 matches
Mail list logo
