The tests that should be done are about the building, the recognition and the forecast processes.

1)Building: First donwnload Wayeb from here https://github.com/ElAlev/Wayeb. Assuming $WAYEB_HOME is the root directory of Wayeb:

$ cd $WAYEB_HOME

Then build a fat jar:

$ sbt assembly
If it prints a success message, it passes the test.

2) Recognition: In $WAYEB_HOME/data/demo/data.csv you may find a very simple dataset, consisting of 100 events. The event type is either A, B or C. In $WAYEB_HOME/patterns/demo/a_seq_b_or_c.sre you may find a simple complex event definition for the above dataset. It detects an event of type A followed by another event of type B or C. If we want to run this pattern over the stream, we must first compile this pattern into an automaton (make sure you have created a results folder under $WAYEB_HOME):

$ java -jar cef/target/scala-2.12/wayeb-0.2.0-SNAPSHOT.jar compile --patterns:patterns/demo/a_seq_b_or_c.sre --outputFsm results/a_seq_b_or_c.fsm

Now, results/a_seq_b_or_c.fsm is the produced serialized finite state machine. Note that we also provided as input a declarations.sre file. This file simply lets the engine know that the three predicates IsEventTypePredicate(A), IsEventTypePredicate(B) and IsEventTypePredicate(C) are mutually exclusive (i.e., an event can have only one type). This helps the compiler create a more compact automaton. We can use this FSM to perform event recognition on this simple dataset:

$ java -jar cef/target/scala-2.12/wayeb-0.2.0-SNAPSHOT.jar recognition --fsm:results/a_seq_b_or_c.fsm --stream:data/demo/data.csv --statsFile:results/recstats

If it prints information about the throughput and the number of matches, it recognizes the pattern in the stream and it passes the test. 

3) Forecasting: For forecasting, we first need to use a training dataset in order to learn a probabilistic model for the FSM. For this simple guide, we will use $WAYEB_HOME/data/demo/data.csv both as a training and as a test dataset, solely for convenience. Normally, you should use different datasets.

We first run maximum likelihood estimation:

$ java -jar cef/target/scala-2.12/wayeb-0.2.0-SNAPSHOT.jar mle --fsm:results/a_seq_b_or_c.fsm --stream:data/demo/data.csv --outputMc:results/a_seq_b_or_c.mc

The file results/a_seq_b_or_c.mc is the serialized Markov model. The final step is to use the FSM and the Markov model to perform forecasting:

$ java -jar cef/target/scala-2.12/wayeb-0.2.0-SNAPSHOT.jar forecasting --modelType:fmm --fsm:results/a_seq_b_or_c.fsm --mc:results/a_seq_b_or_c.mc --stream:data/demo/data.csv --statsFile:results/forestats --threshold:0.5 --maxSpread:10 --horizon:20 --spreadMethod:classify-nextk

The last command should return some classification statistics like precision, f1 and accuracy.

1) Get familiar with HELIOS instructions
2) Download sample codes and relevant libraries
3) Build the sample APP into a APK (you may modify the sample if you wish)
4) Install the APK to the Android phone (in the absence of a phone, you can use an emulator)
5) Verify with the Android phone that the app launches OK.
6) Send a unique message (such as a random number) to "BugChat" channel in the APP and do the following steps:
  - In the app, open the options menu (the three dots in the right-hand side after title)
  - Tap “Discover others”
  - Search for your nick name and WRITE DOWN the first 6 characters of your ID (it is in the format “nickname @ID”)
7) Fill in the survey and let us know
  - what was the message you sent, with rough time/date information, and
  - the first 6 characters of your ID

Install doc2json

doc2json is located at https://gitlab.ow2.org/decoder/doc_to_asfm

Linux installation

The application requires zlib https://zlib.net/ to retrieve the content of the documents and Clang Tools https://clang.llvm.org/docs/ClangTools.html to convert the user's parsing algorithm into an interruptible reading algorithm.

To install these libraries, you can type the following commands:

> sudo apt-get install zlib1g-dev clang libclang-dev > apt list --installed "libclang*-dev"

If the clang version is less than clang-10 (for instance clang-6), the next cmake build process may fail and you need to update to clang-10 with the following commands

> sudo apt-get install clang-10 libclang-10-dev > sudo apt-get purge --auto-remove libclang-common-6.0-dev > sudo ln -s /usr/bin/clang-10 /usr/bin/clang

You can also check that llvm provides its own header files to the Clang Tools. 

> llvm-config --includedir

should answer a path that contains llvm-xx. Fedora, for instance, returns /usr/include, which prevents the Clang Tools to find some headers like <stddef.h> that are required for string manipulation during the source to source transformation. In such a case, you can try the docker installation that is more robust.

Please note that if after having tested doc2json, you need to revert to your original clang 6 version, just type

# do no use these commands before having built the project and the algorithms libraries > sudo rm /usr/bin/clang > sudo apt-get install clang

Then you can download and build the project

> git clone git@gitlab.ow2.org:decoder/doc_to_asfm.git doc2json > cd doc2json > mkdir build > cd build > cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$PWD .. > make -j 4 # make test is optional = to check if doc2json works on the internal documentation > make test > make install

Docker installation

To download and build it (Docker users) :

> git clone git@gitlab.ow2.org:decoder/doc_to_asfm.git doc2json > cd doc2json > sudo docker build -t doc2json_img . > docker run --name doc2json -it doc2json_img bash # in the docker container > cd /doc2json

Minimal test (to check doc2json works)

Under a Linux system, you can then run some test examples in the build directory, which is also the installation directory, you can type

> ./bin/doc2json ./share/doc2json/libInvoiceReader.so -c ./share/doc2json/config-invoice.xml ../test/invoice.ods -o test/invoice.json > ./bin/doc2json ./share/doc2json/libTextWordReader.so -c ./share/doc2json/config-text-word.xml ../test/StructuredDocument_french.docx -o test/StructuredDocument_french_word.json > ./bin/doc2json ./share/doc2json/libTextOpenofficeReader.so -c ./share/doc2json/config-text-openoffice.xml ../test/StructuredDocument_french.odt -o test/StructuredDocument_french_openoffice.json

Under the Docker container, you can run the same test examples from the /doc2json directory

> ./bin/doc2json ./share/doc2json/libInvoiceReader.so -c ./share/doc2json/config-invoice.xml src/test/invoice.ods -o src/test/invoice.json > ./bin/doc2json ./share/doc2json/libTextWordReader.so -c ./share/doc2json/config-text-word.xml src/test/StructuredDocument_french.docx -o src/test/StructuredDocument_french_word.json > ./bin/doc2json ./share/doc2json/libTextOpenofficeReader.so -c ./share/doc2json/config-text-openoffice.xml src/test/StructuredDocument_french.odt -o src/test/StructuredDocument_french_openoffice.json

to extract the content of the documents in the json format. You can open the document ../test/StructuredDocument_french.docx and compare its content with the result of the extraction, that is the file test/StructuredDocument_french_word.json.

Then, in the build directory for Linux users and in the /doc2json/src directory for Docker users

diff test/StructuredDocument_french_openoffice.json test/StructuredDocument_french_word.json

should show no differences between the two json extracted files even if the origin format (word versus openoffice/opendocument) is very different.

A utility create-reader.sh is provided to generate a parsing library from a custom user's parsing algorithm. Hence the command (in the build directory for Linux users and in the /doc2json directory for docker users)

./bin/create-reader.sh -I . share/doc2json/InvoiceReader.cpp

generates again the parsing library share/doc2json/libInvoiceReader.so from the parsing algorithm share/doc2json/InvoiceReader.cpp. The transformation into a state machine model is generated in the file share/doc2json/InvoiceReaderInstr.cpp.

Apply doc2json to your documents (a text with a title and sections, subsections, subsubsections, ...)

We now suppose that your document is named file.docx or file.odt. It should have a title identified by a specific style.

You may run the test in /tmp with an environment variable DOC2JSON_INSTALL_DIR that refers to the installation directory of doc2json. This is the build directory for Linux users. You can type

export DOC2JSON_INSTALL_DIR=$PWD

in the build directory before trying the test. This environment variable is automatically set for docker users. But you need copy your document into the /tmp directory of the docker container with the command

docker cp .../file.docx doc2json:/tmp

You need to look at the name of the styles the headings of your document.
By default, for a french word document, these styles are Titre, Titre1, Titre2, Titre3, ... For an english word document, they may be Title, Heading1, Heading2, Heading3, ... You need to provide these styles to doc2json by modifying the configuration file config-text-word.xml and by replacing the french Titre by the styles that appear in the style ribbon of Word.

cp $DOC2JSON_INSTALL_DIR/share/doc2json/config-text-word.xml /tmp # edit config-text-word.xml and replace Titre1 by Heading1 or by the styles of the different sections of your document

If the title is not recognized, doc2json will answer "bad generation of the output format!" with a corrupted output json document. This should be modified for a future version.

For the opendocument format, you need to find the style ribbon by clicking on the parameter menu (top right) of libreoffice. Then styles like "Heading 1" should be replaced by "Heading_20_1" in config-text-openoffice.xml - spaces are replaced by "_20_". Sometimes libreoffice renames these styles internally. For instance, it may rename the "Title" style with "P1" or with "P2". The parsing algorithm is not smart enough to recognize this renaming - it will be in a future version. So if the extraction fails, you can unzip your file.odt, and then edit the file content.xml to look for the text of your "Title" and see what is the associated style. Do not spend too much time on that point if it fails.

Then the adequate command

> cd /tmp > $DOC2JSON_INSTALL_DIR/bin/doc2json $DOC2JSON_INSTALL_DIR/share/doc2json/libTextWordReader.so -c /tmp/config-text-word.xml file.docx -o file.json > $DOC2JSON_INSTALL_DIR/bin/doc2json $DOC2JSON_INSTALL_DIR/share/doc2json/libTextOpenofficeReader.so -c /tmp/config-text-openoffice.xml file.odt -o file.json

should extract in file.json the sections and the text of your document.

Feedback questionnaire

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

Campaign Mailing List

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and to join the mailing list for this campaign, in order to interact with the Campaign Manager. Find out more about Reachout informed consent.

Please read carefully these instructions before completing the Questionnaires.

To connect to the SMOOTH platform and perform the test, please use this link.

The beta version of the software can be accessed at https://www.gotriple.eu  

Instructions:

Test 1: Goal to find which authors published the most on a topic

1. Go to the GoTriple Beta testing platform via the above web address
2. Enter a search term of your choice 
3. Browse the results of the search
4. Select the 'Visual' View of results 
5. Explore the visual view elements
6. Refine the results to show papers from just one of the disciplines provided 
7. Clear the refinement to show results from all disciplines again
8. Find which authors published the most on this topic
9. Click on an author name to view other publications from this author.

Test 2: Goal to produce a Knowledge Map and examine it

1. Make a new search on 'Society + Covid'
2. Refine the results to show only papers published in 2020 
3. Clear the 2020 selection
4. Find book chapters published on this topic (same search Society + Covid)
5. Clear the book chapter selection to return to the overall search list
6. Create a Knowledge Map for this search (be patient it takes a bit of time!) 
7. Examine the knowledge map and see the grouped publications 
8. Return to Home Page

Test 3 Goal: Examine Disciplines and produce a Streamgraph

1. Examine the Disciplines Tab - try clicking on any that are of interest to you
2. View a list of publications from a discipline 
3. Use the filter to refine the results shown
4. Return to the Home page
5. Make a new search on the term 'Co-design'
6. View the Streamgraph for this search   
7. Examine the results of the Streamgraph
8. Visit the GOTRIPLE tab to view project information 

The Toolbox is accessible without the need to log in to the system, but the options are limited to pure search. You can see that without registering the options in the menu are very few. To perform this campaign, we would like all involved users to first sign in into the DataBench Toolbox to get a user profile that you will use throughout the campaign:

- Go to https://databench.ijs.si/ and click on “Sign up” option located at the top of the page on the right side.

- Fill in the form to generate your new user by providing a username and password of your choice, your organization, email, and your user type (at least Technical for this exercise).

Once you have created your user, please sign in with it to the Toolbox. You will be directed to the Toolbox main page again, where you could see that you have more options available. 

Besides the options available through the menu, the main page provides:
A) a carrousel with links,
B) User journeys for users of different profiles: Technical, Business and Benchmarks providers,
C) Videos aimed at these 3 types of users explaining briefly the main functionalities offered for each of them,
D) Shortcuts to some of the of the functionalities, such as FAQ, access to the benchmarks or knowledge catalogues, the DataBench Observatory, etc. 

A) Get information about DataBench pipelines and blueprints

This campaign aims at providing you the means to search and browse existing data pipelines and the explanations on how to map your own architecture to efforts such as the BDV Reference model, the DataBench Framework and the mappings with existing initiatives. 

We encourage you to first go to the Technical user journey  accessible from the front-page of the Toolbox, read it and follow the links given to you to get acquainted with the entries related to blueprints and pipelines. In the “Advanced” user journey you will find the following:

- Link to the DataBench Framework and it relation to the BDV Reference Model, where you can find an introduction to the different elements that composes the DataBench approach towards technical benchmarking.

- Link to the DataBench Generic Pipeline , where an explanation of the 4 main steps in data pipelines are explained. These 4 steps are the basic building blocks for the mappings to other blueprints and existing initiatives.

- User Journey - Generic Big Data Analytics Blueprint : This is the main piece of information that you need to understand what we mean by mapping an existing architecture to our pipelines and blueprints. You will find links to the generic pipeline figure.

- Practical example of creating a blueprint and derived cost-effectiveness analysis: Targeting the Telecommunications Industry .

- Ways to report your suggestions for new blueprints, by using the Suggest blueprint/pipeline option  under the Knowledge Nuggets menu 

Below is a summary of the minimal set of actions we encourage you to do:

1. Go to the User journeys area of the main page and click on “Technical”.
   
   2. Go to the link to the User Journey: Generic Big Data Analytics Blueprint  at the bottom of the “Advanced” area of the page. 

3. Read and understand the different elements of the pipeline (the 4 steps) and the elements of the generic blueprint as described in the previous link.

4. Check examples of already existing blueprints. In order to do that use the search box located at the top right corner and type “blueprint”. Browse through the blueprints. 

B) Desk analysis

Once you are familiar with the DataBench Toolbox and the main concepts related to the blueprints, you need to do some homework. You should try to map your own architecture to the DataBench pipeline and the generic blueprint. We suggest the following steps:

- Prepare a figure with the architecture you have in mind in your project/organization. 

- Create links to the 4 steps of the data pipeline and generate a new figure showing the mapping.

- Create links to the Generic Big Data Analytics Blueprint  figure and generate a new figure showing the mappings. In order to do so you might use the generic pipeline figure and particularize to your components as it was done in the example provided for the Telecommunications Industry . 

C) Upload your blueprint to the Toolbox

- Upload your files as pdf or images by using the Form of suggestion of blueprints   available from the Knowledge Nuggets menu. Try to include a description with a few words about the sector of application of your blueprint, main technical decisions or anything you might find interesting to share. 

- The DataBench project will revise the blueprints and publish them into the platform acknowledging your authorship. 

Congratulations! You have completed the assignment of this campaign! Go now to fill in the feedback questionnaire. Please note that filling in the questionnaire will be your ticket for incentives.

The Toolbox is accessible without the need to log in to the system, but the options are limited to pure search. You can see that without registering the options in the menu are very few. 

Initial steps to log in as a Toolbox user

To perform this campaign, we would like all involved users to first sign in into the DataBench Toolbox and create  a user profile that you will use throughout the campaign:

- Go to http://databench.ijs.si/ and click on “Sign up” option located at the top of the page on the right side.
- Fill in the form to generate your new user by providing an username and password of your choice, your organization, email, and your user type (Technical and/or Business, depending on your preferences and skills).

Once you have created your user, please sign in with it into the Toolbox. You will be directed to the Toolbox main page again, where you could check that you have more options available. 

Besides the options available through the menu, the main page provides:
A) a carrousel with links,
B) User journeys for users of different profiles: Technical, Business and Benchmarks providers,
C) Videos aimed at these 3 types of users explaining briefly the main functionalities offered for each of them,
D) Shortcuts to some of the functionalities, such as FAQ, access to the benchmarks or knowledge catalogues, the DataBench Observatory, etc. 

A) For Technical Users

This campaign aims at using the user journeys as starting point to help you navigating the tool. We encourage you to click on the Technical user journey, read it and follow the provided links to get acquainted with the tool and what you can do with it. Get used to the main two catalogues: the benchmarks catalogue (tools for big data and AI benchmarking), and the knowledge nuggets catalogue (providing information about technical and business aspects related to benchmarking and big data technologies). Learn about existing big data architectural blueprints and browse some of them. 

Additionally, if you already have a goal in your mind (i.e. finding a benchmark for testing a specific ML model, or compare the characteristics of different NoSQL databases), we encourage you to try to find the appropriate benchmark and report your conclusions later in the questionnaire. 

Below is a summary of the minimal set of actions we encourage you to do:

1. Go to the User journeys area of the main page and click on “Technical”. 

2. Read the content of this page, divided into advice for “Beginners” (first-time users) and “Advanced” (providing extra recommendations of what to do next). Focus first on the “Beginners” area and click on the different links to browse to the different options to get used to the tool. We recommend you to come back to the User journey page  until you click on all the available options for beginners, but feel free to stray and use the navigation and links from other pages to get used to the tool. After you finish clicking on all the options for beginners, you should have seen the benchmarks and knowledge nuggets catalogues, used some of the search functionalities and browsed some of the existing architectural blueprints. You are now ready to go further!

3. Focus now on the “Advanced” area of the User journey page . 

- Here you will find ways to suggest new content via web forms (i.e. new benchmarks you might know that are missing in the catalogue, a version of a big data blueprint you are dealing with in a project, or a new knowledge nugget based on your experience). We are not expecting you to fill-in these forms at this stage, but just acknowledge their potential value (and feel free to contribute any time).  

- You will find also links to specific more advanced user journeys or practical examples at the end of the advanced user journeys. Click on the ones that take your attention and start navigating via the links offered by them. From this moment we expect that you know the main options of the Toolbox and how to navigate and browse through it. You should have noted by now that both benchmarks and knowledge nuggets are annotated or categorized with clickable tags, which makes navigation through related items possible.  

4. Get used to the search functionalities. The Toolbox offers 4 types of search:
- Search text box located at the top right corner of the pages. This is a full text search. You can enter any text and the results matching that text from both the benchmark and knowledge nuggets catalogues will appear.

- Search by “BDV Reference Model”  option from the menu allows you to have a look at the model created by the BDV PPP community (check the BDV SRIA  for more details). The model is represented graphically and is clickable. If you click in any of the vertical or horizontal layers of the model you will be directed to the benchmarks and/or knowledge annotated in the Toolbox to these layers. Browse through this search.

- Search by “Guided benchmark search” . In simple terms this is a search by the tags used to annotate benchmarks and knowledge nuggets. These tags range from technical to business aspects. You can click on the categories of tags to find related information. Browse to some of the options of this search.  

- Finally, the “Search by Blueprint/Pipeline”  option allows a search that presents graphically a generic architectural blueprint developed in DataBench with the most common elements of a big data architecture. The blueprint is aligned with 4 steps of a DataBench Generic data pipeline  (data acquisition, preparation, analysis and visualization/interaction). The graphic is clickable both at the level of the four steps of the pipeline and in some of the detailed elements of the blueprint. Click on the parts of the diagram you are interested to find a list of existing benchmarks and nuggets related to it. Browse some of them. There are nuggets that show a summary of existing big data tools for each of the elements of the pipeline. See if you find it easy to browse through the results .

Congratulations! You have completed the assignment of this campaign! Go now to fill in the feedback questionnaire. 

NOTE – Some of the available benchmarks can be deployed and run in your premises. Those are listed first in the Benchmark catalogue and when you click on them you will find the configuration file at the bottom of their description. If you want to run any of them, you should have dedicated infrastructure to do so. We are not expecting you to do so in this exercise.

B) For Business users

As for technical users, this campaign aims at using the user journeys as starting point to help you navigating the tool. We encourage you to click on the Business user journey, read it and follow the links given to you to get acquainted with the tool and what you can do with it. Get used to the main two catalogues: the benchmarks catalogue (tools for big data and AI benchmarking), but mainly to the knowledge nuggets catalogue (providing information about technical and business aspects related to benchmarking and big data technologies). Learn about existing big data architectural blueprints and browse to some of them, as they apply to different industries and might be of interest for business purposes.

Additionally, if you already have a goal in your mind (i.e. finding most widely used business KPIs in a specific sector), we encourage you to try to find the appropriate information in the knowledge nugget catalogue and report your conclusions later in the questionnaire. 

Below there is a summary of the minimal set of actions we encourage you to do:

1. Go to the User journeys area of the main page and click on “Business”. 

2. Read the content of this page, divided into advice for “Beginners” (first-time users) and “Advanced” (providing extra recommendations for what to do next). Focus first on the “Beginners” area and click on the different links to browse to the different options to get used to the tool. We recommend you to come back to this User journey page  until you click on all the available options for beginners, but feel free to stray and use the navigation and links from other pages to get used to the tool. After finishing clicking on all the options for beginners, you should have seen the benchmarks and knowledge nuggets catalogues, used some of the search functionalities and browsed some of the existing architectural blueprints. You are now ready to go further!

3. Focus now on the “Advanced” area of the User journey page .
- You will find links to different elements, such as nuggets related to business KPIs, by industry, etc. Browse through them and follow the links.

- You will find ways to suggest new content via web forms (i.e. a new knowledge nugget based on your experience). We are not expecting you to fill-in these forms at this stage, but just acknowledge their potential value (but feel free to contribute any time).  

- You will find also links to specific more advanced user journeys or practical examples at the end of the advanced user journeys. Click on the ones that take your attention and start navigating via the links offered by them. From this moment we expect that you know the main options of the Toolbox and how to navigate and browse through it. You should have noted by now that both benchmarks and knowledge nuggets are annotated or categorized with clickable tags, which makes navigation through related items possible.  

5. Get used to the search functionalities. The Toolbox offers 4 types of search:
- Search text box located at the top right corner of the pages. This is a full text search. You can enter any text and the results, matching that text from both the benchmark and knowledge nuggets catalogues, will appear.

- Search by “BDV Reference Model”  option from the menu allows you to have a look at the model created by the BDV PPP community (check the BDV SRIA  for more details). The model is represented graphically and is clickable. If you click on any of the vertical or horizontal layers of the model you will be directed to the benchmarks and/or knowledge annotated in the Toolbox to these layers. Browse through this search.

- Search by “Guided benchmark search” . In simple terms this is a search by the tags used to annotate benchmarks and knowledge nuggets. These tags range from technical to business aspects. You can click on the categories of tags to find related information. Browse to some of the options of this search.  

Finally, the “Search by Blueprint/Pipeline”  option allows a search that presents graphically a generic architectural blueprint developed in DataBench with the most common elements of a big data architecture. The blueprint is aligned with 4 steps of a DataBench Generic data pipeline  (data acquisition, preparation, analysis and visualization/interaction). The graphic is clickable both at the level of the four steps of the pipeline and in some of the detailed elements of the blueprint. Click on the parts of the diagram you are interested to find a list of existing benchmarks and nuggets related to it. Browse some of them. There are nuggets that show a summary of existing big data tools for each of the elements of the pipeline. See if you find them it easy to browse through the results .
6. This part of the test is not guided, as we expect you to navigate through the options you have seen previously. Once you know how to navigate, try to find information of interest for your industry or area of interest:
• Try to find information about the most widely used KPIs or interesting use cases.
• Try to find information about architectural blueprints for your inspiration.  

Congratulations! You have completed the assignment of this campaign! Go now to fill in the feedback questionnaire.

Participants of the survey must have before answering the questionnaires must:

• Complete at least one pilot scenario
• Have clear instructions about the usage of the software as well as the goals of each scenario
• Answer all the questions of the survey which is divided in three main sections:
  • General section concerning participant's information
  • Evaluation of the pilot as a whole
  • Evaluation of each application included in the pilot

You will find more help in the following guides:

• Unit test amplification with Descartes & DSpot
• DSpot hands-on example
• Descartes and DSpot demo applied to OW2 Joram
• Configuration test amplification with CAMP
• Crash Reproduction Demo with Botsing

Discover more  STAMP software on GitHub.

Feel free to contact the support team and to contribute.

For the beta testing campaign - create a user group in the tool, create a campaign, answer a questionnaire and review the results of the assessment. The URL of the website is (http://energyshield.epu.ntua.gr/) . Information and guide of the platform is included here: (https://1drv.ms/w/s!Avx-hU-EvNxviEse2KU6hPqEoY4O?e=Hn5byP)

Just follow the link to the questionnaire.

Please follow the https://demo.safe-deed.eu/ link and evaluate all subordinate applications. Instructions can be found in embedded videos in the main page of the demonstrator as well as in the applications' pages. Additional explanations are also provided when appropriate.

Introduction

From now, you are going to act as a passenger, which is a person who wants to share a car with other people (at least with a driver) for a short period of time from one point to another.

Instructions

Instructions will be provided within the survey. Please, go to the survey

Introduction

From now, you are going to act as a driver, which is a person who wants to rent a car and drive it for a short period of time from one point to another.

Instructions

Instructions will be provided within the survey. Please, go to the survey

Introduction

From now, you are going to act as a individual owner, which is a person who has a vehicle and wants share costs allowing other users to rent it for a short period of time.

Download and Install the Mobile App

1. Download .apk from https://drive.google.com/file/d/1xXMWmUq4D5UzTbzt83fazpkWSkeeGQ9R/view?usp=sharing.
2. Install the Android App.
3. Run the Carsharing App.
4. Allow Carsharing to access location: Press Allow all the time.
5. Allow Carsharing to access photos, media and files: Press Allow.

Sign up and Login

Now you are going to create your credentials. Since the Agilia solution is based on a permissioned Blockchain network, the credentials are couple of certificates. These certificates are encrypted and stored in your mobile using a password.

1. Press Create Certificate.
2. Fill a Name and a Password.
3. Press Create
4. Logout:
   1. Open the burger menu.
   2. Press Exit.
5. Import certificates of a created user:
   1. Press Import Certificate.
   2. Find the Certificate file in /Android/data/com.carsharing/files.
   3. Fill the Password that you have entered previously in order to decrypt your certificates.
   4. Press Submit.

Create a new Vehicle

You need to register your vehicle in the application to allow other users to rent it. 

1. Navigate to the Vehicles Screen (Second option of the burger menu).
2. Create a new vehicle:
   1. Press the + button.
   2. Fill, at least, the required fields: License Plate, Brand, Model, Colour, Seats, Year, Vehicle State. If you fill the vehicle state as BAD, your vehicle can not be rented.
   3. Press the Save button.
3. Now, in the vehicle list, you can see the car that you have created.

Create an Offer

You need to create an offer in order show to other users that your car is available to be rented.

1. Navigate to the My Offers Screen (Third option of the burger menu).
2. Create a new offer:
   1. Press the + button.
   2. Fill, at least, the required fields: License Plate, Price for KM, Price For Time, Start Date, End Date, Escrow and Start Place.
   3. Press the Save button.
3. Now, in the My offers list, you can see the offer that you have created.

Watch trips related to your vehicle

You can see the trips associated to your vehicles after, at least, one driver reserve a trip with your car.

1. Navigate to the Vehicles Screen (Second option of the burger menu).
2. Find the vehicle that you want to inspect (you can use the filters).
3. Press the vehicle.
4. Press the ... button (blue button) and the eye option (green color).
5. This screen shows the trips related to your selected vehicle.
6. Press a the trip that you want to see the details.

Withdraw credit (CSCoins)

After at least one trip finished you can see that your CSCoins has increased. Then you can withdraw your CSCoins. 1 CSCoins equals 1 Euro

1. Press the CSCoins Button (In the header bar in the top right-hand).
2. Press Withdraw CSCoins.
3. Fill the email of your Paypal Sandbox account. Please, select one of the following accounts:
   1. sb-ejr771011751@personal.example.com
   2. sb-fxu4391011730@personal.example.com.
4. Fill the amount.
5. Press Withdraw.
6. When the Paypal workflow is finished, press OK.
7. The transaction can take some minutes. Please, refresh the screen (pull-to-refres gesture).

In order to test the ReachOut platform, you will need to:

1. Visit https://reachout-project.eu
2. Register as a campaign manager
   You will need to provide your details, e-mail address, login and password.
   You will receive a message to your e-mail address with an activation link.
3. Create your project
   You will have to fill in the project details.
4. Create your campaign with the appropriate campaign details.
   Note that you can use the XWiki syntax for formatting the details (links, bullets, ...)
5. Customize the questionnaire in LimeSurvey
   You can do this by clicking on the "Customize and activate the associated questionnaire" button. Log into LimeSurvey using your ReachOut login and password provided during the registration.
   Once in LimeSurvey, you can edit the questions.
6. Activate the questionnaire in LimeSurvey
7. Manage the progress of your campaign using the campaign dashboard
   To do this, go back to your home page on the ReachOut website, and click on the Dashboard button below your campaign details. Then, edit the dashboard, save.
8. Fill in the questionnaire (as a beta tester)
   To do this, log out of LimeSurvey and ReachOut, go to the ReachOut website, click on "Checkout existing campaigns" and fill in the questionnaire.
9. View the answers on LimeSurvey
   Log into LimeSurvey and go to your campaign on LimeSurvey.
   Then, click on Statistics in the left menu, then on the "Simple mode" button top left. You can view statistics about the answers that have been provided by beta testers.

STEP 1: Installation and creation of the working environment

1. Download Parsec on the Parsec website - Get Parsec.
2. Install the software on your browser following the instructions received by email. 
3. Open Parsec on your browser.
4. Create your organization, your workspaces.

STEP 2 : Invite a new user in your organization

1. Invite a new user by referring to the UG (user guide). 
2. Share a workspace with the user.
3. Test the collaborative file synchronization with your guest by modifying the content of a file. Then check if all the modifications made in the file are taken into account. 
4. Test the history function on the same file. (see UG) 

STEP 3 : Your workspace and its features

1. Import files into your workspaces from the Parsec software interface.
2. Import files into the shared Parsec directory using your PC file explorer. 
3. Modify a file, save and exit.
4. Test the different workspace features:

• Going back in time
• Sharing files
• Renaming a file

Scénario du test

ÉTAPE 1 : Installation et création de l’environnement de travail

1. Télécharger Parsec sur Get Parsec - Parsec 
2. Installer le logiciel selon votre navigateur en suivant les instructions reçues par mail. 
3. Ouvrir Parsec sur votre navigateur
4. Créer votre organisation, vos espaces de travail

ÉTAPE 2 : Inviter un nouvel utilisateur dans votre organisation

1. Inviter un nouvel utilisateur en vous référant au GU (guide d'utilisation). 
2. Partager un espace de travail avec l’utilisateur.
3. Tester la synchronisation collaborative des fichiers avec votre invité en modifiant le contenu d’un fichier. Vérifiez ensuite la prise en compte de toutes les modifications effectuées dans le fichier. 
4. Testez la fonction historique sur même fichier. (voir GU) 

ÉTAPE 3 : Votre espace de travail et ses fonctionnalités

1. Importer des fichiers dans vos espaces de travail depuis l’interface du logiciel
2. Importer des fichiers dans Parsec depuis votre explorateur de fichier PC   
3. Modifier un fichier, enregistrer et quitter 
4. Tester les différentes fonctionnalités de l’espace de travail 

• Remonter dans le temps 
• Partager des fichiers 
• Renommer des fichiers 

- Checkout project using git:

git clone https://github.com/gibello/zql.git

- Build project, using maven:

cd zql/
mvn clean install

1. Setting up Modelio CAMEL designer

• Download and install Modelio open source 4.1 available at www.modelio.org/downloads/download-modelio.html
• Deploy CAMEL Designer Module on your open project. Instructions to deploy CAMEL Designer are available here github.com/Modelio-R-D/CamelDesigner/wiki/Installation
• CAMEL Designer module releases are available from this link github.com/Modelio-R-D/CamelDesigner/releases

2. Create Camel Model: Steps to complete

• Create an empty package by right-clicking your root UML project or any other Package -> Create Element -> Package
• Right-click an empty package to show available commands and click on Camel Designer -> Create element -> Create Camel Model 

Expected results:

An empty Camel Model is created.

3. Create metric type model: Steps to complete

• Right-click a CAMEL Model to display the list of available commands
• Click on Camel Designer -> Create element -> Metric_Model 

Expected results:

A metric type model is created inside the CAMEL model.

4. Create software component: Steps to complete

• Create a Deployment Model: right-click on the CAMEL model -> Camel Designer -> Create element -> Deployment Model
• Create a Deployment Diagram: right-click the deployment model -> Camel Designer -> Create Diagram -> Deployment model Diagram
• Open the deployment model diagram
• In the palette, in the Deployment Type box, select the Software Component icon, then draw a rectangle inside the deployment model diagram to create a Software Component 

Expected results:

A software component is created and displayed in the diagram.

Start by cloning the repository found at https://bitbucket.alexandra.dk/projects/OL/repos/usecase-3

Details for the test scenario and a Step-by-Step guide can be found in the "documentation" sub-folder, which can be broken into 3 main tasks:

• Building the codebase.
• Deploying a number of services.
• Running through a simple use case.

1. Install Melodic on your machine as described on the Melodic download page (scenario1)
2. Deploy simple two component application. scenario2.pdf
3. Install the Eclipse oxygen-based Camel editor, which enable you to create your model, manual available on Melodic's website (scenario3)
4. Model and deploy your own application using Melodic platform. scenario4.pdf

We prepared a questionnaire composed of 30 questions.

Install and configure the individual services (check the “Delivery and Usage” sections on each document)
• ARCHITECT cloud patterns service
• OPTIMUS simulation service
• MCSLA service
• ACSmI discovery/contracting/monitoring services
• ADAPT deployment orchestrator
• ADAPT Violation handler
Install and configure DECIDE DevOps framework (check the “Delivery and Usage” section)
• DECIDE DevOps framework
Connect to the DevOps framework web interface and follow the workflow to create, deploy and manage a multi-cloud application (check the “User Manual” sections on the aforementioned documents)

To run a simple experiment run:
spark-submit  master local[*]  class eu.linkedeodata.geotriples.GeoTriplesCMD /path_to/geotriples-spark.jar spark -i /path_to/greece-natural-a/gis_osm_natural_free_1.shp -o /path_to/folder_to_store_results  /path_to/greece-natural-a/gis_osm_natural_free_1.ttl

We would like to check if the RML processor handles the RML term maps as expected (see https://rml.io/specs/rml/#term-map). 

We want the user to be able to provide any term map (mostly constant- or template-valued) and to get the requested results. The term maps are defined by editing the .ttl file (the rr:objectMap fields, there are some examples in the document).
So we would like to check if the program can handle any given term map. So you can try and execute the project with different term maps (mostly template-valued) to see how it handles them.

The detailed instructions to execute the beta test are available at: https://elastest.io/docs/try-elastest/

For this use case, we consider an office agent that works at Piraeus Port, in Athens, Greece and needs to have an overview of the vessels position and status located near the port, as well as track any occurred illegal fishing activities in the open sea of Saronic Gulf.

After the successful log in into the MSA UI follow the guidelines described below:

1. Pan around the map and inspect the relevant sea area to have an overview of the vessels location as well as the events occurring.

2. Click on any vessel or event marker on the map to get more information for that particular marker. Try investigating the vessels destination, speed and vessel type. As concerns the events markers, for some types of events (e.g. proximity & in-areas events) after clicking on the marker you can see that extra geometries are displayed as overlays connecting the vessels that were engaged in a proximity event or the geometry of the area that a vessel entered in that exact time.

3. Using the sidebar tools menu located at the left side of the browser's window viewport, click on the layer's icon button and click between the available data layers to toggle them on-off.

4. By using the Filtering icon button that's underneath layer's button try to filter the vessels by their type. Toggle between any desired vessel type and keep those needed. Do the same for event types accordingly.

5. Find out how many events (simple and Forecast ones) are in this particular sea area. This information is kept under the Events icon button in the left sidebar. Hit the Events icon having the events panel list showing up. There are two tabs, "Simple Events" & "Forecast Events". Now hover upon the events list and click on any event card. The map is zooming in into the event's specific location. Try this process for various types of events.

6. Now span across the map and hit on a vessel marker. In the popup box showing the vessel's description, there's a 'Past track' button. Try clicking on this button to investigate the vessel's past track (trajectory) and look closely to find out any past events that may be occurred in that past trajectory line.

7. Congratulations! Following the above steps you've had an overview of the current maritime situation of this case area by investigating all the current vessels location and occurred events as well as you were able to track any vessels that are about to be engaged into illegal activities such as illegal Fishing.

Install JmlGen

JmlGen is located at https://gitlab.ow2.org/decoder/jmlgen .

To download and build it:

$ git clone https://gitlab.ow2.org/decoder/jmlgen.git
$ cd jmlgen
$ mvn clean install

Minimal test (to check JmlGen works)

You can then run a test example, as follows:

$ java -jar target/jmlgen-0.0.1-SNAPSHOT.jar src/main/resources/jmlgen.properties

Some java code with JML inside should be produced in /tmp/jmlgen (the original java code is in src/test/java/eu/decoder/sample_jmlgen/ directory).
To see it, for example:

$ cat /tmp/jmlgen/src/test/java/eu/decoder/sample_jmlgen/Sample*

(note that you may customize the output directory by editing src/main/resources/jmlgen.properties, and changing the value of "target" property).

Apply JmlGen to a real project

We will take as example the OW2 sat4j project (https://gitlab.ow2.org/sat4j).

You may run the test in /tmp:

$ cd /tmp
$ git clone https://gitlab.ow2.org/sat4j/sat4j.git

Now create a JmlGen configuration file (let's say, /tmp/sat4j.properties), with the following content (you may copy/paste it):

root: /tmp/sat4j
destination: /tmp/sat4j-JML
sourcepath: org.sat4j.br4cp/src/main/java:org.sat4j.core/src/main/java:org.sat4j.intervalorders/src/main/java:org.sat4j.maxsat/src/main/java:org.sat4j.pb/src/main/java:org.sat4j.sat/src/main/java:org.sat4j.sudoku/src/main/java

(Note: sourcepath lists all source folders, separated with colons; in many java projects, it would simply be set to "src/main/java").

Go back to the directory where you installed JmlGen, and run it:

$ java -jar target/jmlgen-0.0.1-SNAPSHOT.jar /tmp/sat4j.properties

You should see logs in the console, that detail where JML annotations have been inserted: go in some corresponding files (under /tmp/sat4j-JML) to discover JML annotations.

For example, the following command should display some JML annotations inserted in the SuDoku.java sample of Sat4j:

$ cat /tmp/sat4j-JML/org.sat4j.sudoku/src/main/java/org/sat4j/apps/sudoku/SuDoku.java | grep "/*@"

Note some annotations can be of immediate interest: for example, "non_null" annotations reflect that a method result should be tested to null, as the method was called without check (for a call like "method1().method2()", JmlGen would annotate "method1()" as "non_null", which denotes a risk of null pointer exception). A plain text search for "non_null" annotations, without any analysis tool, can be profitable.

Apply JmlGen to your own project

Now you are ready to use JmlGen on your own! And report bugs/issues at https://gitlab.ow2.org/decoder/jmlgen/-/issues.

When done, use any 3rd-party JML tool (like OpenJml) to perform analysis of your java code, now instrumented by JmlGen.

The software aims at creating artificial tabular data. The system takes as input a table and automatically trains a Machine Learning model capable of generating an artificial copy. The synthetic version retains the same statistical properties but is void of sensitive information.

The process is composed of 4 steps:

1.Register and login (http://app.intuite.ai/)
After filling in the registration form, you will receive a link to confirm your email. Upon verification of your email, a password will be sent to you.
2.Load Data
3.Train model
4.Synthesize new data
5.Download data

The user guide is available at:

https://docs.google.com/document/d/1QEh5upzahsgrKTORPP9UBRp_EZiky1rJ35fAk2zNMU8/edit?usp=sharing

• Open http://beta.crossminer.org/app/kibana#/dashboards
• Select a dashboard, for instance "scava-overview"
• Select a project from "Project selection" view
• This has the effect to filter data for the selected projects in other views.
• you can manage filters from the top left bar of the window.
• On top right of the window, you can edit the time selection (by default 10 years)
• Click on "Dashboard" from the left pane to select another dashboard.
• The same logic can be applied on all dashboards
• Last part is to understand how dashboards are created. Let's follow this short tutorial: https://www.reachout-project.eu/view/Crossminer/kibana

A) For Service Providers (Looking for acquiring Data inside the Marketplace):

1. Go to https://ng8.datagora.eu/login and click on "Sign in" button on the right upon side of the web
   2. Enter in the EMAIL: "serviceprovider1@test.com" and this password
   3. In the left side of the Application you see "Main Menu", and you click in  "Catalogue section". Apply some filters to the Data Signals Catalogue and search for any signal you are interested.
   4. Go to "Data Discovery". In this view, you can configure and personalize the type of "Data Requests" you aim to retrieve from the Marketplace. Apply and set any filter you consider interesting for your service and finally press on "Discovery". E.g. Signal Type: Vehicle Speed (or more) / Add Suggestions (if needed) / Duration: All years / Location: Spain
   5. Check the "Discovery Results" of available data in the marketplace. Then, check the "Analytics" or "Context Filtering" to get access to all the functionalities. Then, click on "Create Data Request".
   6. Congratulations! You have created your first Data Request, just go to "Main Menu" and click in "Data Wallet" and you can see a drop menu with "Data Requests" and Data Transactions". Click on "Data Requests" to see the one you have created.  

B) For Data Owners (Accepting Data Requests and Exchange my data generated):

1. Go to https://ng8.datagora.eu/login and click on "Sign in" button on the right upon side of the web
   2. Enter in the EMAIL: "ownertest@test.com" and this password
   3. Go to the upper part of the Application, and firstly select the type of Device from you would accept to share your data. Two categoires "Vehicles" and "Buildings".
   4. In the left side of the Application you see "Main Menu", and you click in the drop menu  "Data Wallet", and you will see "Available Data Requests" and "Accepted Data Requests", "Data Collected" and "Transaction Summary".
   5. Click on "Available Data Requests" and you would find out all the "Data Requests" published by interested Service Providers. You can accept or decline, you as a Data Owner has the choices to share or not your data.
   6. Finally, if you click on "Accepted Data Requests" you will see, the full list of Accepted Requests I have grant my permission to access to data. If you are no longer interested in it, you can withdraw your consent to share data, and the Offer is terminated.

Producers should use the system with real shipments (enter data in platform, activate data logger) that can arrive at destination over the summer/beginning of autumn period.
Producers should put the IOF2020 project team in contact with the retailers willing to close the loop, by downloading the APP and providing their feedback.

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

In order to test the ecosystem please go to the feedback questionary, where the instructions are provided.

Introduction

The project presents four tools integrated with a user interface to interact with them:

1. Trust and Integration Controller (TIC): enable developers to use and configure a robust Hyperledger Fabric Blockchain Network, allowing users to use the logic, privacy and data consensus in their applications.
2. Co-located and Orchestrated Network Fabric (CONF): in its current version, is able to automatically deploy the Hyperledger Fabric Network previously mentioned along with the APIs to interact with it. 

To use the tools a user interface has been designed and provided for the testing. This interface allows the utilisation of the tools, and by means of a simple application is able to transfer token between two peers using the blockchain network behind. Moreover, through the navigator, it enables developers or end users to know how the chain is updated after every transaction and to configure the organization in the Hyperledger network.

Instructions

In order to test the provided scenario:

1. Navigate to following URL: http://tac.uist.edu.mk/beta/testing
   In the interface, sign up to create your own credentials:
2. Follow the provided instructions when signing up in the previous URL

In order to test the ecosystem please go to the feedback questionary, where the instructions are provided.

This initial prototype implements a blockchain based peer to peer trading platform and contains the following basic functionalities:
- Register as a new user.
- Login with registered credentials.
- View the personal energy profile statistics.
- Users can post advertisements to sell energy.
- Users can  buy energy from the Energy Marketplace.
- Users can view their history of all transactions
- Admins can access the Blockchain Explorer , to get an overview of all the energy transactions.   

This prototype implements smart contracts which saves all the transactions associated with smart meter readings, energy advertisements, marketplace transactions and user energy profile to the blockchain.

Before you answer the feedback questionnaire, please follow these testing Instructions.

As a reminder here is the Web App Link.

One you have performed the test, please fill in the FEEDBACK QUESTIONNAIRE on ReachOut

Add the FASTEN Maven plugin to your Java project using documentation available at https://github.com/fasten-project/fasten-maven-plugin/wiki.
If your project has a know vulnerability in one of his dependency the Maven plugin should be able to identify it.

You will find below a description of what you need to do to successfully run and experiment with Java call graph generator beta version.

Prerequisites

First make sure that you have Java 11 or higher installed.

Next you need to download the Java call graph generator.

Verify that you are good to by executing the Java call graph generator: java -jar javacg-opal-0.0.1-beta1-with-dependencies.jar
This should print the syntax help message.

You are now ready to perform a first test.

Testing Scenarios and instructions

The campaign includes 3 different test scenarios, presented from the simplest to the more advanced. We recommend that you follow instructions from top to bottom, but each scenario is independent so you can safely skip one.

-Test #1: execution with basic local application and dependency

-Test #2: execution with Maven public artifact 

-Test #3: execution with your own project

To get started, please go to the testing instructions and guidelines. 

Thanks for evaluating the FASTEN call graph generator and stay tuned for more FASTEN beta testing campaign (including Maven plugin)!

Answer to the questionnaire based on the experiments on the CROSSMINER platform  of the last 3 months