Usage examples Sample Clauses
The "Usage examples" clause provides illustrative scenarios or sample applications to demonstrate how a particular provision, product, or process should be used in practice. Typically, this clause includes hypothetical situations or step-by-step guides that clarify the intended operation or interpretation of the main terms. By offering concrete examples, it helps users or parties better understand complex requirements, reduces ambiguity, and ensures consistent application of the agreement or instructions.
Usage examples. rinohtype supports three modes of operation, which are discussed in more detail in the Chapter
Usage examples. In this section, an example of how to generate a simple message will be described.
6.4.1 package.xml file The ROS2 manifest must have the below dependencies: • Must be member_of_group of rosidl_interface_packages group. • Is buildtool_depend dependent of rosidl_default_generators
Usage examples. In this section, an example of how to generate a simple message will be described.
6.4.1 package.xml file The ROS2 package manifest is an XML file called package.xml that must satisfy the following re- quirements: • It must be a member_of_group of the rosidl_interface_packages group. • It must be buildtool_depend dependent of the rosidl_default_generators
Usage examples. The Python code to create a Handle in EPIC service offered by ▇▇▇▇ looks like Figure 12 (many details omitted): 8 ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇/EUDAT/Services/DataManagement/PID/iRODS-Integration/C 9 ▇▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇/EUDAT/Services/DataManagement/PID/iRODS-Integration/Python def createHandle(self,prefix,keyValues,suffix=''): uri = self.baseuri + '/' + prefix if suffix != '': uri += "/" + suffix index = 1 json = {} for key in keyValues: json[str(index)] = {'type':key,'data':keyValues[key]} index += 1 new_handle_json = simplejson.dumps(json) hdrs = {'If-None-Match': '*', 'Content-Type':'application/json'} try: response,content = self.http.request(uri,method='PUT', headers=hdrs, body=new_handle_json) except: self._debugMsg('createHandleWithLocation', "An Exception occurred during Creation of " + uri) return None else: self._debugMsg('createHandleWithLocation', "Request completed") return response['location'] The workflow is pretty simple: first a URL is created. This is composed of the service URL, a prefix (which is unique for each partner) and a suffix (which is unique for each object). Then a JSON document is prepared from the parameter array keyValues. Before the HTTP request PUT is sent, the HTTP headers are extended to include the information that the JSON representation will be using. Finally the whole HTTP message, composed of the header and body, is sent to the previously-prepared URL, and the service response is interpreted and returned. The method createHandle from the file epicclient.py can be included in an iRODS rule as shown in Figure 13. testCreateRetrieveDelete { msiPyInitialize; msiLocalPython4("/irods/pidservices/epicclient.py", "createHandle", "noRecursionTest", *prefix, *suffix, "{'URL':'▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇.▇▇▇/loc1', 'CHECKSUM':'abcdef'}", INPUT *prefix="9210",*suffix="TESTHANDLE3" OUTPUT *res Firstly the Python interpreter is initialized, then the method "createHandle" (from the file epicclient.py) is called with following parameters: *prefix, *suffix, and JSON contents (as a string). The result of the operation can be accessed via the variable *res. If no more Python-based micro-services will be called, the Python interpreter can be finalized.