{"_id":"58fbcdb4809fc30f00f2dc04","user":"58fbcc0bd8c0ba0f00cf52d6","version":{"_id":"5511fc8d0c1a08190077f90f","__v":11,"project":"5511fc8c0c1a08190077f90c","createdAt":"2015-03-25T00:08:45.273Z","releaseDate":"2015-03-25T00:08:45.273Z","categories":["5511fc8d0c1a08190077f910","5511fd52c1b13537009f5d31","568ecb0cbeb2700d004717ee","568ecb149ebef90d0087271a","568ecb1cbdb9260d00149d42","56a6a012b3ffe00d00156f1e","56a6bfe37ef6620d00e2f25f","58fbccb5809fc30f00f2dc03","58fbcd136b29580f00d8ff3a","5942ec4d50b8a900373ce9ff","59481476d305c20019295d8c"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":0,"project":"5511fc8c0c1a08190077f90c","category":{"_id":"58fbcd136b29580f00d8ff3a","__v":0,"project":"5511fc8c0c1a08190077f90c","version":"5511fc8d0c1a08190077f90f","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-04-22T21:37:23.604Z","from_sync":false,"order":1,"slug":"audio-retrieval-and-analysis","title":"Audio Retrieval and Analysis"},"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-04-22T21:40:04.218Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"Having defined the motivation behind our audio analysis, we will go on to explain how our data flow is structured.\n\nAs mentioned, we will have [Alpha Sensor Kits](doc:alpha-sensor-kit) deployed all around the world and gathering audio samples. At the same time, the boards will be analyzing the data and producing results for the beekeepers to see in their mobile phone through our Buzzbox App.\nYou can check the current status of the analysis in the [Theory behind Audio Analysis](doc:theory-behind-audio-analysis) section.\n\nServer-side analysis will be used to perform a general analysis and training process using all the data we have received. This will lead to incremental improvements to our understanding of how different beehive behaviors are translated into different sound characteristics, our algorithms and software, and the experience for beekeepers all over the world.\n\nThe audio data flow can be then summarized in the following graph:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/3a68269-dataflow.PNG\",\n        \"dataflow.PNG\",\n        1034,\n        783,\n        \"#e8e3db\"\n      ],\n      \"caption\": \"Audio Data Flow\"\n    }\n  ]\n}\n[/block]\nDuring the next sections, we will provide details on the part played by the [Hardware](doc:hardware-recommendations) and [Server-side Storage and Processing](doc:server-side-storage-and-processing) in this data flow.","excerpt":"","slug":"data-flow-structure","type":"basic","title":"Data Flow Structure"}

Data Flow Structure


Having defined the motivation behind our audio analysis, we will go on to explain how our data flow is structured. As mentioned, we will have [Alpha Sensor Kits](doc:alpha-sensor-kit) deployed all around the world and gathering audio samples. At the same time, the boards will be analyzing the data and producing results for the beekeepers to see in their mobile phone through our Buzzbox App. You can check the current status of the analysis in the [Theory behind Audio Analysis](doc:theory-behind-audio-analysis) section. Server-side analysis will be used to perform a general analysis and training process using all the data we have received. This will lead to incremental improvements to our understanding of how different beehive behaviors are translated into different sound characteristics, our algorithms and software, and the experience for beekeepers all over the world. The audio data flow can be then summarized in the following graph: [block:image] { "images": [ { "image": [ "https://files.readme.io/3a68269-dataflow.PNG", "dataflow.PNG", 1034, 783, "#e8e3db" ], "caption": "Audio Data Flow" } ] } [/block] During the next sections, we will provide details on the part played by the [Hardware](doc:hardware-recommendations) and [Server-side Storage and Processing](doc:server-side-storage-and-processing) in this data flow.