** Attachment added: "first.py" https://bugs.launchpad.net/yade/+bug/1596021/+attachment/4689846/+files/first.py
-- 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 _______________________________________________ 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
