yade-dev team mailing list archive

[Jan Stránský <honzik.stransky@xxxxxxxxx>]

Hello Eugen,

could you please be more specific? e.g. where have you seen this bug or a
minimal working example reproducing the bug.

I was not able to reproduce it myself. Just now I am trying some small
examples and here are my results. Script:
...
O.engines = [
ForceResetter(),
InsertionSortCollider([Bo1_Sphere_Aabb(),Bo1_Facet_Aabb()],label='collider'),
InteractionLoop(...),
PyRunner(iterPeriod=1,command="addPlotData()"),
PyRunner(iterPeriod=1,command="printInfo()"),
NewtonIntegrator(),
]

ipython:

Yade [1]: O.engines
 ->  [1]:
[<ForceResetter instance at 0x506d280>,
 <InsertionSortCollider instance at 0x501dd00>,
 <InteractionLoop instance at 0x49b1530>,
 <PyRunner instance at 0x4f92a20>,
 <PyRunner instance at 0x4ff5300>,
 <NewtonIntegrator instance at 0x4547020>]

Yade [2]: len(O.engines)
 ->  [2]: 6

Yade [3]: O.engines[0]
 ->  [3]: <ForceResetter instance at 0x506d280>

Yade [4]: O.engines[5]
 ->  [4]: <NewtonIntegrator instance at 0x4547020>


cheers
Jan



2013/4/30 Eugen Kubowsky <1174749@xxxxxxxxxxxxxxxxxx>

> Public bug reported:
>
> Hi,
> I've seen a little bug. not critical.
> If you browse the Engines of your simulation the first Engine starts with
> number 0. It should be 1 because the number of engines is defined as
> len(enginelist)+1 seemingly.
>
> ** Affects: yade
>      Importance: Undecided
>          Status: New
>
> ** Attachment added: "Bildschirmfoto vom 2013-04-30 15:06:36.png"
>
> https://bugs.launchpad.net/bugs/1174749/+attachment/3660218/+files/Bildschirmfoto%20vom%202013-04-30%2015%3A06%3A36.png
>
> --
> You received this bug notification because you are a member of Yade
> developers, which is subscribed to Yade.
> https://bugs.launchpad.net/bugs/1174749
>
> Title:
>   Controller Engines -> Engine count starts at 0 instead of 1
>
> Status in Yet Another Dynamic Engine:
>   New
>
> Bug description:
>   Hi,
>   I've seen a little bug. not critical.
>   If you browse the Engines of your simulation the first Engine starts
> with number 0. It should be 1 because the number of engines is defined as
> len(enginelist)+1 seemingly.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/yade/+bug/1174749/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1174749

Title:
  Controller Engines -> Engine count starts at 0 instead of 1

Status in Yet Another Dynamic Engine:
  New

Bug description:
  Hi,
  I've seen a little bug. not critical.
  If you browse the Engines of your simulation the first Engine starts with number 0. It should be 1 because the number of engines is defined as len(enginelist)+1 seemingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1174749/+subscriptions