Re: Quick script to check data logger data

Replies are listed 'Best First'.
Re^2: Quick script to check data logger data by GrandFather (Saint) on Aug 08, 2024 at 21:21 UTC
I pick PDL up for tasks occasionally, but not often enough to maintain fluency with it. It's one of those catch-22 situations where PDL would be a really handy tool to have in the toolbox, but <fluency> * <need to use> never quite peeks over the <is more productive with> threshold. Just a little more <need to use> would increase <fluency> enough to make the difference, but I find too many other things to occupy my time so don't go out of my way enough to find excuses to use it. Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond	[reply]
Re^3: Quick script to check data logger data by etj (Priest) on Aug 10, 2024 at 02:44 UTC
I'd be interested to see a bit more concrete data and the problem you're solving, since I expect it would be easy for a journeyman like me to turn that into a couple of lines of PDL; that would then be a useful example I could then steal into some docs. Here, that would include a screenshot of how the Tk window actually looks, since PDL has some really good plotting stuff available.	[reply]
Re^4: Quick script to check data logger data by GrandFather (Saint) on Aug 11, 2024 at 10:09 UTC
Turns out when I said "now we are starting to collect data", I spoke too soon. There are bugs in the software that drive the logger and, after months of back and forth between us and the manufacturer, we haven't been able to get the system to work correctly. The data consists of measurements in two axis from an induction magnetometer at 64Hz. The analysis looks for signals at fairly low frequency (7Hz maybe) that are related to some ionospheric phenomena I've forgotten about. Data files are a day's worth of data can come out to around 21MB. My test script looks at the first 16 seconds (1024 points) and plots a simple frequency/amplitude graph just to check that the data looks sane (basically that it has wiggly bits). The data below is fairly typical and shows a spike just below 8Hz - the interesting bit to the scientists. Absolute amplitude isn't very interesting for a quick assessment of the system. Read more... (16 kB) Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond	[reply] [d/l]
Re^5: Quick script to check data logger data by etj (Priest) on Aug 11, 2024 at 20:55 UTC
Re^5: Quick script to check data logger data by etj (Priest) on Aug 11, 2024 at 18:51 UTC
Re^5: Quick script to check data logger data by etj (Priest) on Aug 11, 2024 at 18:43 UTC
Re^5: Quick script to check data logger data by cavac (Prior) on Aug 12, 2024 at 17:00 UTC
Re^6: Quick script to check data logger data by GrandFather (Saint) on Aug 12, 2024 at 23:09 UTC
Some notes below your chosen depth have not been shown here
Re^2: Quick script to check data logger data by cavac (Prior) on Aug 12, 2024 at 16:49 UTC
etj, i had a similar thought regarding Net::Clacks. I mean, it's a sensor that delivers data in real time. Not having that update up on some web page, also in real time (complete with timestamp of last sucessful read) would give me sleepless nights. Ok, yes, admittedly, it would also give me sleepless nights WITH real time monitoring. At least everytime that sensor runs into trouble, a red alarm light would light up on my big DIY LED status panel (next to my computer) and the master caution alarm would start to blare. "This thing watches for geomagnetic storms. If it fails, better assume that a large one is in progress and has taken out the sensor"(). () "Fail save" wakes you up at night. "Fail deadly" keeps you asleep forever. PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP Also check out my sisters artwork and my weekly webcomics	[reply]