Software Users Guide - Revision history

Dvernon: /* Using yarpmanger to manage CINDY applications */

2025-07-10T12:43:27Z

‎Using yarpmanger to manage CINDY applications

Dvernon: /* Using yarpmanger to manage CINDY applications */

2025-07-10T12:43:13Z

‎Using yarpmanger to manage CINDY applications

Dvernon: /* Using yarpmanger to manage CINDY applications */

2025-07-10T12:04:56Z

‎Using yarpmanger to manage CINDY applications

Dvernon: /* Using gyarpmanger to manage CINDY applications */

2025-07-10T11:51:21Z

‎Using gyarpmanger to manage CINDY applications

Dvernon: /* Setting up your machine: Running YARP */

2019-06-04T16:58:19Z

‎Setting up your machine: Running YARP

Dvernon at 15:18, 23 February 2015

2015-02-23T15:18:49Z

Dvernon: /* Using gyarpmanger to manage CINDY applications */

2015-02-23T15:17:57Z

‎Using gyarpmanger to manage CINDY applications

Dvernon at 08:09, 17 February 2015

2015-02-17T08:09:57Z

Dvernon at 18:36, 15 February 2015

2015-02-15T18:36:55Z

Dvernon at 13:34, 15 February 2015

2015-02-15T13:34:42Z

← Older revision		Revision as of 12:43, 10 July 2025
Line 35:		Line 35:


−	YARP provides GUI and a console/terminal tools to help you run these application. This is called ''yarpmanager'' and ''yarpmanager-console''. These are powerful tools and you can read more about them ~~here~~ [https://www.yarp.it/latest/group__yarpmanager.html here]. For the present, just note that ''yarpmanager'' can read a <code>.ini</code> configuration file to find out where the applications are (among other things).	+	YARP provides GUI and a console/terminal tools to help you run these application. This is called ''yarpmanager'' and ''yarpmanager-console''. These are powerful tools and you can read more about them [https://www.yarp.it/latest/group__yarpmanager.html here]. For the present, just note that ''yarpmanager'' can read a <code>.ini</code> configuration file to find out where the applications are (among other things).

← Older revision		Revision as of 12:43, 10 July 2025
Line 35:		Line 35:


−	YARP provides GUI and a console/terminal tools to help you run these application. This is called ''yarpmanager'' and ''yarpmanager-console''. These are powerful tools and you can read more about them here [~~http~~://~~wiki~~.~~icub~~.~~org~~/~~yarpdoc~~/~~yarpmanager~~.html here]. For the present, just note that ''yarpmanager'' can read a <code>.ini</code> configuration file to find out where the applications are (among other things).	+	YARP provides GUI and a console/terminal tools to help you run these application. This is called ''yarpmanager'' and ''yarpmanager-console''. These are powerful tools and you can read more about them here [https://www.yarp.it/latest/group__yarpmanager.html here]. For the present, just note that ''yarpmanager'' can read a <code>.ini</code> configuration file to find out where the applications are (among other things).

@@ Line 44: / Line 44: @@
   C:/CINDY>yarpmanager
-Once this tool has been launched, you need to open the applications you want to run.
+On my implementation of YARP, this launches the console tool, rather than the GUI tool, so the following instructions assume you are using the console version of ''yarpmanager''.
-<!-- Do this by opening on the Applications folder on the left-hand side and double-clicking on the application you are interested in.   Find the one labelled --><code>protoComponent_test</code> (included with the original release of the CINDY repository) and double-click on it.
+Once this tool has been launched, you need to open the applications you want to run. First, list the applications that are available by entering the following command.
@@ Line 58: / Line 89: @@
-Now try running the <code>protoComponentGUI_test</code> application.  It will launch three components, replacing the two Yarpview components  with a dedicated  <code>protoComponentGUI</code> component to display the images and set the threshold interactively.
+Now try running the <code>protoComponentGUI_test</code> application.  It will launch three components, replacing the two Yarpview components  with a dedicated  <code>protoComponentGUI</code> component to display the images and set the threshold interactively. -->
 ----
 Return to [[The CINDY Cognitive Architecture]] main page.

@@ Line 30: / Line 30: @@
 This allows YARP to overwrite the  YARP configuration file with the IP address of the computer.   In some instances, e.g. when setting up your own network of YARP servers, you may want to define your own static IP addresses for every computer on the network which you want to use as a YARP run server.  Instructions on how to do this will be provided in due course.
-== Using ''gyarpmanger'' to manage CINDY applications ==
+== Using ''yarpmanger'' to manage CINDY applications ==
 CINDY software is just as set of interconnected components and CINDY software applications are defined by identifying the components to be used, the computers (nodes) on which they are to be run, and the connections between the various components.   All this is done with a <code>.xml</code> application file, normally stored in the <code>app</code> directory.
-YARP provides a GUI tool to help you run these application.  This is called ''gyarpmanager''.   It is a powerful tool and you can read more about it [http://wiki.icub.org/yarpdoc/yarpmanager.html here].   For the present, just note that ''gyarpmanager'' can read a <code>.ini</code> configuration file to find out where the applications are (among other things).
+YARP provides GUI and a console/terminal tools to help you run these application.  This is called ''yarpmanager'' and ''yarpmanager-console''.  These are powerful tools and you can read more about them here [http://wiki.icub.org/yarpdoc/yarpmanager.html here].   For the present, just note that ''yarpmanager'' can read a <code>.ini</code> configuration file to find out where the applications are (among other things).
-There is a default <code>ymanager.ini</code> file in the root of the CINDY directory and it simply tells ''gyarpmanager'' to look for all application <code>.xml</code> files under the <code>release</code> directory.
+There is a default <code>ymanager.ini</code> file in the root of the CINDY directory and it simply tells ''yarpmanager'' to look for all application <code>.xml</code> files under the <code>release</code> directory.
 So, to finally get started, launch another (i.e. a third)  ''Command Prompt'' terminal, change directory to the CINDY root directory and enter ''gyarpmanager''
-  C:/CINDY>gyarpmanager
+  C:/CINDY>yarpmanager
-Once this tool has been launched, you need to open the applications you want to run.  Do this by opening on the Applications folder on the left-hand side and double-clicking on the application you are interested in.   Find the one labelled <code>protoComponent_test</code> (included with the original release of the CINDY repository) and double-click on it.
+Once this tool has been launched, you need to open the applications you want to run.

@@ Line 7: / Line 7: @@
 Before you do, you have to launch a YARP server and a YARP run server.
-From the Windows 7 toolbar, launch a ''Command Prompt'' terminal and do the following.
+From the Windows 10 toolbar, launch a ''Command Prompt'' terminal and do the following.
   yarp server

@@ Line 44: / Line 44: @@
   C:/CINDY>gyarpmanager
-Once this tool has been launched, you need to open the applications you want to run.  Do this by opening on the Applications folder on the left-hand side and double-clicking on the application you are interested in.   Find the one labelled <code>protoComponent_test'</code> (included with the original release of the CINDY repository) and double-click on it.
+Once this tool has been launched, you need to open the applications you want to run.  Do this by opening on the Applications folder on the left-hand side and double-clicking on the application you are interested in.   Find the one labelled <code>protoComponent_test</code> (included with the original release of the CINDY repository) and double-click on it.
-Now, click the ''Run'' the on the ''protoComponent_test'' interface panel.  It will launch two components. The first one - <code>imageSource</code> - streams images from a file to a port (simulating a camera). The second one - <code>protoComponent</code> - takes these images and does some simple image processing (binary thresholding).
+Now, click the ''Run'' the on the ''protoComponent_test'' interface panel.  It will launch four components. The first one - <code>imageSource</code> - streams images from a file to a port (simulating a camera). The second one - <code>protoComponent</code> - takes these images and does some simple image processing (binary thresholding). The other two components are Yarpview components to display the image data.
@@ Line 55: / Line 55: @@
 Click ''Stop'' to stop the application, i.e. the two components.
 ----
 Return to [[The CINDY Cognitive Architecture]] main page.

@@ Line 15: / Line 15: @@
 Now, launch another ''Command Prompt'' terminal and do this.
-  yarp run --server /dream1
+  yarp run --server /cindy1
 This creates a run server named <code>/cindy1</code> and is used by YARP to find out where to execute the components in the application.
@@ Line 26: / Line 26: @@
 and again in another terminal
-  yarp run --server /dream1
+  yarp run --server /cindy1
 This allows YARP to overwrite the  YARP configuration file with the IP address of the computer.   In some instances, e.g. when setting up your own network of YARP servers, you may want to define your own static IP addresses for every computer on the network which you want to use as a YARP run server.  Instructions on how to do this will be provided in due course.
-== Using ''gyarpmanger'' to manage DREAM applications ==
+== Using ''gyarpmanger'' to manage CINDY applications ==
 CINDY software is just as set of interconnected components and CINDY software applications are defined by identifying the components to be used, the computers (nodes) on which they are to be run, and the connections between the various components.   All this is done with a <code>.xml</code> application file, normally stored in the <code>app</code> directory.

@@ Line 1: / Line 1: @@
-This guide explains how to use YARP and YARP tools to manage and run DREAM robot applications comprising a collection of components.
+This guide explains how to use YARP and YARP tools to manage and run CINDY applications comprising a collection of components.
 == Setting up your machine: Running YARP ==
-Once you have installed the DREAM software development environment you are (almost) ready to run the DREAM applications.
+Once you have installed the CINDY software development environment you are (almost) ready to run the CINDY applications.
 Before you do, you have to launch a YARP server and a YARP run server.
@@ Line 17: / Line 17: @@
   yarp run --server /dream1
-This creates a run server named <code>/dream1</code> and is used by YARP to find out where to execute the components in the application.
+This creates a run server named <code>/cindy1</code> and is used by YARP to find out where to execute the components in the application.
@@ Line 32: / Line 32: @@
 == Using ''gyarpmanger'' to manage DREAM applications ==
-DREAM software is just as set of interconnected components and DREAM software applications are defined by identifying the components to be used, the computers (nodes) on which they are to be run, and the connections between the various components.   All this is done with a <code>.xml</code> application file, normally stored in the <code>app</code> directory.
+CINDY software is just as set of interconnected components and CINDY software applications are defined by identifying the components to be used, the computers (nodes) on which they are to be run, and the connections between the various components.   All this is done with a <code>.xml</code> application file, normally stored in the <code>app</code> directory.
@@ Line 40: / Line 40: @@
 There is a default <code>ymanager.ini</code> file in the root of the DREAM directory and it simply tells ''gyarpmanager'' to look for all application <code>.xml</code> files under the <code>release</code> directory.
-So, to finally get started, launch another (i.e. a third)  ''Command Prompt'' terminal, change directory to the DREAM root directory and enter ''gyarpmanager''
+So, to finally get started, launch another (i.e. a third)  ''Command Prompt'' terminal, change directory to the CINDY root directory and enter ''gyarpmanager''
-  C:/DREAM>gyarpmanager
+  C:/CINDY>gyarpmanager
-Once this tool has been launched, you need to open the applications you want to run.  Do this by opening on the Applications folder on the left-hand side and double-clicking on the application you are interested in.   Find the one labelled <code>Demo_of_protoComponent'</code> (included with the original release of the DREAM repository) and double-click on it.
+Once this tool has been launched, you need to open the applications you want to run.  Do this by opening on the Applications folder on the left-hand side and double-clicking on the application you are interested in.   Find the one labelled <code>protoComponent_test'</code> (included with the original release of the CINDY repository) and double-click on it.
-Now, click the ''Run'' the on the ''Demo_of_protoComponent'' interface panel.  It will launch two components. The first one - <code>imageSource</code> - streams images from a file to a port (simulating a camera). The second one - <code>protoComponent</code> - takes these images and does some simple image processing (binary thresholding).
+Now, click the ''Run'' the on the ''protoComponent_test'' interface panel.  It will launch two components. The first one - <code>imageSource</code> - streams images from a file to a port (simulating a camera). The second one - <code>protoComponent</code> - takes these images and does some simple image processing (binary thresholding).