Differences
This shows you the differences between two versions of the page.
doc:pycram:process_modules [2021/06/10 12:01] – created jdech | doc:pycram:process_modules [2021/06/11 08:29] (current) – jdech | ||
---|---|---|---|
Line 26: | Line 26: | ||
else: | else: | ||
logerr(f" | logerr(f" | ||
- | </ | + | </ |
The robot name is the name of the currently loaded robot extracted from the robot description. | The robot name is the name of the currently loaded robot extracted from the robot description. | ||
The robot type is a class attribute of the ProcessModule class which is set in the high-level plan with either the decorator ' | The robot type is a class attribute of the ProcessModule class which is set in the high-level plan with either the decorator ' | ||
Lastly, the type is the cmd property of the motion designator for which the process module is being chosen. | Lastly, the type is the cmd property of the motion designator for which the process module is being chosen. | ||
+ | Too differentiate between the process modules for the real and simulated robot, two dictionary' | ||
+ | |||
+ | This method for choosing a process module then needs to be registered as a resolver, this is done by appending the method to the list of resolvers in the ProcessModule class atribute. An example of this can be seen below | ||
+ | < | ||
+ | |||
+ | ==== Importing in the final plan ==== | ||
+ | For the registration to take effect the files, which cointains the ' |