yade-dev team mailing list archive

[Jérôme Duriez <jerome.duriez@xxxxxxxxxxx>]

Indeed, that's another point of view.. Mine would be that
O.tags['params'] is deeply related with the batch parameters rather than
anything else. I'll wait a couple of days and then mark the bug as
invalid if I'm the only one thinking that way.

(In fact, the solution you're proposing would not work for my case
because I decide to load, or do something else, depending on the batch
parameters)

Speaking by the way about O.tags in general, I never use it for
something else than 'params' and am curious what use can be made of it
(which starts to be off topic here)

Thanks !

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

Title:
  O.tags['params'] for 2 batchs and 1 save

Status in Yade:
  New

Bug description:
  Hello,

  I've faced some issue for batch simulation. I have a batch simulation
  that loads a .yade save from a previous simulation that was also
  launched in batch mode.

  The two batch-mode simulations consider different parameters in their
  .table. And in the second simulation, O.tags['params'] refers to the
  parameters of the first batch-mode simulation, while I would like it
  refers to the parameters of the current simulation..

  I'm attaching example scripts "first.py" and "second.py", together
  with their "first.table" and "second.table" to illustrate. "first.py"
  will generate a .yade that will be used by "second.py". During the
  batch execution of "second.py", O.tags['params'] refers to first.table
  instead of second.table.

  It turns out the O.load erases the right O.tags['params']

  Do we agree it is a bug or, at least, an indesirable feature ? Would
  it be possible to not save O.tags['params'] in .yade files ?

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