Saved in:
| Main Authors: | , , |
|---|---|
| Format: | Recurso digital |
| Language: | English |
| Published: |
Zenodo
2025
|
| Subjects: | |
| Online Access: | https://doi.org/10.5281/zenodo.17629570 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Table of Contents:
- <p><a href="https://netsoft.gsuite.tmit.bme.hu/projects/quest/" target="_blank" rel="noopener">QUEST</a> is an open-call project of the <a href="https://spirit-project.eu">SPIRIT</a> EU project.</p> <p>This repository contains all the software components necessary to replicate our results comparing a WebRTC-based point cloud <a href="https://github.com/idlab-discover/pc-webrtc-m2m">telepresence Unity</a> <a href="https://github.com/idlab-discover/pc-webrtc-m2m">application</a> with our modified version, which replaces WebRTC with Media over QUIC.</p> <p>Input datasaet available at <a href="https://doi.org/10.5281/zenodo.17632383">https://doi.org/10.5281/zenodo.17632383</a>.</p> <h2>Licence</h2> <p>All of our code is published under EUPL v1.2. However, existing projects retain their original licensing.</p> <h2>the build script </h2> <p>The ./build script helps to all the required software components, but it assumes a Unity build environment is already installed.</p> <h2>Reserving resources on the IMEC virtual wall testbed</h2> <p>The ./jfed/ script creates rspec files. The directory `./jfed/rspec` contains the rspec files we used.</p> <h3>Method 1</h3> <p>The jFed graphical user interface can be use to reserve resources defined by these rspec files. </p> <h3>Method 2</h3> <p>Alternative ./jfed/jfed can reserve resources as well. For example,</p> <pre><code>cd jfed ./jfed --action run --rspec-file ./rspec/fanout.rspec --sliver fanout </code></pre> <p>You can specify the Fed4FIRE project and the duration of the reservation as well:</p> <pre><code>$ ./jfed --help Usage: jfed [options] --action ACTION Command to execute or "help" --duration HOUR Duration of the resource allocation (default: 2) --help Display this help --project NAME Name of the project (default: spiritquest) --rspec FILE Rspec file (default: rspec/default.rspec) --slice NAME Name of the slice (default: exp1)</code></pre> <p>"Recent versions of the CLI have some problems", so you should create a <a href="https://doc.ilabt.imec.be/jfed-documentation/otherjfedtools.html#certificate-passwords">passwordless pem file</a> under `./jfed/nopass.pem`.</p> <h3>manifest.rspec</h3> <p>The command of method 2 saves the manifest file under`./jfed/output/manifest.rspec`. For method 1, the following command will fetch the manifest from the Fed4FIRE testbed portal:</p> <pre><code>cd jfed ./jfed --action get_rspec --sliver fanout</code></pre> <h2>Setting up the experiment</h2> <p>./jfed/deploy copies all the necessary files and installs the required dependencies to the testbed nodes. The deploy script relies on file `./jfed/output/manifest.rspec` created in the previous step.</p> <h2>Conducting the measurements</h2> <p>First, you must start <a href="https://www.gnu.org/software/screen/">screen</a>, then the following steps is going to run several measurements with different configuration settings.</p> <pre><code>cd ./experiments/fanout ../../tipsy/tipsy config make</code></pre> <p>The results will be available in <em>./experiments/fanout/measurements/result.json</em> and <em>./experiments/fanout/plots/fig.pdf</em>.</p>