View allAll Photos Tagged Visualize

Visualize the sky through your viewfinder. Anjar Hariansyah captured this stunning starscape with the OM-D E-M5 Mark II's Live Composite mode.

 

Shot with an M.ZUIKO 12-40mm f2.8 PRO lens.

  

data: text of Hamlet

 

number of lines: 6786

 

x - line position

y - line length (in words)

A visualization of how I produce my weekly roundup of interesting stuff online.

TouchGraph of Facebook

"A-Team" edition

Lee Le, Kim Chu, Alex Dy, Joan Park, Danni Kong, Jess Romero

exterior 3d visualization

Damien Borgniet, coursework, HEAJ (Haute-École Albert Jacquard, Namur, Belgium).

 

HEAJ website :

www.infographie-sup.be/

Visualization: Studio216

Architect: Bassetti Architects

Location: Seattle

Edited the hell out of this thing, but it ended up looking cartoony...I think...

eric klotz from visualized 2014

designcorner.blinkr.net/visualcomplexity.com/?page=3

 

Visualizing The Bible

 

This visualization started as a collaboration between Christoph Romhild and Chris Harrison. As Chris explains: "Christoph, a Lutheran Pastor, first emailed me in October of 2007. He described a data set he was putting together that defined textual cross references found in the Bible. He had already done considerable work visualizing the data before contacting me. Together, we struggled to find an elegant solution to render the data, more than 63,000 cross references in total. As work progressed, it became clear that an interactive visualization would be needed to properly explore the data, where users could zoom in and prune down the information to manageable levels. However, this was less interesting to us, as several Bible-exploration programs existed that offered similar functionality (and much more). Instead we set our sights on the other end of the spectrum - something more beautiful than functional. At the same time, we wanted something that honored and revealed the complexity of the data at every level - as one leans in, smaller details should become visible".

 

This process ultimately led them to the multi-colored arc diagram shown here. The bar graph that runs along the bottom represents all of the chapters in the Bible. Books alternate in color between white and light gray. The length of each bar denotes the number of verses in the chapter. Each of the 63,779 cross references found in the Bible is depicted by a single arc - the color corresponds to the distance between the two chapters, creating a rainbow-like effect.

 

This process ultimately led them to the multi-colored arc diagram shown here. The bar graph that runs along the bottom represents all of the chapters in the Bible. Books alternate in color between white and light gray. The length of each bar denotes the number of verses in the chapter. Each of the 63,779 cross references found in the Bible is depicted by a single arc - the color corresponds to the distance between the two chapters, creating a rainbow-like effect. " class="spark_image" />

View of ground level, retail reuse of historic building in Antwerp. Design: Pompei A.D. Pencil drawing with digital rendering and montage, 2005

Plus(undocumented):

 

* + and -: Increase or decrease the intensity (brightness) of the particles; multiple presses further increase or decrease the intensity.

* A and S: Add or Subtract particles to the visualizer. You can make the visualizer as complex (or sparse) as you wish.

* R: Reset the intensity and particle count to their default values.

* E: When in nebula mode (press N), this greatly accentuates the nebula clouds, making them very easy to see. (If you’ve used the M key to change modes, you may find that the nebula clouds aren’t visible; it seems they’re only used in certain modes.)

 

via Lifehacker: lifehacker.com/5055598/itunes-8-visualizers-undocumented-...

Tour & Taxis: last installation for Revolve's 2014 photo exhibition "The Rise of Renewables"

Tour & Taxis: last installation for Revolve's 2014 photo exhibition "The Rise of Renewables"

Interactive Installation visualizing the retweet threads on Twitter following the Iranian elections of June 2009. To be shown at the IXDA2010 gallery

Tour & Taxis: last installation for Revolve's 2014 photo exhibition "The Rise of Renewables"

Web application for visualizing the US Federal Taxes.

 

The application can be explored here:

ffctn.com/a/datavizchallenge/

 

Visualization of offered filters on the Samsung 6

From Isotype Revisited project (http://www.isotyperevisited.org) at the University of Reading. Reproduced with permission.

"Twitarium" is a project on visualizing Twitter,developed by a team called Dengaku5.

 

We have extracted locational information from atweet, and displayed a dot on globe, where it is coming from.

Tour & Taxis: last installation for Revolve's 2014 photo exhibition "The Rise of Renewables"

A code-swarm visualization we did for our dacodi prototype.

This is an example of using the Radar Chart to show level of expertise in various facets of a particular skill set: SSIS Development, comparing expertise from 2011 to 2012.

How do you extract the cube root of 87?

 

One of the best ways of finding square roots for all numbers which is commonly taught, is called the Babylonian method. It resembles long division, with remainders that build at an angle under a long radical sign. To understand how it works, you can think of it in geometric terms. On each iteration a root which when squared will account for a larger and larger square area of the total area of the square is discovered. The remaining two-dimensional area to be resolved is then represented by two long rectangles, and a smaller square which border the square of the root discovered so far.

 

This image represents my attempt to reason by analogy from this geometric understanding of the square root algorithm, to understand how the cube-root algorithm must work.

 

Once I had this picture, it became obvious that the second and all subsequent steps of the cube root algorithm involves coming as close as possible to the area of 3 squat boxes, 3 long boxes and a cube.

 

Where in the square root algorithm digits are broken up into groups of 2, beginning at the decimal point, and going into each direction, they are in the cube root algorithm broken into groups of 3. Where in the square root algorithm you begin by finding the closest square that is less than or equal to a number represented by the first group of digits, in the cube root algorithm your first step is to find the cube that is equal to or less than the number represented by the first group of digits. You second step is to take that quantity, call it a and then find a single-digit quantity b, that when the following formula is applied, give an answer equal to or less than the remainder:

 

b^3 + 3( 10a^2 * b + b^2 * 10a)

 

or b cubed plus 3 times the expression 10a squared times b plus b squared times 10a.

 

b cubed is literally the cube of the digit chosen for b. This quantity is taken once in each iteration. With each iteration it becomes the most negligible quantity of them all.

 

The rest of the formula is multiplied by 3, because we are dealing with 3 identical sets of two different boxes. These represent the 3 undiscovered edge-boxes, and 3 undiscovered face-boxes of the cube discovered so far.

 

In both of these terms a is multiplied by 10, because we are doing the calculation for the sake of the next place-value digit. We are doing a calculation for one tenth the magnitude of the preceding digit. The last few digits of these numbers seem to always be zeros, except for the cube of b.

 

Both of these terms have a squared value multiplied by a value without an exponent. They describe a 3 dimensional area, one side of which is always square. They can be thought of as extruded from the face of one of the cubes. Terms with a squared in them are extruded from the faces of the discovered cube, terms with b squared in them can be thought of as extruded from the face of the cube of b, all the way to the edge of the cube of a.

 

With each iteration of the algorithm the significance of b shrinks to about a tenth of what it was in the previous iteration, and therefore terms that depend on b cubed or squared rapidly diminish in importance. After a couple of iterations it is more important to see if the digit chosen for b produces an acceptable result when multiplied against 30a^2, and move on if it isn't close. (For that matter, just look at 30a^2, and see if it is already large or small compared with the remainder.)

 

One important lesson of the cube root algorithm is that cubes are very touchy, the slightest change to a digit way off to the right can put you out of the ball-park for the answer you're trying to get. The calculations are so cumbersome and susceptible to error simply because they are so numerous when attempted by hand that you would quickly be satisfied with a gross approximation rather than five correct significant digits.

 

This method of finding a cube root will find the cube root of 87. Since 87 is not a perfect cube, unlike, say 27, 64, or 125, some other methods that can find cube roots, like prime factoring, will not work for 87.

Funky visualization of my music listening over time from MartinD at last.fm. Read his explanation to understand what it means, or just enjoy the soothing colours.

Windows media player.

Created using lastgraph.aeracode.org

 

(for some reason, even though I've been on Last.fm since 19 March 2009, LastGraph only did 2006-2009...)

Interior project and visualizations of a catalog house KM

That is exactly how my nose feels like today.

Visualization of data on liver disease from archive.ics.uci.edu/ml/datasets/Liver+Disorders . The purpleish colour are subjects who were diagnosed with liver disease, the greenish colour are healthy subjects. The points of the triangle are the relative values of blood tests for things associated with liver disease, in increasing value from left to right and from top to bottom. The intensity of the fill colour is dependent on the amount of alcohol in their system.

 

I chose this set of data to visualize because there is no apparent correlation between any two pieces of data, and I was wondering if representing every piece of data as a piece of a visual would lead to a significant pattern.

1 2 ••• 27 28 30 32 33 ••• 79 80