Собственно собрал барахло заныканное по полочкам, рюкзаку и карманам.
на фото отсутствуют ASUS EEE PC T101MT отданный матери под печатную машинку, подаренный товарищу несколько лет назад HP iPAQ hx2110 и НЁХ, подаренный девушке несколько лет назад HTC Artemis.
>>> Просмотр (2488x2020, 1246 Kb)
Таиланде.
Китай: |
 |
 |
| Первые впечатления от настоящего Китая | Лучший трамвай на свете | Кошки и книжки госпожи Чан |
Мне важно ваше мнение о том, что я делаю и что пишу в журнале. Ваш комментарий - лучшая оценка моей работы. Давайте общаться больше!
Добавляйте меня 
в друзья, если вы ещё этого не сделали!
Кроме ЖЖ, я также пишу в 
Твиттер | 
Фейсбук | 
Инстаграм
Все фоторепортажи о путешествиях на сайте www.macos.ms
Вы можете заказать рекламу в этом журнале или разместить баннер. Подготовить блогерский фоторепортаж? Провести конкурс? Отправиться в путешествие с вашим продуктом? Легко и с удовольствием! Пишите: macos@gde.ru
Бельгия спорит с 
Голландией за звание самой велосипедной страны мира, Китай их догоняет. Велотранспорта здесь очень много, но для него инфраструктуру пока не построили. 
Китай: |
 |
|
| Олимпийское наследство Пекина | Знакомство с Гонконгом | Кошки и книжки госпожи Чан |
Мне важно ваше мнение о том, что я делаю и что пишу в журнале. Ваш комментарий - лучшая оценка моей работы. Давайте общаться больше!
Добавляйте меня в друзья, если вы ещё этого не сделали!
Кроме ЖЖ, я также пишу в Твиттер | Фейсбук | Инстаграм
Все фоторепортажи о путешествиях на сайте www.macos.ms
Вы можете заказать рекламу в этом журнале или разместить баннер. Подготовить блогерский фоторепортаж? Провести конкурс? Отправиться в путешествие с вашим продуктом? Легко и с удовольствием! Пишите: macos@gde.ru
| Piled Higher & Deeper by Jorge Cham |
www.phdcomics.com
|
|
 |
||
|
title:
"Search Results" - originally published
8/28/2013
For the latest news in PHD Comics, CLICK HERE! |
||
Есть ли у вас знакомые, которые совершенно случайно могут забыть в машине пару сотен тысяч долларов и потом не вспомнить, откуда же они взялись? Оказывается, есть на земле и такие замечательные люди!
Китайские газеты сообщают о совершенно чудесной истории, в которой следователи нашли в машине бывшего топ-менеджера HTC кучу наличности суммой примерно 262 000 $. Топ-менеджер при этом совсем не простой — по чистому и удивительному совпадению он подозревается в краже коммерческих тайн своего бывшего работодателя, то есть — компании HTC.
Карманные часы, наручные часы, а теперь – наперстные часы. Именно так выглядит эволюция хронометров в глазах команды стартапа The Ring Clock, запустившего недавно краудфандинговую кампанию, которая позволит реализовать задумку с часами, имеющими форму кольца и легко размещающимися на пальце руки.
Несмотря на эру повсеместных мобильных гаджетов, отдельные часы еще имеют достаточно большой спрос. По понятным причинам (благодаря обратному процессу «это не способ узнать время, а роскошь») особенно популярны сегодня либо дорогие, имиджевые, наручные часы, либо необычные устройства, призванные «удивить и поразить» друзей, подруг и просто прохожих. Именно в последнюю категорию попадают Ring Clock.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
#! /usr/bin/gnuplot -persist
set terminal postscript "NimbusSanL-Regu" eps color enhanced fontfile "/usr/share/texmf-texlive/fonts/type1/urw/helvetic/uhvr8a.pfb"
set output "./plots/threshold_sparsity.ps"
set key bottom right
set xtics 10
set mxtics 10
set ytics 10
set mytics 10
set yrange [60:100]
set y2range [60:100]
set xrange [10**-5:1]
set style line 1 lt 1 pt 6 ps 1.2
set style line 2 lt 1 pt 9 ps 1.4
set logscale x
set format x "10^{%L}"
set grid xtics ytics mxtics
set y2tics 5
set xlabel "Threshold value for the matrix" font "NimbusSanL-Regu,18"
set ylabel "Matrix sparsity, \% percentage" font "NimbusSanL-Regu,18"
set y2label "Output disturbance attenuation, \% percentage" font "NimbusSanL-Regu,18"
plot ".data" using 6:8 title "Percentage of sparsity of the Hessian matrix" with points linestyle 1 lc rgb "blue" axis x1y1 ,
".data" using 6:((1- $4/$2)*100) title "Output disturbance attenuation performance, \% of rejection" with points linestyle 2 lc rgb "dark-red" axis x1y2 |
set y2range [60:100] set y2tics 5set y2label "Output disturbance attenuation, \% percentage" font "NimbusSanL-Regu,18" |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 |
#! /usr/bin/gnuplot -persist
set terminal postscript "NimbusSanL-Regu" eps color enhanced fontfile "/usr/share/texmf-texlive/fonts/type1/urw/helvetic/uhvr8a.pfb"
set output "./plots/plotOutputDisturbancePlant.ps"
set lmargin 10
set rmargin 2
set grid
set bmargin 4
set style line 1 lt 1 pt 5 ps 0.3
set style line 2 lt 2 pt 7 ps 0.5
set style line 3 lt 3 pt 9 ps 0.3
set style line 4 lt 4 pt 11 ps 0.3
set style line 5 lt 5 pt 13 ps 0.3
set xrange [300:600]
set multiplot
set nokey
set size 1,0.35
set xlabel "Sampling instant"
set ylabel "Control input"
set origin 0.0,0.0
set bmargin 3
set tmargin 0
plot "./data.data" index 23 using 3 title " " with linespoints linestyle 1 lc rgb "red",
"./data.data" index 22 using 3 title " " with linespoints linestyle 2 lc rgb "dark-red",
"./data.data" index 18 using 3 title " " with linespoints linestyle 3 lc rgb "dark-green",
"./data.data" index 14 using 3 title " " with linespoints linestyle 4 lc rgb "blue",
"./data.data" index 12 using 3 title " " with linespoints linestyle 5 lc rgb "green"
set ylabel "Output disturbance"
set size 1,0.3
set origin 0.0,0.39
set xlabel " "
set bmargin 0
set tmargin 1
set nokey
plot "./data.data" index 23 using 2 title " " with linespoints linestyle 1 lc rgb "red",
"./data.data" index 22 using 2 title " " with linespoints linestyle 2 lc rgb "dark-red",
"./data.data" index 18 using 2 title " " with linespoints linestyle 3 lc rgb "dark-green",
"./data.data" index 14 using 2 title " " with linespoints linestyle 4 lc rgb "blue",
"./data.data" index 12 using 2 title " " with linespoints linestyle 5 lc rgb "green"
set size 1,0.3
set origin 0.0,0.7
set bmargin 0.1
set xlabel " "
set tmargin 1
set ylabel "Residual disturbance"
plot "./data.data" index 23 using 1 title " " with linespoints linestyle 1 lc rgb "red",
"./data.data" index 22 using 1 title " " with linespoints linestyle 2 lc rgb "dark-red",
"./data.data" index 18 using 1 title " " with linespoints linestyle 3 lc rgb "dark-green",
"./data.data" index 14 using 1 title " " with linespoints linestyle 4 lc rgb "blue",
"./data.data" index 12 using 1 title " " with linespoints linestyle 5 lc rgb "green"
set nomultiplot
|
на строках 17-22. После этих танцев с бубном строим график:set size 1,0.35 set origin 0.0,0.0 set bmargin 3 set tmargin 0
plot "./data.data" index 23 using 3 title " " with linespoints linestyle 1 lc rgb "red"
Вообще полезно продумать структуру данных для строительства графиков заранее. Например, размещать данные для разных случаев блоками (ряды данных, отбитых двумя пустыми строками), чтобы использовать возможности gnuplot и особенно инструкции index.График, расположенный в середине (строки 32-43 ), строится точно так же, только:
Ну и наконец верхний график в примере это строки 44-54, после чего выключаем multiplot и скармливаем всё gnuplot для графопостроительства. Всё легко и просто :-)set size 1,0.3 set origin 0.0,0.39
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 |
reset set term png font "Times,15" set output "broken_axes1.png" f(x)=exp(-x)*sin(500*x) #plotting function set yrange [-1:1] #The later two plot have same yrange set sample 400 set tics nomirror set tmargin at screen 0.9 #the later two plots will share this tmargin set bmargin at screen 0.1 #------------------------------------b------ set multiplot #begin multiplot mode #axes broken line set arrow 1 from screen 0.5,0.08 to screen 0.52,0.12 nohead set arrow 2 from screen 0.52,0.08 to screen 0.54,0.12 nohead set arrow 3 from screen 0.5,0.88 to screen 0.52,0.92 nohead set arrow 4 from screen 0.52,0.88 to screen 0.54,0.92 nohead #x,y axis label and title label set label 1 "Time: t(s)" at screen 0.475,0.025 set label 2 "Signal:U(mV)" at screen 0.025,0.44 rotate by 90 set label 3 center "U=exp(-t)sin(500t)" at screen 0.5,0.95 #The left part set border 1+2+4 #the right border is not plotted set lmargin at screen 0.1 #the left-part's location set rmargin at screen 0.51 set xtics 0,0.02,0.08 plot [0:0.1] f(x) w l lt 1 lw 2 notitle #unset the labels and arrows, otherwise they will be plot #for the second time unset label 1 unset label 2 unset label 3 unset arrow 1 unset arrow 2 unset arrow 3 unset arrow 4 #the right part set border 1+4+8 #the left border is not plotted set lmargin at screen 0.53 #the right-part's location set rmargin at screen 0.94 #ytics is not plotted, as the second plot will share it with the first one unset ytics set xtics 0.9,0.02,1.0 plot [0.9:1] f(x) w l lt 1 lw 2 unset multiplot |
#axes broken line set arrow 1 from screen 0.5,0.08 to screen 0.52,0.12 nohead set arrow 2 from screen 0.52,0.08 to screen 0.54,0.12 nohead set arrow 3 from screen 0.5,0.88 to screen 0.52,0.92 nohead set arrow 4 from screen 0.52,0.88 to screen 0.54,0.92 nohead |
Сложность здесь в том, чтобы угадать с полями ( set lmargin и set rmargin ). У японской девушки всё легко и просто, но если нужно построить что-то посложнее, угадывание может отнять время.
и строим левую часть:#unset the labels and arrows, otherwise they will be plot #for the second time unset label 1 unset label 2 unset label 3 unset arrow 1 unset arrow 2 unset arrow 3 unset arrow 4
Всё, выключаем мультиплот unset multiplot и вставляем эффектный график в статью.#the right part set border 1+4+8 #the left border is not plotted set lmargin at screen 0.53 #the right-part's location set rmargin at screen 0.94 #ytics is not plotted, as the second plot will share it with the first one unset ytics set xtics 0.9,0.02,1.0 plot [0.9:1] f(x) w l lt 1 lw 2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
#! /usr/bin/gnuplot -persist set terminal postscript "NimbusSanL-Regu" eps color enhanced fontfile "/usr/share/texmf-texlive/fonts/type1/urw/helvetic/uhvr8a.pfb" set output "./decoupled.ps" set lmargin 10 set rmargin 2 set grid set bmargin 4 set multiplot set xrange [0.16:0.22] set yrange [0:2000] set xtics 0.005 set grid set key top left set size 1,0.35 set xlabel "Mean computation time, milliseconds" set origin 0.0,0.0 set bmargin 3 set tmargin 0 plot ".data" using ($2*10**3):1 title "No coupling, DM with 4 actuators" with boxes fs pattern 2 lc rgb "blue" set ylabel "Frequency of occurrences (out of 4000 data points)" set size 1,0.3 set origin 0.0,0.39 set bmargin 0 set tmargin 1 set xtics 0.1 set xrange [0.2:1.7] set yrange [0:130] set xlabel "" set grid set key top left plot ".data" using ($2*10**3):1 title "No coupling, DM with 49 actuators" with boxes fs pattern 1 lc rgb "dark-red" set xtics 0.5 set size 1,0.3 set origin 0.0,0.7 set bmargin 0.1 set tmargin 1 set xrange [0:8] set xlabel "" set ylabel "" set arrow 3 from screen 0.52,0.98 to screen 0.50,0.94 nohead set arrow 4 from screen 0.57,0.98 to screen 0.55,0.94 nohead set arrow 1 from screen 0.52,0.72 to screen 0.50,0.68 nohead set arrow 2 from screen 0.57,0.72 to screen 0.55,0.68 nohead set border 1+2+4 set lmargin at screen 0.1 set rmargin at screen 0.51 set xtics 0.1 set yrange [0:80] plot [0.3:1.5] ".data" using ($2*10**3):1 title "No coupling, DM with 100 actuators" with boxes fs pattern 5 lc rgb "dark-green" unset arrow 1 unset arrow 2 unset arrow 3 unset arrow 4 set border 1+4+8 set lmargin at screen 0.56 set rmargin at screen 0.975 set nokey set xtics 0.05 set yrange [0:1000] plot [7:7.5] ".data" using ($2*10**3):1 title " " with boxes fs pattern 5 lc rgb "dark-green" set nomultiplot |
plot [7:7.5] ".data" using ($2*10**3):1
![02]](http://ic.pics.livejournal.com/dmitry_novak/28439101/135523/135523_original.jpg "02]")
Yesterday, NASA announced with some fanfare that after 36 years in space, the probe Voyager 1 has entered interstellar space.
I have two things to say here, and I want to be careful. First, this is an amazing event, and well worth celebrating. Second, a lot of people are saying Voyager 1 has left the solar system, and that’s not really accurate.
First things first. What scientists discovered is that in mid-to-late 2012, Voyager entered a new region of space. This all has to do with the solar wind, a stream of subatomic particles blown outward by the Sun. This wind expands outwards, and far beyond the orbit of Neptune it encounters the particles that exist between the stars. It pushes those aside, and loses momentum as it does so. At some point, the pressure from the wind is no longer strong enough to expand against the pressure of those external particles, and it slows to a stop. This region is called the heliopause. For years, we’ve known that Voyager is in the fuzzy volume of space where the heliopause lies, but it’s been maddeningly difficult to know if it had punched through.
The Sun then gave us a gift: a coronal mass ejection. These vast explosions of material sweep outward, and one that went off in March 2012. After more than a year of travel, this blast reached the heliopause. When it did so, it interacted with the material there, causing it to vibrate. This type of interaction is detectable by Voyager, and when scientists analyzed the data, they realized the density of the material was far higher than expected. This is just what would happen if Voyager had in fact flown through the heliopause.
So. It looks like, after traveling 19 billion kilometers (12 billion miles), one of our spacecraft has entered what can reasonably be considered interstellar space.
But does this mean it has left the solar system? Well, no. That might seem odd since I just said it’s in interstellar space, but that’s only when you look at the Sun’s influence on the particles out there.
However, there’s more to our solar system’s far-flung suburbs than errant electrons and protons. Even out there, over 120 times farther from the Sun than the Earth’s orbit, there are more substantive objects: huge, frozen chunks of ice that are essentially giant comets. The Sun is surrounded by trillions of these iceballs, a countless swarm of them called the Oort Cloud. They take thousands of years to orbit the Sun even once, but enthralled to its gravity they are.
This makes them bona fide solar system objects, and that’s why we can’t really say Voyager 1 has left the solar system. There’s still more solar system beyond it!
It’s like walking outside the front door of your house and saying you’ve left your property. While you’ve left your house, there’s still the yard all around you. You have a ways to go yet.
I make this point because the claim that Voyager has left the solar system has been made before. Many times. Many, many times. The latest was in March of this year, when some scientists announced they had detected a change in the environment Voyager was in, marking the boundary to interstellar space. That announcement was quickly contradicted by the Voyager team at JPL, including Voyager team leader Ed Stone. Full disclosure and mea culpa: I said at the time that Voyager had left the solar system, but then quickly backed off that claim when the Voyager team chimed in.
However, with these new results, Stone has given his blessing. So while Voyager still has a ways to go (many thousands of years, actually) before it actually leaves what we can think of as our solar system, I think it’s fair to say it’s now in interstellar space.
And this is an astonishing achievement for humanity. It was inevitable; we knew this would happen even before Voyager (and its twin Voyager 2) was even launched, in 1977. But still, after all these years, and so much terribly empty space traveled, this point has now been reached. Humanity is now an interstellar species.
I think the words I wrote back in March, premature as they were, finally can ring even more truly today:
[Voyager] has slipped the surly bounds of the Sun’s influence and is still moving with enough velocity to carry it out into the galaxy. Our proxy, our envoy, is heading out to the stars, where it belongs.
It’s just the first. There will be many more, some of which are already well on their way. Someday, perhaps, we may join them.
Remember the 3Doodler? Odds are plenty of you do, seeing as how the company managed to nab a staggering $2.3 million for its $30,000 Kickstarter campaign. For the minority of you who didn't participate, here's a quick refresher: the device is a 3D printing pen. It's a bit like a hot glue gun for plastic -- simple and ingenuous, it melts a single strand of ABS or PLA, allowing you to draw objects in the air, solidifying as you draw up.
The pen was still in early prototype phase when we first saw it, and now, here at IFA its co-creator Max Bogue is showing off the final shipping product (seeing as how Kickstarter funders will be getting theirs later this year). This 3Doodler actually looks pretty similar to that early unit. All the same elements are in place: a slot in the rear to feed in the plastic, the heated tip where it comes out in semi-liquid form, an exhaust fan (which is pretty loud, but should quiet down before people start to get theirs) and two buttons for fast and slow extrusion.%Gallery-slideshow81791%
Follow all of our IFA 2013 coverage by heading to our event hub!
Filed under: Peripherals
You may have heard speculation that the NSA has secretly broken the strong cryptographic systems used to keep data secret -- after all, why collect all that scrambled data if they can't unscramble it? But Bruce Schneier argues (convincingly) that this is so impossible as to be fanciful. So why have they done this? My guess is that they're counting on flaws being revealed in the cryptographic implementations in the field (or maybe they've discovered such flaws and are keeping them secret). Or they're hoping for a big breakthrough in the future (quantum computing, anyone?).
Right now the upper practical limit on brute force is somewhere under 80 bits. However, using that as a guide gives us some indication as to how good an attack has to be to break any of the modern algorithms. These days, encryption algorithms have, at a minimum, 128-bit keys. That means any NSA cryptoanalytic breakthrough has to reduce the effective key length by at least 48 bits in order to be practical.
There’s more, though. That DES attack requires an impractical 70 terabytes of known plaintext encrypted with the key we’re trying to break. Other mathematical attacks require similar amounts of data. In order to be effective in decrypting actual operational traffic, the NSA needs an attack that can be executed with the known plaintext in a common MS-Word header: much, much less.
So while the NSA certainly has symmetric cryptanalysis capabilities that we in the academic world do not, converting that into practical attacks on the sorts of data it is likely to encounter seems so impossible as to be fanciful.
How Advanced Is the NSA’s Cryptanalysis — And Can We Resist It?
(Image: A Stick Figure Guide to the Advanced Encryption Standard (AES) ) 
    
|
Jeff Moser's "A Stick Figure Guide to the Advanced Encryption Standard (AES)" beautifully presents the history, context, and workings of one of the most important pieces of math in the modern world. AES is at the core of virtually every privacy technology you use, and it holds the promise of building an NSA-proof, unsnoopable Internet.
A Stick Figure Guide to the Advanced Encryption Standard (AES)
(via O'Reilly Radar) 
|
|
