1,856 karma · joined September 24, 2014
[0] almost literally by the thermal numbers
So there you have, one reason to take this course that is not "roll your own crypto" (which you should never do, unless you really really really know what you're doing. And even then you should check with a few people smarter than you to make sure everything is as you think it is.
Obviously that is how _I_ type code, and not something that can generalize to how others work. So it's my preference to still think about my code before, and while, I write it.
When I was a child a hairdresser cut a bit of my ear. Obviously I cried at the moment, it hurt. I may have been anxious about going to get a haircut for a couple of times afterwards. But then we found another hairdresser that was absolutely marvelous with kids, and never had any issue afterwards.
It's just about how the situations are handled. The given story being a very very poor example, despite the parents having good intentions.
[0] I'm aware one of our best bets here would be a proper survey and sensitive enough telescopes/satellites actively looking for these kind of objects. And that there are some projects and programs along these lines already. It'd seem there's some more work to be done in that area though.
Thanks for the suggetion though :)
Another issue I'm thinking is that I don't know the state of the art of meteor/bolide trajectory estimation (it's apparently very poor), so you'd probably need to fire a bunch of these (or a very large one) along an (uncertain) path hoping for it to affect the impactor.
So this is just more of the same problem: how do you fire a barrage of nuclear missiles over a region to stop an impactor in such a way that you're not mistaken for a madman starting nuclear war?
Since it was a book for children, it was full of illustrations but it went into some details (or maybe I'm adding stuff into it in retrospect). The main protagonists were a boy and a girl, with a pet (maybe a dog?). I think I remember the boy having some kind of curly/fluffy hair. I remember the eyes of the characters were distinctive, but can't really recall _how_.
Any idea or pointers about finding this book? I don't remember anything about the title, author, publisher, etc.
Edit: I think you updated your comment while I replied (or maybe I just hit reply without seing the last part of your comment). I see now that you've mentioned GitHub issues, which is a kind of interface that I've seen get a better balance, but I'm not sure how it stands from a producor pov against a mailing list (decentralization is obviously lacking on them).
Now, this is an artificial divide: there's nothing in the defintion of what OCR is that means "oh it only works on scanned documents". It's just what it used to mean back in the day.
Still, if that's your kind of problem, you may look into something more along the lines of a deep convnet to do character detection and then recognize each bounding box into an alphabet.
hamming_dist = bin(a^b).count("1")
It relies on a string operations, but takes ~1 microsecond on an old i5 7200u to compare 32bit numbers. In python 3.10 we'll get int.bit_count() to get the same result without having to do these kind of things (and a ~6x speedup on the operation, but I suspect the XOR and integer handling of python might already be a large part of the running time for this calculation).If you need to go faster, you can basically pull hamming distance with just two assembly instructions: XOR and POPCNT. I haven't gone so low level for a long time, but you should be able to get into the nanosecond speed range using those.
Python 3.6.3 (v3.6.3:2c5fed8, Oct 3 2017, 18:11:49) [MSC v.1900 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.2.0 -- An enhanced Interactive Python. Type '?' for help.
In [1]: 01
File "<ipython-input-1-3351d58b1d3b>", line 1
01
^
SyntaxError: invalid token
In [2]: 0o1
Out[2]: 1
In [3]: 0o10
Out[3]: 8You can definitely do it in 20 minutes if you know how (which is also applicable to the ML version):
import cv2
import numpy as np
red_duck = cv2.imread("red_duck.png", cv2.IMREAD_GRAYSCALE)
# boilertplate etc, up to the point where you want to match your ducks on screen:
res = cv2.matchTemplate(img_screen, red_duck, cv2.TM_CCOEFF_NORMED)
positions = np.zeros_like(img_screen)
positions[res > 0.7] = 1 # we found a duck
# now do whatever you want with each position
# on real life images you may need to do some additional post-processing, on 8-bit rendered images you probably don't need toAll in all, the BFA is "good enough" most of the times. For the use cases where it isn't, you're either:
* Budget constrained and can't really afford not using BFA
* Able to (pay for and) use either a color wheel in front of your sensor, or go with prism + triple sensor.
* Bite the bullet and go with a "strange" color array. You'll probably need to work on the software side for demosaicing to get proper support and fix eventual artifacts.
[0] even more green! 20/36 photosites are green, 8 red 8 blue
[1] with W being white, meaning no color filter or "panchromatic cell". In theory this helps on dim light conditions.
Nowadays they classical algorithms are being replaced by convnets that are trained on different BFA/image pairs and can get very good results -- at the cost of placing a convnet in the middle (so much higher computational cost, which can be offloaded to a GPU/AI accelerator if available).
If you want to see what a "pixel perfect" camera gives you, there are the Sigma cameras with Foveon sensors[0] or you can check the cameras that have a sensor-shift superresolution approach (some pro Olympus and Hasselblad models have this feature). Sensor-shift SR has the problem that it works best on static scenes, because it takes several images which are then later combined on a single picture, and if there's movement between the images it may introduce a few artifacts.
[0] which do full color data for every pixel, as they use silicon depth to filter wavelenth
[0] I understand the emissions cheating was not supossed to be open, but a relatively open system allowed said student to take a peek and see what was going on.
Edit: I glimpsed at it... it's long and full of details, plus the simulations run in the archived version!