Timeline for Automation of finding a starting point of measurement in a large dataset
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 28, 2020 at 13:10 | vote | accept | tildekara | ||
| Sep 28, 2020 at 9:39 | answer | added | Kasra Manshaei | timeline score: 1 | |
| Sep 28, 2020 at 9:20 | history | edited | tildekara | CC BY-SA 4.0 |
added 4 characters in body
|
| Sep 28, 2020 at 9:13 | history | edited | tildekara | CC BY-SA 4.0 |
added 124 characters in body
|
| Sep 28, 2020 at 9:10 | comment | added | tildekara | @KasraManshaei Good point! I didn't specify it (I'll edit post) but the beggining of raise when I choose manually is very dependent from my choosing. I pick a point that is the closest to rising signal but is still somewhere in the middle of signal noise before rising. One point above or below doesn't bother me that much. I need it to offset the whole signal and set the point as 0 to then perform curve fit so the difference between 0 and 0.0001 points won't be a problem. | |
| Sep 28, 2020 at 9:02 | comment | added | Kasra Manshaei | The main question is how do you determine the first rising point. Speaking based on the experience, they can just be roughly estimated (due to noise) and more or less using what you are doing now. The evidence is the fact that even in the first figure the marked point is not exactly the beginning of raise (next immediate point is lower in magnitude) ... I think u need to expalin ur question more than focusing on python code. How do you determine the beginning of raise? | |
| Sep 28, 2020 at 8:52 | history | asked | tildekara | CC BY-SA 4.0 |