Love it! Trying to use it with my nanoPAD2 and it only outputs `note_on` and `note_off` events. Can we bind on these? Example output:
22:56:38.740 note_on channel=1 note=36 velocity=89 [nanoPAD2 PAD]
192 karma · joined August 31, 2011
22:56:38.740 note_on channel=1 note=36 velocity=89 [nanoPAD2 PAD]
def my_func(a: int, b: int):
print(a+b)
# both of these can be used
my_func(1, 2)
my_func(a=1, b=2)On the one hand, I'm not expecting high signal from this because it's not standardized - too many external variables you can't control. It would also be pretty hard to evaluate as "just watching the path of struggle" is very subjective.
On the other hand, potential "public good" benefit can't be ignored, plus it can be added to interviewees' public resume/github account to be shown to the future employers.
The downside is it looks more brittle than the simpler approaches. Upside is performance plus ability to revoke tokens.
I looked up "Валентина Сынах" Skype user and, as expected, their full phone number is +7904xxxxxxx (see full number in the article), with Russian prefix +7. Note, WHOIS records have US number +1904xxxxxxx. Not sure why the author only searched for the last 10 digits.
+7 904 code is a very busy area code in Russia shared by several major carriers, covering the majority of Russian regions, so the probability of someone having any particular 7 digits in that area is pretty high. For example there's someone else registered in Skype with number +7904xxxxxx4, just one digit apart. I haven't been able to find an English source, but you can look at the list of carriers and regions in Russian in [1].
Also, US area code +1 904 matches the address in WHOIS records (both Jacksonville, FL), so at least it doesn't look like someone just changed the first digit and used their own Russian number.
Power of 2 requirement stands, though.
Currently std dev of each position coord in rest is 1.9mm.
Fusion with IMU is the next level and is usually done later down the line because it needs to be tuned for particular model. Yes, the drone does that.
The timing calculation still needs to be done somewhere though, I wish there was a module that would do it internally and just publish the timing numbers - that would be more scalable and then even Arduino would be able to handle several sensors.
There's a whole bunch of indoor positioning methods, having different precision/simplicity/cost profiles, so you might need to shop around. Probably cheapest and closest to my sensor is ultrasound sensors like http://www.marvelmind.com
Seamless switching is definitely doable and shouldn't be hard, just need some time to implement. I'm using PX4 autopilot and it's very friendly for adding new functionality.
Orchestration is also close - in current demo both station and drone use Wifi to coordinate, so it's a matter of adding new logic.
Currently the most limiting resource for that project is my time :) I'd be happy if other people would want to join!
Yep, I'm using Mavlink protocol (specifically ATT_POS_MOCAP message) to feed 3d position to the drone autopilot.
Let me know if you have any questions!
errTo = require 'errto'
readDirectoryAsync = (catalog, cb) ->
fs.readdir catalog, errTo cb, (filenames) -> # Notice no 'err' argument.
# Error check is done automatically in errTo and cb(err) is called on error.
# Subsequent code is called ONLY when no error given.
callback null, filenames
# Express sample.
app.get '/', (req, res, next) ->
readDirectoryAsync __dirname, errTo next, (filenames) -> # Use Express error handling by calling next(err)
res.send filenames