SQL Server Integration Services (SSIS) does a good job of this I think. SSIS is made for manipulating data flows. The flow of data happens to be very well represented in many cases by visual network flow diagrams. Most of the common patterns of data flow are implemented as drag and drop widgets.
That said, as necessary, you can do pretty much anything in that environment as code if you want. The best thing about the language, though, is that /if/ you go down the path of coding something out instead of using a common pattern, it forces you to ask "Why am I doing something out of the norm here?" Sometimes you have a valid reason. Sometimes you don't and that question course corrects you back into a maintainable architecture. It's a very niche language (even mostly vendor locked down), but I think it's a great example of a visual programming environment that's mostly great to work in.
My wife is an instructor at University of Louisiana at Lafayette. Yesterday all faculty/staff/students got an email about a girl who was assaulted. She was walking down a street close to the university. Two white men (one in a Trump hat) pulled up next to her in a car, hopped out, hit her over the head with something then stole her hijab and wallet. http://www.theadvertiser.com/story/news/crime/2016/11/09/ul-...
Can you guys give any insight into how you're combining the sensor data? I'm a newb on the topic, but I was trying to do something similar in a different domain and got stuck trying to make a kalman filter. I tried to get an EE friend to explain them to me, but I couldn't get it.
Multiple fields actually invented Kalman filters independently and it turns out they are all actually the same thing, they just have widely varying derivations. My personal favourite explanation comes from the textbook: Probabilistic Robotics (2005) by Thrun, Burgard, and Fox.
It's the start of the Summer, I'm in my 2nd year MS-CS. I began a simulation last night at 9PM that's still running (usually 14 hour turnaround). I just got in, sat at my desk and thought "I'm bored, guess I'll check HN" and THIS is what I see.
I've been authoring a post on solving interview questions in map/reduce between experimental runs myself, so I guess I already hit the "bored graduate student" point too...
I remember having to resist the urge to map/reduce everything in interview questions :P. Somehow, I don't think interviewers want to hear how you'd use a cannon to solve a tiny problem.
That said, as necessary, you can do pretty much anything in that environment as code if you want. The best thing about the language, though, is that /if/ you go down the path of coding something out instead of using a common pattern, it forces you to ask "Why am I doing something out of the norm here?" Sometimes you have a valid reason. Sometimes you don't and that question course corrects you back into a maintainable architecture. It's a very niche language (even mostly vendor locked down), but I think it's a great example of a visual programming environment that's mostly great to work in.