5,205 karma · joined February 8, 2008
http://www.etymonline.com/index.php?allowed_in_frame=0&searc...
https://renderman.pixar.com/view/denoiser
PCA would be one way to do that. This recent paper suggests that they may be decomposing the samples mostly by path type, though:
https://www.disneyresearch.com/publication/pathspace-decompo...
https://facweb.cs.byu.edu/graphics/publications/metropolisTu...
...he used to tear up her hardware, the designer's, and put the real parts into cases he'd make in his shop. Say he'd make a solid bronze case for a minidisk unit, ebony inlays, carve the control surfaces out of fossil ivory, turquoise, rock crystal. It weighed more, sure, but it turned out a lot of people liked that, like they had their music or their memory, whatever, in something that felt like it was there... And people liked touching all that stuff: metal, a smooth stone... And once you had the case, when the manufacturer brought out a new model, well, if the electronics were any better, you just pulled the old ones out and put the new ones in your case. So you still had the same object, just with better functions.
https://en.wikipedia.org/wiki/Cyclone_(programming_language)
I found this the most interesting point in the article. I would have assumed that any psychological effect of viewing trees would be largely due to their greenness, since that is their dominant visual aspect. But, assuming a largely deciduous environment, naked trees in winter would seem to have the same effect. So the effect must be stimulated by something deeper than just raw color.
https://commons.wikimedia.org/wiki/File:Lorenz_attractor_yb....
One approach would be to avoid sampling at all, by using boolean geometric operations to find the exact shapes of visible polygons within a pixel, then using their color and areas to calculate their combined contributions. I expect the calculation involved will be impractical relative to multisampling, though.
Another approach would be sample exactly once per pixel or, equivalently, render the polygons without antialiasing. Naturally, that would eliminate the show-through of hidden geometry at the expense of the accuracy of pixels around polygon edges. You might then be able to approximate the antialiased values by a post-processing filter, maybe guided by the presence of edges, although doing so will introduce its own set of artifacts.
And if you consider "one sample per pixel" to be a budget over the entire image, you could sample the polygons more densely near polygon edges and more sparsely elsewhere, using nearby samples to approximate the values of pixels with no samples.
It looks like several airports that were contracting them have since switched to another contractor, though:
https://en.wikipedia.org/wiki/Covenant_Aviation_Security#For...
However, there are a variety of exercises you can do to learn to see low-level visual input over higher-level interpretations, like copying images upside-down, following a visual edge with both eye and pencil, using a viewfinder or grid to narrow attention, measuring angles/distances between landmarks, moving attention to "negative space", etc.
You can find these kinds of exercises in most life drawing books. I particularly like "Drawing on the Right Side of the Brain", as it's structured for independent study, it has a focus on quickly producing results for absolute novices, and it has a scientific bent -- although anything it says about physical neurological structure should be taken with a grain of salt.
Drawing from a population that has spent most of their lives competing and winning may skew the results somewhat, relative to other populations...
vegetation texture -> greenish
sky texture -> blueish
everything else -> brownish
...which is not a bad set of defaults for most photos.http://www.joelonsoftware.com/articles/fog0000000069.html
(While I know they charge like this for most of their e-books, this particular example is embarrassing.)
http://www.etymonline.com/index.php?term=bug&allowed_in_fram...
At the time of Grace Hopper, the term was used in engineering contexts to refer to defects in general, quite unrelated to insects. Per your link, that's why she wrote "first actual case of a bug being found" -- it was amusing and unusual to find a bug (defect) caused by a bug (insect). If this were not the case, there would be no need to use the words "first" or "actual", or even note the event.
And it makes even less sense on this particular article, since, if you read between the lines, Adobe is acknowledging that Flash is a tainted brand and that SWF is on its way out.
And that just shows how little a mandatory backdoor policy would help: being able to read something doesn't mean you can understand it. It's always possible for someone to come up with a communication scheme that you didn't anticipate or can't interpret, and you can't legislate away that capability.
So a backdoor policy doesn't trade privacy for safety -- instead it trades privacy for a chance at safety, and pretty much just safety from careless, unprepared attackers.