Question #622864 on Yade changed:
https://answers.launchpad.net/yade/+question/622864
Status: Open => Answered
Jérôme Duriez proposed the following answer:
Hello,
1) Yes, this is correct (the order as well), see source code [1] to be sure.
As a personal remark, note that such recording engines are probably less useful
in YADE now that such kind of data can be easily accessed and saved through
Python [2].
(Obviously, you may still use them though, if you're OK to spend time to know
how these engines work)
3) The ForceRecorder is able to deal with several YADE bodies through its ids
attribute [3], see also source code [1] to check that a cumulative value is
stored.
Provided you know which (and how many) YADE bodies are created when you import
this "mesh file", and that you correctly define this ids attribute, you should
be able to do everything you want here.
Jerome
PS: I would recommend you open different Launchpad questions when you
have different questions, 2) being here quite distinct from 1)/3)
[1]
https://github.com/yade/trunk/blob/e4e757f2e98a620e3177b7a36a1d10f69f6a6a28/pkg/dem/ForceTorqueRecorder.cpp#L14
[2] https://yade-dem.org/doc/tutorial-data-mining.html
[3]
https://yade-dem.org/doc/yade.wrapper.html?highlight=forcerecorder#yade.wrapper.ForceRecorder.ids
--
You received this question notification because your team yade-users is
an answer contact for Yade.
_______________________________________________
Mailing list: https://launchpad.net/~yade-users
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-users
More help : https://help.launchpad.net/ListHelp
