We love to hear feedback. Please take a moment and fill out the form below and we will respond within 24 hours. Thank you so much!


| 017:040 Khan | : |
Has then your Lord (O pagans of Makkah) preferred for you sons, and taken for Himself from among the angels daughters. Verily! You utter an awful saying, indeed. |
| 017:040 Maulana | : |
Has then your Lord preferred to give you sons, and (for Himself) taken daughters from among the angels? Surely you utter a grievous saying. |
| 017:040 Pickthal | : |
Hath your Lord then distinguished you (O men of Makka) by giving you sons, and hath chosen for Himself females from among the angels? Lo! verily ye speak an awful word! |
| 017:040 Rashad | : |
Has your Lord given you boys, while giving Himself the angels as daughters?! How could you utter such a blasphemy? |
| 017:040 Sarwar | : |
(Pagans) has your Lord given you preference over Himself by granting you sons and taking the angels as His own daughters? What you say is a monstrous utterance. |
| 017:040 Shakir | : |
What! has then your Lord preferred to give you sons, and (for Himself) taken daughters from among the angels? Most surely you utter a grievous saying. |
| 017:040 Sherali | : |
What ! has your Lord favoured you with sons and taken for Himself females from among the angels? Surely, you say a grievous saying. |
| 017:040 Yusufali | : |
Has then your Lord (O Pagans!) preferred for you sons, and taken for Himself daughters among the angels? Truly ye utter a most dreadful saying! |
Concepts/Themes Covered: أركان الإسلام > التوحيد > توحيد الله تعالي > وحدانيته Pillars of Islam> Islamic> Oneness of Allah> Singularity and Being Unique أركان الإسلام > التوحيد > الشرك والمشركون > تنزيه الله جلّ جلاله عن الشريك Pillars of Islam> Islamic> Polytheism and the Polytheists> Allah's Freedom from Partnership الإيمان > الملائكة > الإيمان بهم Faith> The Angels> To Believe in them
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


I appear etched into the background.
Gradient text
background: inherit;
filter: blur(0.4rem)
text-shadow
background-clip: text


Jaguar E-Pace Facelift Spied for the First Time, Follows Evoque Lead
by Mihnea RaduJaguar is already working on a number of mid-life facelifts, such as for the XF sedan/wagon or the popular F-Pace. However, we were surprised to see the E-Pace, one of the newest and smallest products, also getting a makeover.
The E-Pace was launched in 2018. So if the facelift we see here will launch in 2020, which it should, it will come just two years into the life cycle of the car. It's not that we can't find anything wrong with it, just not enough for such a rush job.
The E-Pace is a compact premium crossover that competes against things like the Audi Q3, BMW X1 or the new Mercedes GLB. It's a hot segment that also happens to overlap with some cool non-premium models, such as the Mazda CX-5.
Obviously, those don't come with a premium badge, and Jaguar has done quite a few things right with the E-Pace. For example, due to the stiff chassis and suspension, taking corners can be a pleasant interior. And ignoring the sluggish infotainment, the rest of the cabin feels really special. We especially like the complex, F-Type-like shape of the dash and the finer leather trims.
But there are some flaws too, not all of which can be addressed during the facelift. For example, due to its platform, the E-Pace is a good 100-200kg heavier than its rivals, which can't be good for either performance or fuel economy.
After the facelift, the E-Pace will still use 2-liter turbo engines almost exclusively, so don't expect it to get any faster. However, the mild-hybrid and plug-in technology from its Range Rover sibling, the Evoque, should boost fuel-sipping capabilities. The be the most expensive E-Pace of them all, a 300 horsepower plug-in.
Cosmetic changes include the revised headlights and front bumper, as well as what looks like wrap-around taillights or at least slimmer ones. From the back, the E-Pace looks a bit like a Porsche Macan now, sportier than before.
Of course, these are quite early times for the E-Pace facelift. Jaguar likes to use the media as its marketing too, so expect new details to be let slip in the coming months. 🏁


deepmatcher.batch¶
AttrTensor¶
-
class
deepmatcher.batch.
AttrTensor
[source]¶ A wrapper around the batch tensor for a specific attribute.
The purpose of having a wrapper around the tensor is to include attribute specific metadata along with it. Metadata include the following:
lengths
: Lengths of each sequence (attribute value) in the batch.word_probs
: For each sequence in the batch, a list of word probabilities corresponding to words in the sequence.pc
: The first principal component of the sequence embeddings for all values of this attribute. For details on how this is computed refer documentation forcompute_metadata()
. This is used for implementing the SIF model proposed in this paper.
This class is essentially a
namedtuple
. The tensor containing the data and the associated metadata described above can be accessed as follows:name_attr = AttrTensor(data, lengths, word_probs, pc) assert(name_attr.data == data) assert(name_attr.lengths == lengths) assert(name_attr.word_probs == word_probs) assert(name_attr.pc == pc)
-
static
from_old_metadata
(data, old_attrtensor)[source]¶ Wrap a PyTorch
torch.Tensor
into anAttrTensor
.The metadata information is (shallow) copied from a pre-existing
AttrTensor
. This is useful when the data for an attribute is transformed by a neural network and we wish the wrap the result into anAttrTensor
for further processing by another module that requires access to metadata.Parameters: old_attrtensor ( AttrTensor
) – The pre-existingAttrTensor
to copy metadata from.
MatchingBatch¶
-
class
deepmatcher.batch.
MatchingBatch
(input, train_info)[source]¶ A batch of data and associated metadata for a text matching task.
Consists of one
AttrTensor
(containing the data and metadata) for each attribute. For example, theAttrTensor
s of aMatchingBatch
objectmbatch
for a matching task with two attribtuesname
andcategory
, can be accessed as follows:name_attr = mbatch.name category_attr = mbatch.category


Music
This page has background music configured. You should start to hear music after a moment.
Add music to liven up your content!
<x-view-do> routes support
background music.
Load Music
Just include a
<x-audio-music-load>
element in the content and it will play as soon as it is loaded.
Add Controls, or don't!
You can make any button control the audio, using the
<x-action-activator>
with the <x-audio-music-action>
components.


--- title: "Radio" date: 2021-04-29T16:00:58+02:00 draft: false main_title: "Tailwind radios" subheading: "" seo_title: "Tailwind radio forms - examples & templates" description: "Responsive radios built with Tailwind. Limits the user to one selection, from a list of preset options. The singular property of a radio button makes it distinct from a checkbox. " image: "" video: "" url: "/docs/standard/components/radio/" menu: forms: name: "Radio" --- {{< example lang="html" title="Basic example">}}


{% extends "yaba/layouts/base.html" %} {% block title %}Contact | {{ block.super }}{% endblock %} {% block main_content %}
Please contact me using the form below and I will make sure to reply to you as soon as I can.


%file newheader%>
<%file newnavbar%>| <%wgt%> Work Group | Maturity Level: N/A | Standards Status: Informative | <%complinks%> |
This is a representation of the json schema for <%title%>, which is just a part of the full JSON Schema.
<%json-schema%><%file newfooter%>


Version 2018-12-01
Thomas Schreiber
Dubravko Jagar
RTR-NetTest team
1. Introduction and terms of use
The present document specifies requests for Open Data collected by the RTR-NetTest and is available under https://www.netztest.at/en/Opendata. Open Data can be obtained at the user’s discretion in two possible formats:
-
Zipped CSV files for data collected within the last 31 days or within a specified month (Content-Type: application/zip; cf. Chapter CSV-Export) and
-
JSON data for any requests, even for combinations of several criteria (Content-Type: application/json;charset=UTF-8).
JSON data can be provided for two types of requests:
-
Search for tests by Open Data, i.e. data of all tests meeting some set of user-defined criteria (cf. Chapter Search for tests by open-data) and
-
Search data for one specific test (cf Chapter Open data for one specific test).
The Open Data interface is accessible via https://www.netztest.at/opendata
|
Important
|
Occurrences of INTERFACE in URLs in this document have to be replaced with the above link. |
The services are specified by means of their attributes. Sample requests and responses are also provided. Names within angle brackets <> are mandatory, within curly brackets {} are optional and have to be replaced with actual values. Attributes in a query after ? are always defined as <key>=<value> parameter pairs. Multiple attributes are delimited with ampersand &. The general format is hence:
GET INTERFACE<path>{?key-1=value-1}{&key-2=value-2}…{&key-n=value-n}
The parameter "sender" is optional for low-volume requests. For high-volume requests, please contact RTR<EMAIL_ADDRESS>for instructions regarding the parameter "sender". Users with a registered sender ID can be informed in case of major interface changes.
Data accessible via the Open Data Interface are made available under Creative Commons Attribution 4.0 (CC BY 4.0). Regarding privacy policy and terms of use, please refer to https://www.rtr.at/en/tk/netztestterms.
2. Search for tests by open-data
2.1. Request
| Method | URL |
|---|---|
GET |
INTERFACE/opentests/search{?parameters} |
2.2. Parameters
| Type | Name | Description |
|---|---|---|
Url |
filter-criteria |
Optional. The criteria, which search-results have to meet. Possible criteria are: download_kbit: LONG download_kbit[]: LONG upload_kbit: LONG upload_kbit[]: LONG ping_ms: DOUBLE ping_ms[]: DOUBLE time: DATE time[]: DATE zip_code: LONG zip_code[]: LONG cat_technology: STRING cat_technology[]: STRING client_version: STRING client_version[]: STRING model: STRING model[]: STRING network_name: STRING network_name[]: STRING network_type: STRING network_type[]: STRING platform: STRING platform[]: STRING signal_strength: LONG signal_strength[]: LONG open_uuid: UUID client_uuid: UUID long: DOUBLE long[]: DOUBLE lat: DOUBLE lat[]: DOUBLE mobile_provider_name: STRING mobile_provider_name[]: STRING provider_name: STRING provider_name[]: STRING sim_mcc_mnc: STRING sim_mcc_mnc[]: STRING sim_country: STRING sim_country[]: STRING asn: LONG asn[]: LONG network_country: STRING network_country[]: STRING country_geoip: STRING country_geoip[]: STRING country_location: STRING country_location[]: STRING loc_accuracy: LONG loc_accuracy[]: LONG public_ip_as_name: STRING format: ["json", "csv"] Date fields have to be submitted as a number, representing the number of milliseconds that have elapsed since midnight, January 1st, 1970 or in the format “yyyy-MM-dd HH:mm:ss”. The time is given in UTC. Decimal point (Full Stop “.”) is always used to separate the integer part from the fractional part of a number written in decimal form. This is independent from the local or regional settings. Numeric fields also allow using the comparators ‘>’ and ‘<’ (meaning ‘=>’ and ‘=<’ respectively). Dates have always to be queried as ranges by using these comparators. String fields allow using the wildcard ‘*’ for matching any literals and ‘?’ for matching one arbitrary literal. It is possible, to begin each filter argument with an exclamation mark (!) to negate the filter. E.g. network_type=!LAN will yield all tests where the network type was not LAN. The criteria denoted with [] can be used more than once in a query. Data has to match all criteria. If an array for one criterion is given, the data has to match each entry. Generally a query on a parameter value ‘null’ is not possible, except for the parameter loc_accuracy, where the value -1 means ‘null’. Non-‘null’ values are queried with any single or multiple values. |
Url |
sort_by, sort_order |
Optional. The field for which the data are sorted. Valid fields are: “download_kbit", "upload_kbit", "time", "signal_strength" and "ping_ms”. For this, the sort_by-Parameter specifies the field, the sort_order-Parameter specifies the direction (‘asc’ or ‘desc’). Per Default, the results are sorted by the time of the test in descending order (i.e. sort_by=time&sort_order=desc). |
Url |
max_results |
Optional. This is the page size, i.e. maximum number of result items that are returned per page. The default value is 100 items per page. The page size limit is 10000 items, i.e. not more than 10000 results can be displayed in a page. |
Url |
cursor |
Optional. It is used for pagination if the query returns more than the number of items according to parameter max_results. The value to be used for the display of the next page is given by the previous response in returned parameter next_cursor. |
Url |
format |
Optional. Using the String values "json" or "csv" it is possible to specify the desired output format of the query. Default: "json". If the sort parameters are specified, the value of the cursor is a multiple of the parameter max_results, otherwise it is an arbitrary number. |
Url |
_, timestamp |
Optional. Will be ignored and can be used to prevent caching of the response. |
Url |
sender |
Optional. ID of the sender, for authentication. |
2.3. Response
| Status | Response |
|---|---|
200 |
The resulting JSON or CSV, specified as following. |
400 |
A JSON Error Message containing all fields with invalid values. |
2.3.1. Returned JSON
| Value | Type | Example |
|---|---|---|
duration_ms |
Numeric |
124 |
next_cursor |
Numeric |
1455 |
results |
JSONArray |
[{opendata-summary-item}] |
| duration_ms |
The time it took the server to search for tests matching all criteria in milliseconds. |
| next_cursor |
Cursor for obtaining the next page, if the number of matched items exceeds the page size. ‘null’ if there are no more pages. Cf. search parameters max_results and cursor. |
| results |
The array containing the summaries of all matching tests. It is empty, if no tests matched the criteria. |
2.3.2. Opendata-summary-item
| Value | Type | Example |
|---|---|---|
platform |
String |
“Android 4G” |
model |
String |
"SM-N910F" |
time |
String |
"2013-07-16 09:57:17" |
provider_name |
String |
"Some Provider" |
download_kbit |
Numeric |
81180 |
upload_kbit |
Numeric |
77883 |
ping_ms |
Numeric |
4.254356 |
signal_strength |
Numeric |
-67 |
lte_rsrp |
Numeric |
-70 |
lat |
Numeric |
48.1977655 |
long |
Numeric |
16.349674 |
open_test_uuid |
String |
“Of7d6e88b-e883-467f-8435-ee6f6abc5080” |
open_uuid |
String |
"P9f2b7bb1-39ea-454e-aa97-538564d7f8f1" |
For detailed explanation, please refer to chapter Open data for one specific test.
2.4. Example
2.4.1. Request
GET INTERFACE/opentests/search?asn=1764&sender=a1b2c3d4e5f6
This request searches for all conducted tests where the autonomous system number matches 1764 and displays the recent ones of them according to the default page size (cf. max_results). The sender ID is optionally supplied as well.
GET INTERFACE/opentests/search?download_kbit=>10&download_kbit=<100&platform=An*&time=<2014-06-01 13:10:00&sort_by=upload_kbit&sort_order=asc&max_results=1000&cursor=2000
This request searches for all conducted tests where the download speed is between 10 and 100 kbps, were conducted before June 1st, 2014 13:10:00 UTC and the platform starts with “An”. All results are then sorted by the upload-speed in ascending order. The cursor is set to 2000 in order to display the 3rd page with 1000 items.
GET INTERFACE/opentests/search?lat⇒48.09&lat=<48.35&long⇒16.14&long=<16.62&loc_accuracy⇒0&loc_accuracy=<2000&max_results=10000
This query searches for all conducted tests within the rectangular area around Vienna with a position accuracy of up to 2 km. The recent 10000 tests are returned in one page.
2.4.2. Response
{ "next_cursor": 866505, "results": [ { "platform": " LAN", "model": "IE", "long": 16.393557, "open_test_uuid": "Od1e399e6-2a82-4801-a3e7-d125af88b55d", "time": "2014-10-03 14:19:22", "open_uuid": "P250081fe-a79e-4fbc-8b0b-76b901de2b4b", "download_kbit": 42281, "signal_strength": null, "ping_ms": 4.000914, "lte_rsrp": null, "upload_kbit": 1124, "lat": 48.233243, "provider_name": "next layer" }, ... { "platform": "Android WLAN", "model": "LGE Nexus 5", "long": 16.3497029, "open_test_uuid": "Oa1f286be-3c91-4f7d-b3d3-29d0e143e20d", "time": "2014-08-14 07:59:13", "open_uuid": "Pf9b785d8-d0c4-45c0-abd6-b1d492e72fe2", "download_kbit": 62864, "signal_strength": -57, "ping_ms": 2.769414, "lte_rsrp": null, "upload_kbit": 74528, "lat": 48.1977398, "provider_name": "next layer" } ], "duration_ms": 424 }
The reference interface implementation is available at https://www.netztest.at/en/Opentests via the “Advanced search” input option. The GET-parameters on this site are exactly the same as the parameters of the Open Data interface.
3. Open data for one specific test
This call gets all the open-data for one specific test by its open-test-uuid. The response is a JSON-Object with the values or ‘null’, if a value is unknown.
3.1. Request
| Method | URL |
|---|---|
GET |
INTERFACE/opentests/<open-test-uuid>{?parameters} |
3.2. Parameters
| Type | Name | Description |
|---|---|---|
Url |
open-test-uuid |
Mandatory. The open-test-uuid of the test. |
Url |
verbose |
Optional. If >0 the threadwise speed curve is additionally returned. |
Url |
sender |
Optional. ID of the sender, for authentification. |
3.3. Response
| Status | Response |
|---|---|
200 |
The resulting JSON, specified as following. |
404 |
If the UUID is invalid. |
3.3.1. Returned JSON
| Value | Type | Example |
|---|---|---|
asn |
Numeric |
6830 |
bytes_download |
Numeric |
13653343 |
bytes_upload |
Numeric |
3712431 |
cat_technology |
String |
“3G” |
cell_area_code |
Numeric |
10156 |
cell_location_id |
Numeric |
28708964 |
channel_number |
Numeric |
397 |
client_version |
String |
“1.1” |
community |
String |
“Wien” |
country_asn |
String |
“AT” |
country_geoip |
String |
“AT” |
country_location |
String |
“AT” |
connection |
String |
"nat_local_to_public_ipv4" |
distance |
Numeric |
667.15 |
district |
String |
“Mistelbach” |
download_classification |
Numeric |
3 |
download_kbit |
Numeric |
6903 |
duration_download_ms |
Numeric |
7000.13 |
duration_upload_ms |
Numeric |
7000.12 |
gkz |
Numeric |
90001 |
gkz_sa |
Numeric |
90601 |
implausible |
Boolean |
false |
ip_anonym |
String |
“80.108.108” |
kg_nr |
Numeric |
1009 |
land_cover |
Numeric |
null |
lat |
Numeric |
48.2029024 |
loc_src |
String |
“network” |
loc_accuracy |
Numeric |
5345 |
long |
Numeric |
16.3967841 |
locality |
String |
“Mariahilf” |
lte_rsrp |
Numeric |
-6 |
lte_rsrq |
Numeric |
-81 |
model |
String |
“Sony Xperia Tablet Z LTE” |
model_native |
String |
“SGP321“ |
ndt_download_kbit |
Numeric |
1443 |
ndt_upload_kbit |
Numeric |
2334 |
network_country |
String |
“DE” |
network_mcc_mnc |
String |
232-05 |
network_name |
String |
“3 AT” |
network_type |
String |
“WLAN” |
num_threads |
Numeric |
3 |
num_threads_requested |
Numeric |
3 |
num_theads_ul |
Numeric |
3 |
open_test_uuid |
String |
"O10b9e95c-d47a-4328-b2ff-82ef24c8e6fe" |
open_uuid |
String |
“Pa19046c3-cecf-437a-a3d0-062466c8a32c” |
ping_classification |
Numeric |
3 |
ping_ms |
Numeric |
16.178334 |
pinned |
Boolean |
true |
platform |
String |
“Android” |
product |
String |
“SGP321” |
provider_name |
String |
“Provider” |
province |
String |
“Wien” |
public_ip_as_name |
String |
“AS32768 Provider“ |
radio_band |
Numeric |
1 |
roaming_type |
Integer |
0 |
server_name |
String |
“RTR-DEVELOP-SERVER” |
signal_classification |
Numeric |
3 |
signal_strength |
Numeric |
-56 |
sim_country |
String |
“at” |
sim_mcc_mnc |
String |
“232-05” |
speed_curve |
Speed-Curve-Item |
{speed-curve-item} |
speed_curve_threadwise |
Speed-Curve-Threadwise |
{speed-curve-threadwise} |
test_if_bytes_download |
Numeric |
4991145 |
test_if_bytes_upload |
Numeric |
1961967 |
testdl_if_bytes_download |
Numeric |
4580781 |
testdl_if_bytes_upload |
Numeric |
107077 |
testul_if_bytes_download |
Numeric |
57372 |
testul_if_bytes_upload |
Numeric |
1627790 |
test_duration |
Numeric |
7 |
Time |
String |
"2013-07-15 01:55" |
time_dl_ms |
Numeric |
3692.15 |
time_ul_ms |
Numeric |
13496.54 |
upload_classification |
Numeric |
3 |
upload_kbit |
Numeric |
711 |
wifi_link_speed |
Numeric |
7562 |
zip_code |
Numeric |
1030 |
| asn |
Autonomous system number. |
| bytes_download |
Total number of bytes downloaded during download test (excluding training-phase). |
| bytes_upload |
Total number of bytes uploaded during upload test (excluding training-phase). |
| cat_technology |
Technology category of the network, e.g. “3G”, “4G”, “WLAN”. |
| cell_area_code |
Number describing the coarse location of a cell. E.g. the Tracking Area Code (TAC) in case of 4G or the Location Area Code (LAC) in case of 2G or 3G |
| cell_location_id |
Number identifying the location of a cell. E.g. the 28-bit Cell Identity (CI) in case of 4G, the 28-bit UMTS Cell Identity (CID) in case of UMTS or the 16-bit GSM Cell Identity (CID) in case of GSM. |
| channel_number |
Channel number of the radio channel used during a measurement. E.g. the 18-bit Absolute RF Channel Number (EARFCN) in case of 4G or the 16-bit UMTS Absolute RF Channel Number (UARFCN) in case of 3G. |
| client_version |
Software version number of the client. |
| community |
Name of Austrian community (Gemeinde). |
| connection/nat_type |
Type of connection in terms of NAT and IP-Version (e.g. behind NAT with local to public IP and IPv4). |
| country_asn |
Country of AS of client IP. |
| country_geoip |
Country according client IP address. |
| country_location |
Country of geo-location. |
| cov800cat |
Community category of Austrian 800 MHz coverage obligation derived from gkz (see https://www.rtr.at/en/tk/multibandauktionVersorgungsauflage800MHz). |
| distance |
The distance that the user moved in meters. |
| district |
Name of Austrian district (Bezirk). |
| download_classification |
Classification for the download speed in a
traffic-light system. |
| download_kbit |
The download-speed in kilobit per second. |
| duration_download_ms |
Duration of download test in ms. |
| duration_upload_ms |
Duration of upload test in ms. |
| gkz |
Community ID (Gemeindekennzahl, see http://www.bev.gv.at/portal/page?_pageid=713,2601287&_dad=portal&_schema=PORTAL). |
| gkz_sa |
Community ID (Gemeindekennzahl, see http://www.statistik.at/web_de/klassifikationen/regionale_gliederungen/gemeinden/index.html) |
| implausible |
Identification of implausible test results. |
| ip_anonym |
The anonymized IP-Address of the client. |
| kg_nr |
Number of the cadastral community, see http://www.bev.gv.at/portal/page?_pageid=713,2601287&_dad=portal&_schema=PORTAL |
| land_cover |
Classification of the land cover within austria, see http://www.umweltbundesamt.at/fileadmin/site/umweltthemen/raumplanung/1_flaechennutzung/corine/CORINE_Nomenklatur.pdf and https://www.eea.europa.eu/data-and-maps/data/clc-2006-vector-4 |
| lat |
Latitude of the client position. |
| loc_accuracy |
Estimation of accuracy of client location. |
| loc_src |
Source for the geo location-data. Valuse: “gps”, “network”. |
| locality |
Name of the cadastral community, see: http://www.bev.gv.at/portal/page?_pageid=713,2601287&_dad=portal&_schema=PORTAL |
| long |
Longitude of the client position. |
| lte_rsrp |
LTE signal strength in dBm. |
| lte_rsrq |
LTE signal quality in decibels. |
| model |
Name of the device used. |
| model_native |
Name of the device used, raw device name. |
| ndt_download_kbit |
Download speed in the NDT-test in kilobit per second. |
| ndt_upload_kbit |
Upload speed in the NDT-test in kilobit per second. |
| network_country |
Country of the network in ISO 3166. |
| network_mcc_mnc |
Network identification whereas the first three digits represent the country, the digits following the dash represent the mobile network provider within that country. |
| network_name |
Display name of the mobile network. |
| network_type |
Type of the network, e.g. MOBILE, LAN, WLAN. |
| num_threads |
Number of threads used for the downlink test. |
| num_threads_requested |
Number of threads requested by the server. |
| num_threads_ul |
Number of threads used for the uplink test. |
| open_test_uuid |
Open-Test-UUID: The UUID of the Test. |
| open_uuid |
Open-UUID: Identifies the client that conducted the test. The a new Open-UUID is assigned to the client on a regular basis. |
| ping_classification |
Classification for the ping speed in a traffic-light system. |
| ping_ms |
Median ping (round-trip time) in milliseconds, measured on the server side. In previous versions (before June 3rd 2015) this was the minimum ping measured on the client side. |
| pinned |
True, if if the test is relevant for generating the statistics (e.g. not part of a series) |
| platform |
Platform on which the test has been conducted. E.g.
|
| product Product |
Name of the client device. |
| provider_name |
Name of the internet service provider. |
| province |
Name of Austrian province (Bundesland). |
| public_ip_as_name |
Name of the AS of the clients public IP. |
| radio_band |
Radio band used when conducting the test. |
| roaming_type |
Integer representing the roaming status of the client:
|
| server_name |
Name of the test-server. |
| signal_classification |
Classification for the signal strength in a traffic-light system. |
| signal_strength |
Signal strength (RSSI) in dBm. |
| sim_country |
Home country of the SIM card in ISO 3166. |
| sim_mcc_mnc |
Network identification of the SIM provider. The digits of MCC and MNC have the same meaning as described in “network_mcc_mnc”. |
| speed_curve |
Aggregated history of transferred data bytes during a test. |
| speed_curve_threadwise |
History of transferred data bytes per thread during a test. Returned only if verbose>0. |
| test_duration |
Duration of the test per direction (up- or download) in seconds. |
| test_if_bytes_download |
Data volume received on the interface during the test (including training phase). |
| test_if_bytes_upload |
Data volume transmitted on the interface during the test (including training phase). |
| testdl_if_bytes_download |
Data volume received on the interface during the download test. |
| testdl_if_bytes_upload |
Data volume transmitted on the interface during the download test. |
| testul_if_bytes_download |
Data volume received on the interface during the upload test. |
| testul_if_bytes_upload |
Data volume transmitted on the interface during the upload test. |
| time/time_utc |
UTC date and time when test was started. |
| time_dl_ms |
Relative start time of download in ms. |
| time_ul_ms |
Relative start time of upload in ms. |
| upload_classification |
Classification for the upload speed in a traffic-light system. |
| upload_kbit |
Upload speed in kilobit per second. |
| wifi_link_speed |
WLAN link speed according to the Android API. |
| zip_code |
obsolete, will be removed in future versions |
Note: Only the italic marked items are included in the open data zipped csv file.
3.3.2. Speed-curve-item
| Value | Type | Example |
|---|---|---|
download |
JSONArray |
[{measurement-item}] |
upload |
JSONArray |
[{measurement-item}] |
ping |
JSONArray |
[{ping-item}] |
signal |
JSONArray |
[{signal-item}] |
location |
JSONArray |
[{location-item}] |
| download |
Measurements of downloaded bytes at various times during the test. |
| upload |
Measurements of uploaded bytes at various times during the test. |
| signal |
Measurements of signal strength and network type at various times during the test. |
| location |
The client’s locations throughout the test. |
| ping |
The client’s pings throughout the test |
3.3.3. Measurement-item
| Value | Type | Example |
|---|---|---|
time_elapsed |
Numeric |
55 |
bytes_total |
Numeric |
4096 |
| time_elapsed |
The time elapsed since the start of the test phase in milliseconds. |
| bytes_total |
The sum of all bytes transferred since the start of the test phase. |
3.3.4. Ping-item
| Value | Type | Example |
|---|---|---|
time_elapsed |
Numeric |
55 |
ping_ms |
Numeric |
8 |
| time_elapsed |
The time elapsed since the start of the test in milliseconds. |
| ping_ms |
Ping (round-trip time) in milliseconds, measured on the server side. |
3.3.5. Signal-item
| Value | Type | Example |
|---|---|---|
time_elapsed |
Numeric |
55 |
network_type |
String |
“LTE” |
cat_technology |
String |
“4G” |
signal_strength |
Numeric |
-85 |
lte_rsrq |
Numeric |
-6 |
lte_rsrp |
Numeric |
-77 |
cell_info_2G |
Numeric |
[{Cell Info 2G-Item}] |
cell_info_3G |
Numeric |
[{Cell Info 3G-Item}] |
cell_info_4G |
Numeric |
[{Cell Info 4G-Item}] |
| time_elapsed |
The time elapsed since the start of the test in milliseconds. |
| network_type |
Type of the network, e.g. GSM, EDGE, UMTS, HSPA, LTE, LAN, WLAN… |
| cat_technology |
Technology category of the network, e.g. “3G”, “4G”, “WLAN”. |
| signal_strength |
Signal strength (RSSI) in dBm. |
| lte_rsrq |
LTE signal quality in decibels. |
| lte_rsrp |
LTE signal strength in dBm. |
| cell_info_2G |
Additional information about the used 2G radio cell |
| cell_info_3G |
Additional information about the used 3G radio cell |
| cell_info_4G |
Additional information about the used 4G radio cell |
3.3.6. Cell Info 2G-Item
| Value | Type | Example |
|---|---|---|
arfcn |
Numeric |
1021 |
band |
Numeric |
8 |
bsic |
Numeric |
58 |
cid |
Numeric |
18804 |
frequency_dl |
Numeric |
934.4 |
lac |
Numeric |
47170 |
| arfcn |
16-bit GSM Absolute RF Channel Number |
| band |
Band |
| bsic |
6-bit Base Station Identity Code |
| cid |
16-bit GSM Cell Identity described in TS 27.007, 0..65535 |
| frequency_dl |
Frequency of the downlink in MHz |
| lac |
16-bit Location Area Code, 0..65535 |
3.3.7. Cell Info 3G-Item
| Value | Type | Example |
|---|---|---|
band |
Numeric |
1 |
cid |
Numeric |
9908484 |
frequency_dl |
Numeric |
2137.4 |
lac |
Numeric |
2510 |
psc |
Numeric |
27 |
uarfcn |
Numeric |
10687 |
| band |
Band |
| cid |
CID 28-bit UMTS Cell Identity described in TS 25.331, 0..268435455 |
| frequency_dl |
Frequency of the downlink in MHz |
| lac |
16-bit Location Area Code, 0..65535 |
| psc |
9-bit UMTS Primary Scrambling Code described in TS 25.331, 0..511 |
| uarfcn |
16-bit UMTS Absolute RF Channel Number |
3.3.8. Cell Info 4G-Item
| Value | Type | Example |
|---|---|---|
band |
Numeric |
7 |
ci |
Numeric |
189954 |
earfcn |
Numeric |
2850 |
frequency_dl |
Numeric |
2630 |
pci |
Numeric |
35 |
tac |
Numeric |
6710 |
| band |
Band |
| ci |
28-bit Cell Identity |
| earfcn |
18-bit Absolute RF Channel Number |
| frequency_dl |
Frequency of the downlink in MHz |
| pci |
Physical Cell Id 0..503 |
| tac |
16-bit Tracking Area Code |
3.3.9. Location-item
| Value | Type | Example |
|---|---|---|
time_elapsed |
Numeric |
55 |
loc_accuracy |
Numeric |
8 |
long |
Numeric |
14.20882799 |
lat |
Numeric |
47.76077786 |
altitude |
Numeric |
300.4 |
speed |
Numeric |
22.4 |
bearing |
Numeric |
195.4 |
| time_elapsed |
The time elapsed since the start of the test in milliseconds. |
| loc_accuracy |
Estimation of accuracy of client location. |
| long |
Longitude of the client position. |
| lat |
Latitude of the client position. |
| altitude |
Altitude of the client position in meters |
| speed |
Speed of the client device in meters per second |
| bearing |
Direction of travel of the hosting device in degrees, where 0° ≤ bearing < 360°, counting clockwise relative to the true north |
3.3.10. Speed-curve-threadwise
| Value | Type | Example |
|---|---|---|
download |
JSONArray |
"2": [{measurement-threadwise}] |
upload |
JSONArray |
"0": [{measurement-threadwise}] |
signal |
JSONArray |
[{signal-item}] |
location |
JSONArray |
[{location-item}] |
| download |
Measurements of downloaded bytes per thread at various times during the test. The download threads are named "0", "1", "2" etc. |
| upload |
Measurements of uploaded bytes per thread at various times during the test. The upload threads are named "0", "1", "2" etc. |
Note: If there is no data transmitted in a thread, this thread is not reported at all. The threads may also differ in duration and number of speed curve measurement items. The time gaps between single items are variable as well.
3.3.11. Measurement-threadwise
| Value | Type | Example |
|---|---|---|
time_elapsed_ns |
Numeric |
41183662 |
bytes_total |
Numeric |
319488 |
| time_elapsed_ns |
The time elapsed since the start of the test phase for this thread, in nanoseconds. |
| bytes_total |
The sum of all bytes transferred since the start of the test phase for this thread. |
3.4. Example
3.4.1. Request
GET INTERFACE/opentests/O211ec703-71db-4c32-b61a-77fc1bbf1705?sender=m7n8o9p10q11
3.4.2. Response
{ "asn": 1764, "bytes_download": 76959744, "bytes_upload": 78868480, "cat_technology": "LAN", "cell_area_code": null, "cell_location_id": null, "channel_number": null, "client_version": "0.3", "community": "Wien", "connection": null, "country_asn": "EU", "country_geoip": "AT", "country_location": "AT", "distance": null, "district": "Wien(Stadt)", "download_classification": 3, "download_kbit": 87445, "duration_download_ms": 7040.742745, "duration_upload_ms": 7126.321333, "gkz": 90001, "gkz_sa": 90601, "implausible": false, "ip_anonym": "2a01:190:15fd::", "kg_nr": 1009, "land_cover": null, "lat": 48.198019801980195, "loc_accuracy": 100, "loc_src": "rastered", "locality": "Mariahilf", "long": 16.34952766531714, "lte_rsrp": null, "lte_rsrq": null, "model": "Firefox", "model_native": "Firefox", "ndt_download_kbit": null, "ndt_upload_kbit": null, "network_country": null, "network_mcc_mnc": null, "network_name": null, "network_type": "LAN", "num_threads": 3, "num_threads_requested": 3, "num_threads_ul": 3, "open_test_uuid": "O211ec703-71db-4c32-b61a-77fc1bbf1705", "open_uuid": "P7241cee2-7773-47cb-b398-dd047260db32", "ping_classification": 3, "ping_ms": 2.165636, "pinned": true, "platform": "RMBTws", "product": "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0", "provider_name": "next layer Telekommunikationsdienstleistungs-GmbH", "province": "Wien", "public_ip_as_name": "NEXTLAYER-AS next layer Telekommunikationsdienstleistungs- GmbH,AT", "radio_band": null, "roaming_type": null, "server_name": "RTR https 1G AT", "signal_classification": null, "signal_strength": null, "sim_country": null, "sim_mcc_mnc": null, "speed_curve": { "download": [ { "bytes_total": 319488, "time_elapsed": 41 }, ..., { "bytes_total": 76959744, "time_elapsed": 7280 } ], "location": [ { "lat": 48.20817400000001, "loc_accuracy": 140000, "long": 16.373819, "time_elapsed": 574 }, ..., { "lat": 48.197906299999985, "loc_accuracy": 100, "long": 16.3495225, "time_elapsed": 44488 } ], "signal": [], "upload": [ { "bytes_total": 4096, "time_elapsed": 107 }, ..., { "bytes_total": 78868480, "time_elapsed": 7148 } ] }, "test_duration": 7, "test_if_bytes_download": null, "test_if_bytes_upload": null, "testdl_if_bytes_download": null, "testdl_if_bytes_upload": null, "testul_if_bytes_download": null, "testul_if_bytes_upload": null, "time": "2014-10-01 14:46:06", "time_dl_ms": null, "time_ul_ms": null, "upload_classification": 3, "upload_kbit": 88537, "wifi_link_speed": null, "zip_code": null } }
3.4.3. Request Threadwise
GET INTERFACE/opentests/O211ec703-71db-4c32-b61a-77fc1bbf1705?verbose=1
3.4.4. Response Threadwise
{ "open_test_uuid": "O211ec703-71db-4c32-b61a-77fc1bbf1705", "open_uuid": "P7241cee2-7773-47cb-b398-dd047260db32", "speed_curve": {...} , //same as speed-curve-item "long": 16.34952766531714, "lat": 48.198019801980195, "time": "2014-10-01 14:46:06", ..., //same as above "speed_curve_threadwise": { "download": { "0": [ { "time_elapsed_ns": 41183662, "bytes_total": 319488 }, ... { "time_elapsed_ns":<PHONE_NUMBER>, "bytes_total": 17825792 } ], "1": [ { "time_elapsed_ns": 41273266, "bytes_total": 40960 }, ... { "time_elapsed_ns":<PHONE_NUMBER>, "bytes_total": 42909696 } ], "2": [ { "time_elapsed_ns": 41228267, "bytes_total": 49152 }, ... { "time_elapsed_ns":<PHONE_NUMBER>, "bytes_total": 16224256 } ] }, "upload": {...} //similar to download } }
4. CSV-Export
4.1. Request
| Method | URL |
|---|---|
GET |
INTERFACE/export |
GET |
INTERFACE/export/netztest-opendata-<year>-<month>.zip |
4.2. Parameters
No parameters need to be sent in order to obtain the test results of the last 31 days. For the second type of request, it is necessary to replace <year> with a four-digit year number ≥ 2000 and < 3000 and <month> with a two-digit month number ≥ 01 and ≤ 12).
4.3. Response
| Status | Response |
|---|---|
200 |
Returns a zip file containing a csv file. This file contains the test results of the given period from the open data database. Please refer to chapter Returned JSON for the differences in included items compared to the JSON data. |
4.4. Example
4.4.1. Request
GET INTERFACE/export
4.4.2. Response
open_uuid,open_test_uuid,time_utc,cat_technology,network_type,lat,long,loc_src,loc_accuracy,gkz,zip_code,country_location,download_kbit,upload_kbit,ping_ms,lte_rsrp,lte_rsrq,server_name,test_duration,num_threads,platform,model,client_version,network_mcc_mnc,network_name,sim_mcc_mnc,nat_type,asn,ip_anonym,ndt_download_kbit,ndt_upload_kbit,implausible,signal_strength,pinned,kg_nr,gkz_sa,land_cover,cell_area_code,cell_location_id P83d85a1e-e940-492d-8345-13a1a4c53d7d,Ofcfd6811-b6bc-4c82-8ddc-0d8f56f0f462,2018-03-03 00:00:02,WLAN,WLAN,47.9860743,14.0410021,network,20.0,40912,,AT,3749,529,40.2,,,RTR https 10G AT,7,3,Android,Galaxy J7,3.3.4,,,,nat_local_to_public_ipv4,8447,62.47.60,,,false,-60,true,49104,40912,211,, Pa10bd911-2e48-4c15-aa27-e31231c3f432,O7e336c7d-e867-4cc8-9e7b-5fd4ad519abd,2018-03-03 00:01:16,LAN,LAN,,,,,,,,12268,9176,35.5,,,RTR https 10G AT,7,3,,Chrome,0.8.0,,,,,8412,78.132.3,,,false,,true,,,,, P83d85a1e-e940-492d-8345-13a1a4c53d7d,O8c74e62a-84c3-4c9e-a493-5d9d65cb689f,2018-03-03 00:01:32,WLAN,WLAN,47.9860743,14.0410021,network,22.5,40912,,AT,6552,517,14.5,,,RTR https 10G AT,7,3,Android,Galaxy J7,3.3.4,,,,nat_local_to_public_ipv4,8447,62.47.60,,,false,-68,false,49104,40912,211,, ...
5. ShareImage-Generation
This call generates images containing the results of a user’s speed test.
5.1. Request
| Method | URL |
|---|---|
GET |
INTERFACE/<language>/<open-test-uuid>/<imagetype>.png |
5.2. Parameters
| Type | Name | Description | Example |
|---|---|---|---|
Url |
language |
The language of all text contained in the image. Can currently either be “de” or “en”. |
“de” |
Url |
open-test-uuid |
The Open-Test-UUID for the specific speed-test event. Can be obtained by calling /opentests. |
O10b9e95c-d47a-4328-b2ff-82ef24c8e6fe |
Url |
imagetype |
The type of image that should be generated. Can currently either be “forumlarge”, “forumsmall” or “thumbnail”. |
“forumlarge” |
5.3. Response
| Status | Response |
|---|---|
200 |
The generated image of mimetype image/png. |
400 |
“invalid language” |
400 |
"invalid image type" |
404 |
“Invalid open-uuid” |
5.4. Example
5.4.1. Request
GET INTERFACE/en/O211ec703-71db-4c32-b61a-77fc1bbf1705/forumsmall.png
5.4.2. Response
6. Quality of Service
6.1. Request
| Method | URL |
|---|---|
GET |
INTERFACE/qos/<open-test-uuid> |
6.2. Parameters
| Type | Name | Description |
|---|---|---|
Url |
open-test-uuid |
Mandatory. The open-test-uuid of the test. |
6.3. Response
| Status | Response |
|---|---|
200 |
The resulting JSON, specified as following. |
200 |
Test result could not be loaded. |
6.3.1. Returned JSON
| Value | Type | Example |
|---|---|---|
error |
JSONArray |
[{error-item}] |
testresultdetail_testdesc |
JSONArray |
[{testresultdetail-testdesc-item}] |
testresultdetail |
JSONArray |
[{testresultdetail-item}] |
testresultdetail_desc |
JSONArray |
[{testresultdetail-desc-item}] |
| error |
Error message(s). |
| testresultdetail_testdesc |
Subtest descriptions containing description, name, and type of each subtest. |
| testresultdetail |
Detailed results of each subtest. |
| testresultdetail_desc |
Summaries of groups of subtest results. |
6.3.2. Error-item
An array of strings, e.g. ["Test result could not be loaded."] if the open-test-uuid does not exist, and [] if no error has occurred.
6.3.3. Testresultdetail-testdesc-item
| Value | Type | Example |
|---|---|---|
desc |
String |
"Bei diesem Test wird überprüft, ob die HTTP-Anfrage durch einen Proxy oder eine andere \"Middlebox\" verändert wird." |
name |
String |
"Transparente Verbindung" |
test_type |
String |
"NON_TRANSPARENT_PROXY" |
| desc |
Description of the subtest. |
| name |
Name of the subtest. |
| test_type |
Type of the subtest, i.e., WEBSITE, HTTP_PROXY, NON_TRANSPARENT_PROXY, DNS, TCP, or UDP. |
6.3.4. Testresultdetail-item
| Value | Type | Example |
|---|---|---|
failure_count |
Numeric |
0 |
uid |
Numeric |
432645 |
result |
JSONObject |
{result-item} |
test_summary |
String |
"TCP Outgoing, Port: 585" |
success_count |
Numeric |
1 |
test_desc |
String |
"TCP Outgoing:\nEs wurde versucht, eine ausgehende Verbindung zum QoS-Testserver über den Port: 585 aufzubauen." |
test_type |
String |
"tcp" |
| failure_count |
Number of failures of this subtest. |
| uid |
Primary key of the subtest. |
| result |
Subtest results and objectives. |
| test_summary |
Short description of subtest, e.g. protocol, incoming/outgoing, and port. |
| success_count |
Number of successful test evaluations. |
| test_desc |
Description of subtest type category. |
| test_type |
Type of the test, i.e., website, http_proxy, non_transparent_proxy, dns, tcp, or udp. |
6.3.5. Result-item
Values with name prefix dns_, http_, nontransproxy_, tcp_, udp_, and website_ are specific to the respective subtest types.
| Value | Type | Example |
|---|---|---|
dns_objective_dns_record |
String |
"A" |
dns_objective_host |
String |
"ebay.de", |
dns_objective_resolver |
String |
"Standard" |
dns_objective_timeout |
String |
"2000000000" |
dns_result_duration |
String |
"47716302" |
dns_result_entries |
String |
"[\{\"dns_result_address\":\"<IP_ADDRESS>\",\"dns_result_ttl\":\"1884\"},\{\"dns_result_address\":\"<IP_ADDRESS>\",\"dns_result_ttl\":\"1884\"},\{\"dns_result_address\":\"<IP_ADDRESS>\",\"dns_result_ttl\":\"1884\"}]" |
dns_result_entries_found |
String |
"3" |
dns_result_info |
String |
"OK" |
dns_result_status |
String |
"NOERROR" |
duration_ns |
String |
"614812708" |
http_objective_range |
String |
"bytes=1000000-1004999" |
http_objective_url |
String |
|
http_result_hash |
String |
"fc563e1e80b8cb964d712982fa2143c8" |
http_result_header |
String |
"Server: nginx\nDate: Fri, 03 Oct 2014 16:43:36 GMT\nContent-Type: image/jpeg\nContent-Length: 5000\nLast-Modified: Sat, 27 Sep 2014 14:07:37 GMT\nConnection: keep-alive\nContent-Range: bytes 1000000-1004999/9982005\n" |
http_result_length |
String |
"5000" |
http_result_status |
String |
"206" |
nontransproxy_objective_port |
String |
"51182" |
nontransproxy_objective_request |
String |
"GET / HTTR/7.9" |
nontransproxy_objective_timeout |
String |
"3000000000" |
nontransproxy_result |
String |
"OK" |
nontransproxy_result_response |
String |
"GET / HTTR/7.9" |
start_time_ns |
String |
"24429032022" |
tcp_objective_out_port |
String |
"585" |
tcp_objective_timeout |
String |
"2000000000" |
tcp_result_out |
String |
"OK" |
tcp_result_out_response |
String |
"PING" |
test_type |
String |
"tcp" |
udp_objective_delay |
String |
"300000000" |
udp_objective_out_num_packets |
String |
"1" |
udp_objective_out_port |
String |
"27015" |
udp_objective_timeout |
String |
"2000000000" |
udp_result_out_num_packets |
String |
"1" |
udp_result_out_packet_loss_rate |
String |
"0" |
udp_result_out_response_num_packets |
String |
"1" |
website_objective_timeout |
String |
"10000000000" |
website_objective_url |
String |
|
website_result_duration |
String |
"795957031" |
website_result_info |
String |
"OK" |
website_result_rx_bytes |
String |
"144439" |
website_result_status |
String |
"200" |
website_result_tx_bytes |
String |
"14900" |
| dns_objective_dns_record |
DNS record to request. |
| dns_objective_host |
Target host of this subtest. |
| dns_objective_resolver |
DNS resolver to be used for this subtest. |
| dns_objective_timeout |
DNS query timeout in ns. |
| dns_result_duration |
Time needed to complete the test. |
| dns_result_entries |
Result of this test containing all dns entries that were found. |
| dns_result_entries_found |
Number of entries found. |
| dns_result_info |
Result status of this subtest (OK, TIMEOUT, or ERROR). |
| dns_result_status |
Query status, e.g. NOERROR or NXDOMAIN. |
| duration_ns |
Duration of the subtest in ns. |
| http_objective_range |
String passed to the range request header. |
| http_objective_url |
Target URL of this subtest. |
| http_result_hash |
Checksum of downloaded content or TIMEOUT or ERROR. |
| http_result_header |
Header of HTTP response. |
| http_result_length |
Length of downloaded content. |
| http_result_status |
Status code in header of HTTP response (or -1 if no response). |
| nontransproxy_objective_port |
Test port for non-transparent proxy subtest. |
| nontransproxy_objective_request |
Request string for this subtest. |
| nontransproxy_objective_timeout |
Timeout for this subtest in ns. |
| nontransproxy_result |
Result status of this subtest (OK, TIMEOUT, or ERROR). |
| nontransproxy_result_response |
Response (echo of the test server). |
| start_time_ns |
Starting time of test in ns relative to beginning of RTR- NetTest. |
| tcp_objective_out_port |
Port number used for outgoing TCP subtest. |
| tcp_objective_timeout |
Timeout of this subtest in ns. |
| tcp_result_out |
Result status of this subtest (OK or FAILED). |
| tcp_result_out_response |
Response received by client after sending message to test server. |
| test_type |
Type of subtest. |
| udp_objective_delay |
Delay between packets in ns. |
| udp_objective_out_num_packets |
Number of packets sent by client. |
| udp_objective_out_port |
Port number used for outgoing subtest. |
| udp_objective_timeout |
Timeout for this subtest in ns. |
| udp_result_out_num_packets |
Number of packets received by test server. |
| udp_result_out_packet_loss_rate |
Outgoing packet loss rate. |
| udp_result_out_response_num_packets |
Responses to outgoing packets (used to determine packet loss rate). |
| website_objective_timeout |
Timeout for website subtest. |
| website_objective_url |
Target URL of this subtest. |
| website_result_duration |
Time needed to download and render website in ns. |
| website_result_info |
Result status of this subtest (OK, TIMEOUT, or ERROR). |
| website_result_rx_bytes |
Bytes received during subtest. |
| website_result_status |
Status code in header of HTTP response (or -1 if no response). |
| website_result_tx_bytes |
Bytes transmitted during subtest. |
6.3.6. Testresultdetail-desc-item
| Value | Type | Example |
|---|---|---|
uid |
JSONArray |
[432659, 432660] |
desc |
String |
"Der übertragene Inhalt entspricht exakt dem Original, er wurde nicht modifiziert." |
test |
String |
"HTTP_PROXY" |
status |
String |
"ok" |
| uid |
Array of (numeric) primary keys of the subtest. |
| desc |
Description of the subtest result. |
| test |
Type of the subtest, i.e., WEBSITE, HTTP_PROXY, NON_TRANSPARENT_PROXY, DNS, TCP, or UDP. |
| status |
Status of the subtest result. |
6.4. Example
6.4.1. Request
GET INTERFACE/qos/O56b5cc79-5669-4457-bce2-0aeaf3b7242f
6.4.2. Response
{ "error": [ ], "testresultdetail_testdesc": [ { "desc": "Beim Webseiten-Test wird eine Referenz-Webseite (mobile Kepler-Seite der ETSI) heruntergeladen.  Er wird zur Übersetzung von Domain-Namen auf IP-Adressen verwendet. Es wird - je nach Test - getestet, ob der Dienst verfügbar ist, ob die Antworten korrekt sind und wie schnell der Server antwortet.", "name": "DNS", "test_type": "DNS" }, { "desc": "TCP ist ein wichtiges verbindungsloses Internetprotokoll. Es wird z.B. für die Übertragung von Webseiten und Mails verwendet.", "name": "TCP Ports", "test_type": "TCP" }, { "desc": "UDP ist ein wichtiges verbindungsorientiertes Internet-Protokoll, das für Echtzeitübertragungen (zB. VoIP, Video) verwendet wird.", "name": "UDP Ports", "test_type": "UDP" } ], "testresultdetail": [ { "failure_count": 0, "uid": 432645, "result": { "tcp_objective_timeout": "2000000000", "start_time_ns": "24429032022", "tcp_result_out_response": "PING", "tcp_result_out": "OK", "tcp_objective_out_port": "585", "duration_ns": "614812708" }, "test_summary": "TCP Outgoing, Port: 585", "success_count": 1, "test_desc": "TCP Outgoing:\nEs wurde versucht, eine ausgehende Verbindung zum QoS-Testserver über den Port: 585 aufzubauen.", "test_type": "tcp" }, { "failure_count": 0, "uid": 432646, "result": { "start_time_ns": "24435081033", "udp_objective_out_port": "27015", "udp_result_out_response_num_packets": "1", "udp_result_out_packet_loss_rate": "0", "udp_objective_out_num_packets": "1", "udp_result_out_num_packets": "1", "udp_objective_timeout": "2000000000", "udp_objective_delay": "300000000", "duration_ns": "783956145" }, "test_summary": "UDP Outgoing, Port: 27015, Anzahl Pakete: 1", "success_count": 1, "test_desc": "UDP Outgoing:\nAnzahl verschickter Pakete: 1, am Server angekommen: 1, am Client zurückgekommen: 1.\nPaketverlustrate: 0%", "test_type": "udp" }, ..., { "failure_count": 0, "uid": 432657, "result": { "start_time_ns": "25296847907", "nontransproxy_result": "OK", "nontransproxy_result_response": "GET / HTTR/7.9", "nontransproxy_objective_timeout": "3000000000", "nontransproxy_objective_port": "51182", "nontransproxy_objective_request": "GET / HTTR/7.9", "duration_ns": "452739583" }, "test_summary": "Port: 51182\nAnfrage: GET / HTTR/7.9", "success_count": 1, "test_desc": "Eine HTTP Anfrage mit dem Inhalt: 'GET / HTTR/7.9' wurde an den Testserver (Port: 51182) geschickt.\nDie Antwort war: 'GET / HTTR/7.9'", "test_type": "non_transparent_proxy" }, { "failure_count": 0, "uid": 432659, "result": { "http_objective_range": "bytes=1000000-1004999", "start_time_ns": "25759770876", "http_result_status": "206", "http_result_length": "5000", "http_result_header": "Server: nginx\nDate: Fri, 03 Oct 2014 16:43:36 GMT\nContent-Type: image/jpeg\nContent-Length: 5000\nLast-Modified: Sat, 27 Sep 2014 14:07:37 GMT\nConnection: keep-alive\nContent-Range: bytes 1000000-1004999/9982005\n", "http_objective_url": "http://webtest.netztest.at/qostest/reference01.jpg", "http_result_hash": "fc563e1e80b8cb964d712982fa2143c8", "duration_ns": "225194896" }, "test_summary": "Ziel: http://webtest.netztest.at/qostest/reference01.jpg", "success_count": 1, "test_desc": "Ziel: 'http://webtest.netztest.at/qostest/reference01.jpg'\nIntervall: bytes=1000000-1004999\nDauer: 0,2 s\nLänge: 5000\r\nStatus Code: 206\nHash: fc563e1e80b8cb964d712982fa2143c8\nHeader: \r\nServer: nginx\nDate: Fri, 03 Oct 2014 16:43:36 GMT\nContent-Type: image/jpeg\nContent-Length: 5000\nLast-Modified: Sat, 27 Sep 2014 14:07:37 GMT\nConnection: keep-alive\nContent-Range: bytes 1000000-1004999/9982005\n", "test_type": "http_proxy" }, ..., { "failure_count": 0, "uid": 432661, "result": { "start_time_ns": "26652727959", "website_result_tx_bytes": "14900", "website_objective_url": "http://webtest.netztest.at/kepler", "website_result_rx_bytes": "144439", "website_result_info": "OK", "website_result_duration": "795957031", "website_objective_timeout": "10000000000", "website_result_status": "200", "duration_ns": "813012239" }, "test_summary": "Ziel: http://webtest.netztest.at/kepler", "success_count": 1, "test_desc": "Die Übertragung von http://webtest.netztest.at/kepler dauerte 0,8 s.\r\n\nDatenvolumen Downlink: 144,4 kB\nDatenvolumen Uplink: 14,9 kB\nHTTP Status code: 200", "test_type": "website" }, { "failure_count": 0, "uid": 432662, "result": { "start_time_ns": "27471066031", "dns_objective_timeout": "2000000000", "dns_result_info": "OK", "dns_result_entries_found": "3", "dns_objective_resolver": "Standard", "dns_result_duration": "34847865", "dns_result_entries": "[{\"dns_result_address\":\"<IP_ADDRESS>\",\"dns_result_ttl\":\"3540\"},{\"dns_result_address\":\"<IP_ADDRESS>\",\"dns_result_ttl\":\"3540\"},{\"dns_result_address\":\"<IP_ADDRESS>\",\"dns_result_ttl\":\"3540\"}]", "dns_result_status": "NOERROR", "dns_objective_dns_record": "A", "dns_objective_host": "apple.com", "duration_ns": "34921927" }, "test_summary": "Ziel: apple.com \nEintrag: A\nDNS-Auflöser: Standard", "success_count": 1, "test_desc": "DNS Anfrage für die Domain: apple.com\nAbgefragter Typ: A-Record.\n\nTestergebnis: \nDNS Status: NOERROR\nDNS-Einträge: [[address=<IP_ADDRESS>, ttl=3540], [address=<IP_ADDRESS>, ttl=3540], [address=<IP_ADDRESS>, ttl=3540]]\r\nDauer: 35 ms", "test_type": "dns" }, ... ], "testresultdetail_desc": [ { "uid": [ 432659, 432660 ], "desc": "Der übertragene Inhalt entspricht exakt dem Original, er wurde nicht modifiziert.", "test": "HTTP_PROXY", "status": "ok" }, { "uid": [ 432646, ..., 432656 ], "desc": "Der UDP-Test war erfolgreich. Alle Pakete sind angekommen.", "test": "UDP", "status": "ok" }, { "uid": [ 432645, ..., 432644 ], "desc": "Der TCP-Test war erfolgreich. Es konnte eine Verbindung aufgebaut werden.", "test": "TCP", "status": "ok" }, { "uid": [ 432701 ], "desc": "DNS Abfrage erfolgreich (verwendeter DNS-Server: <IP_ADDRESS>)", "test": "DNS", "status": "ok" }, ..., { "uid": [ 432667, ..., 432703 ], "desc": "Eine DNS-Anfrage für eine nicht existierende Domain war erfolgreich, es wurden keine Einträge gefunden.", "test": "DNS", "status": "ok" }, { "uid": [ 432657, 432658 ], "desc": "Die HTTP Anfrage an den QoS-Testserver wurde nicht verfälscht.", "test": "NON_TRANSPARENT_PROXY", "status": "ok" }, { "uid": [ 432661 ], "desc": "Die Webseite wurde erfolgreich übertragen.", "test": "WEBSITE", "status": "ok" } ] }
7. Change history
| Date | Comment |
|---|---|
2015-09-14 |
Introduction of the change history. Correction of various typos. Hints for sender ID and threadwise speed curve added. |
2017-03-22 |
New filter criteria client_uuid and new output format csv in search for tests by open-data. New RTR logo. |
2018-03-29 |
New Open data fields zip_code is now obsolete and will be removed in future versions |
2018-05-18 |
Open data for individual ping measurement and GPS information |
2018-11-09 |
Open data query for country_location |
2018-12-01 |
Change of the CC licence |


Oct 7, 2013. Giuliana Rancic is optimistic about her future now that her cancer is behind Mommy tweets: Giuliana Rancic's baby news, Vanessa Lachey,
5 days ago Hot pink umbrellas toted by professional models at Night Bright at the Cube, where Giuliana Rancic welcomed fans to Westfield Old Orchard
Oct 11, 2013 Red Carpet Confidential: Why Giuliana Rancic Likes to Splurge More After Her Breast Cancer Diagnosis. Valerie Nome By Valerie. Nome Giuliana and Bill Rancic are ready for a second run at parenthood, and say they' ve lined up their surrogate to give birth to a sibling for their son, Edward
Oct 13, 2013. Beyond her penchant for fedoras and baseball caps, Giuliana Rancic wears a multitude of hats She is co-anchor of E! News, host of "Live From
Oct 17, 2013. Giuliana Rancic has revealed she is addicted to baby strollers. The E! News anchor, who has a 13-month-old. son, Edward Duke, with her Shoes I like, funky foods, crazy thoughts. All the things I come into contact with throughout the course of my day that I feel like sharing P S. Everything will be OK
Oct 19, 2013 Giuliana Rancic isn't afraid to admit she has a problem with. overdoing it when it comes to son Duke's strollers. The E! News host, who became giulianarancic 480 photos; 725389 followers; 59 following Follow Giuliana Rancic. http://www. giulianarancic com · Log in · Privacy · Terms © 2013 Instagram FabFitFun by Giuliana Rancic is a free daily email filled with the latest and greatest in beauty, fitness, diet and wellness Shop the latest G by GIULIANA RANCIC. Women's designer fashion at HSN. com Read customer reviews on these stylish new outfits Oct 15, 2013 October is National Breast Cancer Awareness month, and the nation is going pink to recognize the challenges facing women with breast
Oct 15, 2013 The E! News host and breast cancer survivor is a fitness enthusiast, but she. says this practice helps keep her more balanced than any sweat
Results 1 - 20 of 27 Giuliana Rancic and Efrat Roman Discuss CureDiva. com, a Curated Shop of Fashion and Beauty Must-Haves for Women With Cancer Sep 19, 2013 Giuliana & Bill are loving being parents to their 1-year-old son Duke so much that they want to give him a brother or sister After taking on the Sep 18, 2013. After celebrating Duke's. birthday on Aug 29, Bill and Giuliana Rancic are. ready for their second baby We've got. everything in place. Oct 17, 2013. On Oct 16, TV by the Numbers revealed Giuliana Rancic, who currently stars in Giuliana and Bill, which recently moved from Style to E!, has Get the latest Giuliana Rancic News, Bio, Photos, Credits and More for Giuliana Rancic on TVGuide com Enjoy the best Giuliana Rancic Quotes at BrainyQuote Quotations by Giuliana Rancic, American Journalist, Born August 17, 1974 Share with your friends


Mega Services
Home
Contact
Login
Sign up
Admin
Hello there
Find daily problems and we connect you with a service provider.
Search
Chat
Hi, I am a chat bot
How can I help you?
I need to fix my pipes
Okay, we are sending a plumber and he will be there in 30 minutes
Thanks
Send


In class we are learning about linear regression, fitting a line through data, where the line does not have to pass through the data points precisely.
But we might wonder: Can we find a model for our data that does pass precisely through each point, and won't this model be more useful at predicting the future?
 Enter a list of 7 values into the table below, or click on a button to import prefetched data.
x
f(x)
1
2
3
4
5
6
7
The Lagrange Polynomial, below, passes through all the given data points.
Below is a table of values of the polynomial above, for various inputs, including inputs that correspond to past and future values!
Past
Entered Values
Future
-2
-1
0
1
2
3
4
5
6
7
8
9
10
Graph:
Questions to think about:
The Lagrange Polynomial models the data you input exactly. Based on your observations, though, does it make sense to try to use Lagrange Polynomials to try to predict the future?
To fit n data points, the Lagrange Polynomial is a polynomial of degree n-1. In the above case, n was 7. If you have 2 points, what would the Lagrange Polynomial look like?
In statistics, we try to find a balance between our model closely describing our observations and our model being simple. Think about the situation where our data points fall very close to a parabola.
Think about how you might argue that the best model is a parabola, not a line or Lagrange Polynomial.
Further reading/playing:
It may help to read about overfitting . Essentially, the Lagrange Polynomial is reading too much into the data.
By wanting our polynomial to fit our data exactly, we ignore other, simpler models that fit our data closely, but not precisely.


| studentratings {mitml} | R Documentation |
Contains simulated data for students nested within schools, featuring students' ratings of their teachers' behavior (i.e., disciplinary problems in mathematics and reading class) and their general learning environment (school climate) as well as mathematics and reading achievement scores, and scores for socio-economic status and cognitive ability.
In addition, the data set features the ID of 50 different schools (i.e., clusters), the biological sex of all students, and a broad, additional grouping factor. Different amounts of missing data have been inserted into the data set in a completely random fashion.
data(studentratings)
A data frame containing 750 observations on 10 variables.


--- layout: newsstory title: ONLY A DRAW match: Cambridge City 1 Yeltz 1 ---
After an amazing run of four wins, to be honest it's disappointing we only drew with Cambridge City. I guess that shows how much we've improved over the last few weeks. We're now up to 10th place in the league and almost mathematically safe from relegation.
For more information, you can always read the excellent match reports .
Cambridge City: Davies, Wenlock, Coburn, Holden, Randall, Pincher, Reeder (Wilde 63), Tovey, Taylor (Cleaver 80), Cambridge, Salmons. Subs: Gawthrop, Wilde, Cleaver.
Halesowen Town: McDonnell, Brown, Owen (Cooper 45), Lloyd, Smith, Gardiner, Birch, Aldridge, Thomas, Cartwright, Reed. Subs: Gennard, Collins, Cooper
Referee: D. Whitestone (Northants.) Attendance: 328
Revitalised Halesowen enjoyed long spells of possession in the first half but lacked the killer touch in front of goal to secure victory and were ultimately forced to settle for a point.
For the home side, Ian Cambridge beat Wayne Lloyd to the ball in the 21st minute, but Danny McDonnell was on hand to turn his effort away for a corner before Adam Salmons aimed a fierce diving header wide of the mark following an excellent cross from Neil Coburn three minutes later.
In a flowing move with cross field interchanges between Jason Owen and Paul Birch, Halesowen's Ian Aldridge successfully lobbed goalkeeper Martin Davies in the 24th. minute but his effort struck the top of the crossbar. Three minutes later Aldridge's first time volley fell just wide after Davies had punched clear under pressure from Clinton Thomas.
The visitors took the lead in the 38th minute after persistence from Ashley Brown allowed him to deliver an excellent right wing cross which was headed home by Thomas. With the home side pinned back in their own half, Steve Holden cleared Ian Reed's drive off the line and Davies tipped Wayne Lloyd's close range header over the bar before the half-time interval.
Cambridge levelled in the 55th. minute when Player Manager Chris Tovey headed home a high cross in a crowded goalmouth. Halesowen's Neil Cartwright was then unlucky to see his 72nd. minute drive rebound into safety off the crossbar after his surging run from midfield and Matt Gardiner's drive into the net was ruled offside.
The home side almost stole the points two minutes from time when substitute Chris Cleaver beat the offside trap and place the ball beyond McDonnell in the Halesowen goal, but Adrian Cooper raced back to scoop the ball over the bar.


This feature will allow end-users to filter specific field set by searching them on Dropdown filter bar. After enabling filtering it will filter data on every Filter Debounce Time when on idle after user's every keystroke.
Once after enable filtering by default ornamentum will activate Filter Debounce and set specific Filter Debounce Time in to dropdown. for more details about debouncing please refer Useful Properties from below.
For enabling filtering, it is mandatory to set filterable
to true. by default filterable is set
to false and therefore filtering option will be disabled on default dropdown.
In addition to the filtering property, there are few more properties that will affect to the behaviour of filtering
and can be use with together once filterable
was enabled.
filterDebounce: boolean
Filter Debounce is responsible for listening more user inputs on user every keystroke on dropdown filter bar and search them as a bundle on every Filter Debounce Time. this will be happen recursively if user has continuously providing inputs.
The key advantage is using debounce is reduce client-side operations. because filtering is perform on every Filter Debounce Time rather than filter every keystroke that user enters.
filterDebounceTime: number
This property is uses for defining the debounce time for perform debounce operation and property was depend on Filter Debounce, therefore can't be uses independently on dropdown operations.
filterText: string
This property is uses to override default filter text value for the dropdown and will be automatically filtered according to the provided text on Load Data On Init. with indicating filtered text on filter bar.
Unlike the client side data filtering, server side filtering uses the mechanism to initiate a new API request to fetch data from the server which matches to the particular action whenever a user performs a keyword search. In order to enable this behaviour, it is necessary to use Server-side Data Binding technique.
Also all the properties described in the Useful Properties section, can be used with Server side filtering as well.


{% extends 'base.html' %} {% block title %}Order Form{% endblock %} {% block content %} Start Your Order Order Form Complete this order form to kickstart the songwriting process! We will contact you within 48 hours. The entire process takes up to 4 weeks. {% csrf_token %} {% for each_field in form %} {{ each_field.errors }} {{ each_field.label_tag }} {{ each_field }} {% endfor %} Contact Us Not quite ready to order? Have a burning question? Feel free to drop us an email. We're always happy to chat. Send me an email<EMAIL_ADDRESS>You Tube Check out more music {% endblock content %}
Complete this order form to kickstart the songwriting process! We will contact you within 48 hours. The entire process takes up to 4 weeks.
Not quite ready to order? Have a burning question? Feel free to drop us an email. We're always happy to chat.
Send me an email
You Tube


To complete this form, you must have an Account with Brooks. If you don’t have
one, please request for an Account
Opening Form to create an account before you can apply for this product. All information provided on this forms
is
treated with the utmost confidentiality
High Premium InvestmentBrooks Asset Management Company Reg. No. CA-86,478


qjoypad
Translate input from gamepads or joysticks into keyboard strokes or mouse actions.
More information: home page
- Start QJoyPad:
qjoypad
- Start QJoyPad and look for devices in a specific directory:
qjoypad --device=path/to/directory
- Start QJoyPad but don't show a system tray icon:
qjoypad --notray
- Start QJoyPad and force the window manager to use a system tray icon:
qjoypad --force-tray
- Force a running instance of QJoyPad to update its list of devices and layouts:
qjoypad --update
- Load the given layout in an already running instance of QJoyPad, or start QJoyPad using the given layout:
qjoypad "layout"


Should I click 'accept' on websites' messages about cookies?
I find the GDPR pop-ups infuriating and often just agree because I want to get rid of them
Every week a Guardian Money reader submits a question, and it’s up to you to help him or her out – a selection of the best answers will appear in next Saturday’s paper.
Every website I go on has one of those infuriating GDPR messages about cookies that I have to accept or decline. I’ve got to the point where I just blindly click “accept” to be done with it. Am I making a big mistake? If I press “decline” will it make any difference?
Do you have a problem readers could solve? Email your suggestions to<EMAIL_ADDRESS>or write to us at Money, the Guardian, Kings Place, 90 York Way, London N1 9GU.


_
| |
____ | | ____
| _ \| || _ \
| | | | || |_| |
|_| |_|\_) __/
|_|
NLP
The natural language processing (NLP) module enables Roboy to process and understand the human language.
That way he can interpret the meaning of the detected sentences.
We use a free, open-source NLP library for advanced NLP in Python: spaCy
Extracted Features
| Feature | Ravestate Properties/Signals | Description | Example Sentence: 'Revolutions need six fancy chickens!' |
|---|---|---|---|
| Tokenization | "nlp:tokens" (property) | Segmenting text into words, punctuation marks etc. | 'Revolutions', 'need', 'six', 'fancy', 'chickens', '!' |
| Part-of-Speech (POS) Tagging | "nlp:postags" (property) | Assigning word types to tokens | 'NOUN', 'VERB', 'NUM', 'ADJ', 'NOUN', 'PUNCT' |
| Detailed POS Tag | "nlp:tags" (property) | Fine-grained part-of-speech | 'Revolutions' has the tag: 'NNS', which stand for: noun, plural 'need' has the tag: 'VBP', which stands for: verb, non-3rd person singular present List of POS tags |
| Lemmatization | "nlp:lemmas" (property) | Assigning the base forms of words | 'Revolutions' has the lemma: 'revolution' 'was' would have the lemma: 'be' |
| Named Entity Recognition (NER) | "nlp:ner" (property) | Labelling "real-world" objects | 'six' has the NER: 'CARDINAL', which are numerals that do not fall under another type List of NERs |
| Dependency Parsing | Assigning syntactic dependency labels, describing the relations between individual tokens | 'six' is a 'nummod' (numeric modifier) for 'chickens' List of dependencies displaCy Dependency Visualizer |
|
| Triple Extraction | "nlp:triples" (property) | A triple consists of subject, predicate, object of sentence | Triple: subject: 'Revolutions', predicate: 'need', object: 'chickens' |
| About Roboy | "nlp:roboy" (property) | Detecting whether sentence is about Roboy | 'you', 'roboy', 'robot', 'roboboy', ... |
| Yes-No | "nlp:yesno" (property) | Detecting answers to yes-no questions | Checking for 'yes', 'no', 'i don't know', 'probably', 'probably not' and synonyms of these |
| Sentence Type: Question | "nlp:is-question" (signal) | Detecting whether sentence is a question | |
| Play Game | "nlp:intent-play" (signal) | Interlocutor wants to play a game | input: "I want to play", "I like games" or something similar |
Additional features can be added and published to the system. All existing features can be found here.
Using the Features
React to Property Change
Each feature is stored in a ravestate property. A state which wants to access a property needs read permissions for that property.
Example: State that reads the "yesno" property
@state(
cond=s("nlp:yesno:changed"), # state reacts to a change in the 'yesno' property
read="nlp:yesno", # state is allowed to read the 'yesno' property
write="rawio:out") # state is allowed to write to the output property
def postive_chicken(ctx: ContextWrapper):
if ctx["nlp:yesno"] == "yes":
ctx["rawio:out"] = "You seem to be a positive chicken!"
React to Signal Emission
For 'Sentence Type: Question' a signal is emitted.
Example: State that reacts to the "is-question" signal
@state(
cond=s("nlp:is-question"), # state reacts to the is-question signal
write="rawio:out") # state is allowed to write to the output property
def curious_chicken(ctx: ContextWrapper):
ctx["rawio:out"] = "You seem to ask a lot of question, chicken!"
Using the Triples for Sentence Analysis
The triple extraction is done in extract_triples.py by using the dependency tree of the sentence. A dependency tree shows the relation between the words of a sentence. The finite verb (predicate) is the structural center of the sentence and therefor of the tree. So starting with the predicate the algorithm searches through the dependency tree to find subject and object.
Analyzing a Sentence
Example: 'Chickens like revolutions' reaction state Triple: subject: 'Chickens', predicate: 'like', object: 'revolutions'
@state(
cond=s("nlp:triples:changed"), # state reacts to a change in the 'triples' property
read="nlp:triples", # state is allowed to read the 'triples' property
write="rawio:out") # state is allowed to write to the output chanel
def postive_chicken(ctx: ContextWrapper):
triple = ctx["nlp:triples"][0] # gives you a Triple object
if triple.match_either_lemma(subj={"chicken", "dinosaur"}):
# match_either_lemma() is a method in the Triple class
# returns true when subj, pred or obj have the desired value
ctx["rawio:out"] = "You said something about a chicken, i like chickens!"
# check predicate and object correspondingly


|
Connected Home over IP
672cf7684
|
#include <controller/java/AndroidKeyValueStoreManagerImpl.h>
Public Member Functions | |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| void | InitializeMethodForward (JNIEnv *env) |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| CHIP_ERROR | Init (const char *fileName) |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) const |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| void | Init (const char *file) |
| Initalize the KVS, must be called before using. More... | |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| void | Init () |
| CHIP_ERROR | _Get (const char *key, void *value, size_t value_size, size_t *read_bytes_size=nullptr, size_t offset=0) const |
| CHIP_ERROR | _Delete (const char *key) |
| CHIP_ERROR | _Put (const char *key, const void *value, size_t value_size) |
| Public Member Functions inherited from chip::DeviceLayer::PersistedStorage::KeyValueStoreManager | |
| CHIP_ERROR | Get (const char *key, void *buffer, size_t buffer_size, size_t *read_bytes_size=nullptr, size_t offset_bytes=0) |
| Reads the value of an entry in the KVS. More... | |
| template<typename T > | |
| CHIP_ERROR | Get (const char *key, T *value) |
| This overload of Get accepts a pointer to a trivially copyable object. More... | |
| CHIP_ERROR | Put (const char *key, const void *value, size_t value_size) |
| Adds a key-value entry to the KVS. More... | |
| template<typename T > | |
| CHIP_ERROR | Put (const char *key, const T &value) |
| This overload of Put accepts a reference to a trivially copyable object. More... | |
| CHIP_ERROR | Delete (const char *key) |
| Removes a key-value entry from the KVS. More... | |
Friends | |
| class | KeyValueStoreManager |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManager & | KeyValueStoreMgr () |
| Returns the public interface of the KeyValueStoreManager singleton object. More... | |
| KeyValueStoreManagerImpl & | KeyValueStoreMgrImpl () |
| Returns the platform-specific implementation of the KeyValueStoreManager singleton object. More... | |
Additional Inherited Members | |
| Protected Member Functions inherited from chip::DeviceLayer::PersistedStorage::KeyValueStoreManager | |
| KeyValueStoreManager ()=default | |
| ~KeyValueStoreManager ()=default | |
| KeyValueStoreManager (const KeyValueStoreManager &)=delete | |
| KeyValueStoreManager (const KeyValueStoreManager &&)=delete | |
| KeyValueStoreManager & | operator= (const KeyValueStoreManager &)=delete |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Delete | ( | const char * | key | ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Delete | ( | const char * | key | ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Delete | ( | const char * | key | ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Delete | ( | const char * | key | ) |
|
inline |
|
inline |
|
inline |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Delete | ( | const char * | key | ) |
|
inline |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Get | ( | const char * | key, |
| void * | value, | ||
| size_t | value_size, | ||
| size_t * | read_bytes_size = nullptr , |
||
| size_t | offset = 0 |
||
| ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Get | ( | const char * | key, |
| void * | value, | ||
| size_t | value_size, | ||
| size_t * | read_bytes_size = nullptr , |
||
| size_t | offset = 0 |
||
| ) |
|
inline |
|
inline |
|
inline |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Get | ( | const char * | key, |
| void * | value, | ||
| size_t | value_size, | ||
| size_t * | read_bytes_size = nullptr , |
||
| size_t | offset = 0 |
||
| ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Get | ( | const char * | key, |
| void * | value, | ||
| size_t | value_size, | ||
| size_t * | read_bytes_size = nullptr , |
||
| size_t | offset = 0 |
||
| ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Get | ( | const char * | key, |
| void * | value, | ||
| size_t | value_size, | ||
| size_t * | read_bytes_size = nullptr , |
||
| size_t | offset = 0 |
||
| ) | const |
|
inline |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Put | ( | const char * | key, |
| const void * | value, | ||
| size_t | value_size | ||
| ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Put | ( | const char * | key, |
| const void * | value, | ||
| size_t | value_size | ||
| ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Put | ( | const char * | key, |
| const void * | value, | ||
| size_t | value_size | ||
| ) |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Put | ( | const char * | key, |
| const void * | value, | ||
| size_t | value_size | ||
| ) |
|
inline |
|
inline |
|
inline |
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::_Put | ( | const char * | key, |
| const void * | value, | ||
| size_t | value_size | ||
| ) |
|
inline |
| void chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::Init | ( | ) |
|
inline |
Initalize the KVS, must be called before using.
| CHIP_ERROR chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::Init | ( | const char * | fileName | ) |
| void chip::DeviceLayer::PersistedStorage::KeyValueStoreManagerImpl::InitializeMethodForward | ( | JNIEnv * | env | ) |
|
friend |
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the public interface of the KeyValueStoreManager singleton object.
Returns a reference to the public interface of the KeyValueStoreManager singleton object.
Chip applications should use this to access features of the KeyValueStoreManager object that are common to all platforms.
chip application should use this to access features of the KeyValueStoreManager object that are common to all platforms.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.
|
friend |
Returns the platform-specific implementation of the KeyValueStoreManager singleton object.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the ESP32 platform.
chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the selected platform.
Chip applications can use this to gain access to features of the KeyValueStoreManager that are specific to the Zephyr platform.


< Back
This is a demonstration of Leaflet.js running thanks to the
jscompat shim
.
You shouldn't see this


A Deep Learning Approach to Robot Perception and SLAM
My current research focuses on robust feature extraction from LIDAR, RGB, and RGBD data to aid in long term loop closures during Simultaneous Localization and Mapping (SLAM). I am using modern Deep Learning techniques, such as Generative Adversarial Networks, to extract robust features from large amounts of unlabeled data.
Autonomous Robotic Snowplow
Led team to a 2nd place finish in the ION Autonomous Snowplow Competition. Focused on sensor fusion and localization techniques, including an Extended Kalman Filter and Ultra-Wideband sensors. Developed in C++/Python using the Robot Operating System (ROS) framework. Also, redesigned steering mechanism, actuated plow, and power system, and path planning and steering algorithms.
Neural Controller for Legged Locomotion
Built a robotic cockroach leg and neural controller to study biologically hypothesized neural control networks for joint coordination. Focus was on the dynamics of networks of simulated neurons, central pattern generators, and force feedback. Worked directly with biologists to hypothesize neural connections.
Amphibious Whegs® Robot
Design, built, and tested a rugged robot, which utilized wheel-legs, at tail, and a sealed body to climb obstacles up to 48cm, traverse uneven terrain, and move freely underwater.
Autonomous Vehicle Localization Testing
Helped the robotics division of the National Institute of Standards and Technology install a multi-acre Ultra-Wideband localization system to test the localization systems of autonomous vehicles.
Search and Rescue Robot Testing
Helped the robotics division of the National Institute of Standards and Technology administer testing for search and rescue robots to instruct in a local county robot procurement.


-
Create the distribution using your favorite build tool e.g. Ant.
-
Create MD5 and SHA1 hashes of the distribution file.
-
Digitally sign the distribution, for example:
gpg --armor --output ClickIDE-X.X.X.zip.asc --detach-sig ClickIDE-X.X.X.zip
-
Upload the distribution to your account at people.apache.org
under the folder ~/public_html/click/SUBPROJECT/X.X.X, where
SUBPROJECT is the name of the subproject and X.X.X
is the version.
For example version 2.2.0 of subproject ClickIDE could be published to:
~/public_html/click/clickide/2.2.0
Make sure the uploaded files have the right permissions (664)
and belong to the 'click' group to ensure that other members
have proper access to these files.
If not execute the following commands to ensure file and directory
permissions are correct:
ssh people.apache.org
cd ~/public_html/click/clickide/X.X.X
find . -type d | xargs chmod 775
find . -type f | xargs chmod 664
chgrp -R click *
-
Verify the digital signatures at people.apache.org to
ensure nothing went wrong with the upload.
Please note if this is the first time you verify your key
at people.apache.org, you'll need to import your public
key first.
Assuming your public key ID is 'B51329CB' and your key is available
from the public key server 'pgp.mit.edu', the following command
will import the key on people.apache.org:
ssh people.apache.org
gpg --keyserver pgp.mit.edu --recv-keys B51329CB
Next verify the signature with the following command: (Replace SUBPROJECT with the name of the actual project.)
ssh people.apache.org
cd ~/public_html/click/SUBPROJECT/X.X.X
gpg --verify SUBPROJECT-X.X.X.zip.asc SUBPROJECT-X.X.X.zip
-
Releases must be voted on before they are published. Please
see the Voting
section for details.
-
Releases are published at people.apache.org under
the folder:
/www/www.apache.org/dist/click/SUBPROJECT/X.X.X
For example ClickIDE will be published to the folder:
/www/www.apache.org/dist/click/clickide/X.X.X
An easy way to do this is to copy the files in your public_html
folder for example:
ssh people.apache.org
cp ~/public_html/click/clickide/X.X.X/ /www/www.apache.org/dist/click/clickide/X.X.X
-
Email release announcement to click-user and click-dev
mailing lists.


Is there a veil covering the young gills?
Yes
No
Help, I'm not sure!
Is there a thin veil that dissapears and does not form a ring on the stalk?
Yes
No
Help, I'm not sure!
Does the stalk break like chalk? It may look milky or juicy when cut.
Yes
No
Help, I'm not sure!
Sounds like a Milk Cap or Russula.
View Milk Caps and Russulas
Start Over


First off, some background. I'm only 13 (no comments please) and have tried a few of the typical things you would expect a child of my age to have tried (cannabis, salvia, Absinthe, DMX) and a few you may not expect (prescription codeine pills, nutmeg) so when a mate of mine brought a few bottles of poppers into school I wasn't shocked or anything like that.
I got in a bit late as I had to talk to the head because I returned from my suspension that day and when I entered the classroom I instantly was hit by a strong smell which reminded me more of anesthetic than say glues or stuff like that.  I was handed the bottle and got straight away to sniffing and was slightly surprised that I didn't feel it the second my head lifted, as I was used to after pot. So I sat up and went hmmm and decided to take three more strong sniffs...BIG MISTAKE!
The second I put the bottle down after the forth strong snort was this huge feeling coming into my head and it seemed to be pulling my ears apart and my head felt like it was growing. Then I realised I could hear rather than feel my pulse right underneath my ears and when I looked the teacher in the eye I couldn't help but laugh and fall over. Unfortunently then the next snorts came in and they made it extremely uncomfortable, my face was extremely red and my heart beat could be seen on the other side of my shirt. Also my lungs had that strange feeling that I get when I sway from side to side with only my top half, deflating them. I began to hypervenilate and felt very dizzy. I rather stupidly I thought that I had swallowed some as I had been told that swallowing kills, so I began spitting everywhere only to land myself in trouble and be sent out. On my way out I think I banged into every desk and and the door and collapsed outside it.
However once this odd feeling left it was very pleasant, a strong buzz. I felt extremely talkative and talked to the teacher as my friend and felt quite untouchable. We consequently did this for the rest of the day in obviously smaller doses until we had tremendous headaches and stopped for around an hour. Then after school had ended we planted our selves in the park and opened a new bottle and took out the grass.
However the weed felt different this time, more visual differences than normal and it felt as if time was continuing around me and I was in a slower world, quite nice really. After we had all finished we all parted our seperate ways. The bus ride home was really good fun however I don't know if I can put that down to the poppers or the weed but the lights felt brighter and it felt like the chair was hugging me into it so I actually missed my stop and got off later as I felt to comfortable to get up. The feelings of it all left rather quickly after that, faster than normal for weed, and I went back home and had a rather normal evening. The only difference then was how long I slept for (16 hours) which was quite long for me but that probably just goes down to me using all my energy talking when I was on the alkyl during school.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Utility Apps
Clock/Epoch Time
Timer/Stop Watch
IP Finder
Language Translator
Language Translator
English → Hindi
English to Hindi Translation
Hard work, honesty, success!