CREW offers Open Access

CREW is in continuous Open Access phase to support your experiments free of charge!

Final public event & Globecom tutorial

CREW will present its final results at the Wireless Community event (Leuven, Belgium, 29 October 2015, more info) and organises a hands-on tutorial at Globecom (San Diego, USA, 10 December 2015, more info)

CREW PORTAL: access the CREW facilities

Interested in using the CREW facilities?
[Start here] - [Browse by name] - [Overview images] - [Advanced info] - [WTA GitHub].

Iris Testbed best practices


1.      Everything in the testbed has an exact place

        · Each USRP and node has been assigned a table and number.

        · Unused daughterboards will be placed in proper storage places.

2.      Everything goes back to the exact place after any experiment that causes it to be moved.

3.      Clonezilla is used on all nodes meaning that nodes will be reset to a specific version of IRIS on startup.

4.      Bearing this in mind everyone should take care to store data in the data partition and not elsewhere on a node as it will be lost otherwise.

5.      The firmware in the USRPs will be updated when a new release becomes stable. All hardware will be updated at once rather than a subsection of hardware.

6.      If it is found that any piece of equipment gets broken, or if there is an issue with its functionality (e.g. only works for a certain bandwidth or really low powered) the IRIS testbed users mailing list must be informed. This will be relayed this to the wider group and a note will be made of this on the appropriate wiki pages

7.      All experiments must be scheduled using the Google calendar <ctvr.testbed> specifying all of the following:

        · Name of experimenter

        · Date and time of booking

        · Testbed node number(s)

        · Daughtboard(s) of use

        · Frequency range(s) of use

8.      The testbed should not be used for simulations.

9.      The testbed room should be kept secure.

10.  Testbed users should sign up to the following mailing lists:

        · IRIS support mailing list

        · IRIS testbed users mailing list for enquiries regarding the Iris testbed.

        · IRIS commit mailing list for commit notifications.

11.  Short descriptions of all experimental work using the testbed should be provided in the projects section of the IRIS wiki