HAMMER Experiment Dataset 1 - Fed4FIRE+

Open data API in a single place

Provided by Zenodo

Get early access to HAMMER Experiment Dataset 1 - Fed4FIRE+ API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.07.17 00:00
Created
2022.01.01
Available languages
English
Keywords
beamforming, beyond 5G, deep learning, channel estimation, indoor radio measurements, 5GNR, hybrid beamforming, massive mimo
Quality scoring

Dataset description

In this dataset, we provide the measurement results (DataSet1) conducted in the course of the HAMMER experiment for Fed4FIRE+. The objective of the Experiments is provided in the uploaded reports, the HAMMER experiment presentation and the HAMMER poster. At the report and the documents, the interested researcher may find details about the conducted measurments and their objectives. The specific data set corresponds to the measurements conducted for the Training of the HAMMER deep learning scheme.  More specifically, in HAMMER: a reconfigurable MuPAR antenna array was implemented with 4 RF chains and 8 parasitic elements. the antenna is able to implement 81 different patterns. the project performed extensive measurments inside the w-iLab.t testbed facilities - testing the various patterns, in order to train a Deep Learning model for hybrid beamforming measuments. The measurements were extracted as follows: NR reference signals (DMRS) where transmitted by the HAMMER BS positioned at [9.5, 7.25] coordinates inside the w-iLab.t space. The HAMMER BS is implemented with two X310 USRPs The mobile node measures the signal (USRP B200) and estimates the radio channel. The procedure is repeated continuously sweeping periodically all beam patterns. The radio channel transfer function and the radio channel impulse response are saved. The dataset contains mat files (MATLAB). Meta-data with details for the measurement setup are included in the mat files. Position of the mobile user Position of the HAMMER BS Center Frequency (3.5GHz) Orientation of the mobile user Speed and Waiting time (at each point) for the mobile user. (the mobile user should be considered static when analyzing the measurements). The main dataset contains: The transfer function for 20MHz bandwidth for all 4 active antenna elements. The Channel Impulse Responsefor all 4 active antenna elements. The RSSI in dB (you can consider it as dBm - however, it is not calibrated for the Rx USRP, so it should not be used for propagation analysis vs. distance). The transfer function has dimensions: No Rx (1) No Tx (4) FFT size = 512 (it was downsampled from 2048 to reduce file size) Time index of measurements. It is noted that: Meaurements 1:81:end represent measurements with pattern index #1  (pattern #1 is all OMNI) Meaurements 2:81:end represent measurements with pattern index #2 ... Meaurements 41:81:end represent measurements with pattern index #41 (pattern #41 is all elements looking in-front) ... Meaurements 81:81:end represent measurements with pattern index #41 (pattern #41 is all elements looking back) The channel estimates are raw. In this specific dataset: the training measurements for the points of map1.mat are provided.  the map1 points can be seen in the screenshot of map1.png, in order to exactly understand the geometry of the environment. Additional files provided include: the pattern of the ESPAR antenna simulated at the azimuth. (Four ESPARs are used) pattern indexes (0 is omni, 1 is looking front, -1 looking back). Details can be found in the HAMMER report. For any question, contact kmaliat@unipi.gr Kostas Maliatsos  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks