Yade

Labelling engines after reload

Asked by Jérôme Duriez

Hi, I apologize in advance for this weird question, but...
I have different xml files (obtained successively during a first yade session, but I do not know if this matters). During a second Yade session (current trunk version), I got different results with the three following lines :

O.load('save_i.xml')
O.engines=[NewtonIntegrator(label='newt')] # the choice of the engine does not matter
print newt

Most of the time, I got an error : "NameError: name 'newt' is not defined". It works ("<NewtonIntegrator instance at 0x686d240>") only with one save, the first one that was obtained in the procedure of the first Yade session (still, does it matter ?).

Does someone understand something ? I got mad with labelling engines... Thanks a lot,

Jerome

PS : at the moment I can not precise a simple procedure to generate such "problematic xml saves". Mines were obtained during continuous isotropic unloading, for sample generation (and are around 150 MB)

Question information

Language:
English Edit question
Status:
Expired
For:
Yade Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Bruno Chareyre (bruno-chareyre) said : 		#2

Off-topic (sorry), but... don't save in xml, it kills your HD and it
takes a lot of time.
O.save("test.yade"), or in compressed version O.save("test.yade.gz")

Revision history for this message
Jérôme Duriez (jduriez) said : 		#3

Ok, this is indeed much more compact... But, does not solve the issue (I had to check to get it...)

Revision history for this message
Launchpad Janitor (janitor) said : 		#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.