Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

To get started with this project, you (and your group members) need to set up the software tools needed.

1: Create and Prepare Your Dialogflow Agent (One Per Team)

You need a Google account for this.

2: Join GitHub Classroom and Clone the Student Project

XXX

3: Install MARBEL

  • We assume that you have already installed Eclipse and the MARBEL plug-in. If not, please follow the instructions here. Please check whether you are using the latest version of the plug-in by using the Eclipse menu (Help → Check for Updates).

  • INSTRUCTIONS ON GIT REPO AND DOWNLOAD OF PROJECT FILE

  • Launch Eclipse, make a new workspace, and import (select File then Import) the MARBEL dialog manager project from GitHub.

  • Add the downloaded JSON key file of your Dialogflow agent to the project directory.

  • In the.mas2g file, specify as flowkey the name of the JSON key file, and as flow agent the agent ID (click here to see more details).

4: Install SIC

Please follow the instructions here. Only works with Google Chrome which you therefore also need and can download here.

5: Launch the conversational agent system

  • Open a command terminal and navigate to the folder where you cloned the docker project

  • Enter docker-compose up dialogflow webserver and hit enter.

  • Open a second terminal and navigate to the subfolder sic-local in the docker folder.

  • Enter java -jar computer-browser.jar and hit enter. This will lead to a new browser window. Press ‘Ok’ without filling in a password.

  • Run the .mas2g file.

  • Check the boxes ending with ‘browser' and 'robot’ in the subsequently appearing window, and press 'OK'.

After running java -jar computer-browser.jar a pop-up should appear like the one in the left-hand corner of the picture below. Click okay without filling in a username and password.

Then a google chrome window should open. It should say it is being controlled by automated test software and display long string of random characters. In your terminal it should say ‘ChromeDriver was started successfully’ in one of the lines.

When you run the .mas2g file in your agent, another popup should appear like the one in the left-hand corner of the picture below. The empty box should be ticked next to the browser code that matches your google chrome window code, and then you hit OK

You should now see a window rendering the browser plug-in and hear the agent start talking. The rest now is up to you!

  • No labels