yade-dev team mailing list archive

[Bruno Chareyre <1596021@xxxxxxxxxxxxxxxxxx>]

Hi Jérôme,
O.tags contain whatever you like in terms of named data (e.g. version/date of the script that was used to produce one particular scene).
If you see O.tags['params'] as a memory of which parameters were used (it is obviously not the sole purpose) you realize that forgetting history upon reload may not be a desirable feature.

> 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

For your particular problem maybe the script design itself can be questionned.
Else why not this:

readParamsFromTable(secondParam = 'toto')
#do whatever you like, and depending on the second params maybe:
   O.load('first.yade')
   readParamsFromTable(secondParam = 'toto') #overwrite

-- 
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