Saving/loading simulations

Yes, this is a feature of Yade (you may consider annoying) : all python variables / functions are not saved during a (.xml or .yade) Yade save. Hence, they do not exist once you reload.

Give a look here : https://yade-dem.org/doc/user.html#saving-python-variables

Alright!

So, how can we do the following in a single code;

run a model.py

run_to_reach_equilibrium

save xml

call a apply_load.py

run_to_reach_equilibrium

save xml

The idea is to be able to automatically call a python script which includes definitions of parameters and functions after a certain number of iterations and then save the model after reaching for equilibrium state.

This means, putting all the above commands in a single moodel.py and running it.
Thanks

>this is a feature of Yade

More exactly, it is a feature of python:
me@desktop:~$ python
>>> def helloWorld(): print "hello world!"
>>> helloWorld()
hello world!
>>> quit()
me@desktop:~$ python
>>> helloWorld()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'helloWorld' is not defined

One solution is this:

me@desktop:~$ echo "def helloWorld(): print 'hello world!'" > hello.py
me@desktop:~$ python
>>> from hello import *
>>> helloWorld()
hello world!

@Behzad, the simplest way is to define addData() in the script applying the load. In many cases it makes more sense actually, because you don't need the evolution of position before the loading, or at least you don't want it duplicated in the output of each other loading.

Side points:
- Could you explain why you had the idea of saving in xml? It is a bad idea but it is seen frequently. If there is something in the documentation that pushed you toward this we should fix it. Better save as *.yade, or *.yade.gz, much faster and less disk usage.

- "from yade import utils" is useless and can be the source of troubles. Remove also the "utils." prefix in the script.

Yes, it makes sense for the application of loads.

- as for saving as xml, I thought it's the only option we have!

cheers,
Behzad

Hi,

so, how we call the loading script? It's a python script. Is there anything like call loading.py or something?

>as for saving as xml, I thought it's the only option we have!

Why? Did you read it somewhere?

>how we call the loading script?

What do you mean? You call it just like the script generating the initial packing.
$ yade script.py
or if yade is already running:
>>> run script.py

The script will probably start with O.load("saved.yade")

You mean calling a python script from the python interface of Yade ?
If yes, you may try:

execfile('theNameOfYourScript.py')

Alright, I tried bith execfile('loading.py') and run loading.py

For the moment run loading.py is what I was looking for. It's pretty useful. Because, I can load a saved simulation and then use this command to call a script to redefine the parameters and functions all together.

execfile('loading.py') is also useful because it can be included in the original script.

@Bruno: Yes, it's in loading and saving section of introduction [1]:

[1]: https://yade-dem.org/doc/introduction.html?highlight=xml

Thanks guys

>@Bruno: Yes, it's in loading and saving section of introduction

TYVM. I just fixed it.
B

For future reference, a method to escape the "reloading user-declared functions/variables" problem is examplified in examples/simple-scene/save-then-reload.py [1].
[1]https://github.com/yade/trunk/blob/master/examples/simple-scene/save-then-reload.py