This forum uses cookies This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

 Bug in "average" Physikator Junior Member Posts: 35 Threads: 6 Joined: Jan 2019 01-30-2019, 09:12 PM (This post was last modified: 01-30-2019, 09:58 PM by Physikator.) I'm happily using phyphox for measuring and visualising all kinds of movement (skiing, driving by car ...). I just entered the Neuland of the editor for new experiments and I believe I found a bug: If I want to calculate a standard deviation without the corresponding average, the output strangely shows negative numbers. It turned out that I had do connect the "average" output as well to only receive positive standard deviations. The following experiment shows standard deviations of the pressure in the order of 1bar: Code:```     average_test     no category                   t         x         average         stddev                                x             t                                                   t             average                               x             stddev                                                          stddev                 average                                      ``` Sebastian Staacks Administrator Posts: 321 Threads: 6 Joined: Aug 2018 Institution: RWTH Aachen University 02-02-2019, 12:28 PM Thanks for reporting this. This indeed is a bug. The module does not verify that the output is present and derails before writing the stddev output. Will fix this with the next update. Physikator Junior Member Posts: 35 Threads: 6 Joined: Jan 2019 02-02-2019, 04:43 PM I might have found something in "max" as well, but maybe this is just a case of "it's your own fault": Wanting to find the maximum of an x-component of a sensor, I stubbornly conncted it to the x-input of "max", leaving the y-input open. This consistently leads to a crash. It's great to get a message from phyphox when trying to load a file with obvious bugs (such as unconnected views or unused sensors), so maybe this could be on the "obvious"-list. Sebastian Staacks Administrator Posts: 321 Threads: 6 Joined: Aug 2018 Institution: RWTH Aachen University 02-03-2019, 08:43 PM Yes, it should be on the obvious list The max module always needs y values and looks for the maximum in there. The x is optional. If given, the corresponding x for the maximum y value is returned as well. So, if you want to find the max in a series of values, you need to connect it to y, even if you use those values as x in another context. Are you trying your phyphox-files on iOS? On Android, there should be a (more or less comprehensible) error instead of a crash. On iOS, the current parser tends to crash the entire app (which on iOS simply means that the app closes). The good news is, that the parser on iOS has already been entirely rewritten and will be released with version 1.1.0. With that version, you should get precise errors on iOS. « Next Oldest | Next Newest »

Forum Jump: