sensordata | Simple python scripts to read sensor data

First filter, then map and filter the inner property values through the map.

I did some changes to my code to check the contents of the const sensorData = tryParseJson(data) as shown below.

try this code:

I think problem on alarm table. Id for alarm is identity so you not need to add alarm id And Second thing is you are modifying two tables at same time may be this give exception.

To illustrate I made a for loop, since the provided code example is limited. What you probably want to do, like @Parfait said, is that you initialize a variable before the loop.

This could be a list which you fill and later on create a dataframe with. Or you can directly append to the dataframe for every d value coming in. The use-case here is not very clear, but it seems to me you want to update for every new d immediately.

Hope this example can help:

I just want to start by saying that there are many ways to do this, and what's considered the "best" approach is highly dependent on the specifics to your use case (and sometimes personal preferences).

The most important thing to remember is that the watch has very limited resources (battery, memory, CPU) compared to a typical phone.

Here are a few things to keep in mind no matter what your exact solution will look like:

1. Writing to a file is an expensive operation. Doing this for every data point you receive from a sensor is not ideal. Consider saving your data to a database using Room instead. An easier alternative, as long as you are OK potentially losing some data if the app crashes or the device reboots unexpectedly, is to keep it in memory. This can be done using a basic array or some sort of Map (timestamp and value) depending on exactly what data you need. You can also use a hybrid of the two approaches and save data in batches.

2. Sending data between the watch and the phone is also expensive. I highly suggest storing things on the watch itself and transfer it to the phone only when needed. This can be a manual trigger, daily at a certain time, when the watch is charging, or some other clever strategy to minimize the impact on the watch's battery life.

3. You can send your data to the phone using the Wearable Data Layer API. You will have to set up either a MessageClient or a ChannelClient depending on how much data you need to transfer. If you stick to data structures that are supported by Android (as opposed to creating your own one), sending them over should be fairly straight forward.

4. If you need to process or format your data in order for it to be easily analyzed in MATLAB, consider doing this on the phone rather than the watch. Simpler operations on reasonably sized data sets can of course be performed directly on the watch.

Exactly how you decide to get the file to your computer is outside of the scope of what I'm trying to answer here. There are plenty of well-documented ways to do this. The easiest being to manually transfer it via adb. This can be done directly from the watch too, so you don't even have to send data to the phone.

My original comment:

Side note: Whenever I see (e.g.) v1 v2 v3 v4 v5 I want to replace it with an array v[5]. So, in struct area, you want: struct subarea sub_area[5]; This will greatly simplify your code. You already do this in main – Craig Estey

Your response:

@Craig Estey Ye don't have a huge experience with debuggers yet, usually just use printfs, but sounds very helpful so ill youtube a guide side note: very helpful we didn't foresee this at first but would simplify so much, ty4input – Thybo

I've done better(?) I've done the preliminary restructuring of your code. I believe this will be helpful to others in addition to yourselves.

I'm sorry, but (and I'm saying this with kindness), the code needs a lot of restructuring. The sheer [needless] complexity could be masking numerous bugs.

Things to note:

1. Passing a struct by value is hazardous. It is legal, but it makes the code complicated. Passing by pointer is 99.44% of the time better. You can just modify the given struct "in-place" rather than having to return it [again, by value].
2. Learn about iterating through an array by using a pointer to the "current" element instead of an index. You'll see this in the FORALL loop below.
3. Don't "replicate" code. Notice what happens when using arrays. Instead of (e.g) four copies of the code, we have one
4. Instead of 4 areas (e.g. area1, area2, area3, area4), if we had 10,000 areas. Would you replicate the code 10,000 times as was done in (e.g.) empty_trash?
5. I added typedef for your two struct to simplify things a bit.
6. I've added a few advanced techniques, such as the use of the FORALL macro to traverse arrays.

I've used preprocessor conditionals to denote old code vs new:

You use large amount of delays to put the threads into the sleep state. Also you are using an infinite loop without any condition to break the loop here: