  |
はてなキーワード: Processingとは
Stack Overflow
Server Fault
Super User
Web Applications
Webmasters
Game Development
Software Engineering
WordPress Development
Geographic Information Systems
Electrical Engineering
Android Enthusiasts
Information Security
Database Administrators
Drupal Answers
User Experience
ExpressionEngine® Answers
Cryptography
Code Review
Magento
Programming Puzzles & Code Golf
more (7)
Photography
Graphic Design
Seasoned Advice (cooking)
Home Improvement
Academia
more (8)
Skeptics
Mi Yodeya (Judaism)
Travel
Christianity
English Language Learners
Arqade (gaming)
Bicycles
Role-playing Games
Motor Vehicle Maintenance & Repair
MathOverflow
Mathematics
Cross Validated (stats)
Theoretical Computer Science
Physics
Biology
Philosophy
more (3)
Meta Stack Exchange
Stack Apps
Area 51
Stack Overflow Talent
「エヴァンはこのアイデアがとても気に入ったようでした。彼にとっては良いアイデアだと思いますが、これはそのまま拡大できるビジネスモデルではありません。とても難しいビジネスです。エヴァンは広告が嫌い？ なるほど。なら、クレジットカードがどう処理されるのかわかるまで待ってみたらいいのでは？」
公式の日本語訳では以上のようになっていましたが、1,セリフの発言者が分からない、2,「彼にとっては」の「彼」が誰なのか分からない、3,「わかるまで」の動作の主体が誰なのか分からない、という問題点があるように思えます。
“Ev was so entranced by this idea,” one person told us. “That’s great for Tim, but it doesn’t scale. Also, it’s a hard business. Ev doesn’t like ads? Wait until he finds out what credit card processing is really like.”
Read more at http://www.businessinsider.co.id/inside-the-meltdown-of-evan-williams-startup-medium-2017-2/#WQQXSSY0JzwHZ1Uz.99
英語版の該当する部分はこうなっています。これを踏まえて以下のように訳してみました。
「エヴァンはこの考え方（＝寄付モデル）に魅了されていました」と、ある人物が我々に語ってくれた。「これはティム（・アーバン）に対してはとてもうまくいきましたが、スケールできません。さらにいうと、とても難しいビジネスです。でもエヴァンは広告を嫌ってるから、ですって？ まあ、クレジットカードの処理が実際にはどのようなものなのかに彼（＝エヴァン）が気づくまで、待ってみましょうか」
エヴァンもクレジットカードの実態を知れば寄付モデルを放棄するに違いないと、事情を知る第三者が匂わせているという感じでしょう。
ABA: 応用行動分析 [Applied Behavior Analysis]
AC: 従順な子どもの心 [Adapted Child]（エゴグラム）
AC/ACoD/ACoDF: アダルトチルドレン [Adult Children of Dysfunctional Family]
ACT: アクセプタンス＆コミットメント・セラピー [Acceptance and Commitment Therapy]
AD: アスペルガー障害 [Asperger disorder]
ADD: 注意欠如障害 [Attention Deficit Disorder]
ADHD: 注意欠如・多動性障害 [Attention Deficit / Hyperactivity Disorder]
AN: 神経性無食欲症 [Anorexia nervosa]
AS: アスペルガー症候群 [Asperger Syndrome]
APD: 回避性パーソナリティ障害 [Avoidant Personality Disorder] / 不安パーソナリティ障害 [Anxious Personality Disorder]
ASD: 自閉症スペクトラム障害 [Autistic Spectrum Disorder] / 急性ストレス障害 [Acute Stress Disorder]
ASPD: 反社会性パーソナリティ障害 [Antisocial Personality Disorder]
ASPS: 睡眠相前進症候群 [Advanced sleep phase syndrome]
AUD: アルコール使用障害 [Alcohol use disorder]
BD: 双極性障害 [Bipolar disorder]
BDD: 身体醜形障害 [Body dysmorphic disorder]
BN: 神経性過食症（過食症） [Bulimia nervosa]
BPD: 境界性パーソナリティ障害 [Borderline Personality Disorder]
BPRS: 簡易精神症状評価尺度 [Brief Psychiatric Rating Scale]
BT: 行動療法 [Behavioural Therapy]
CBT: 認知行動療法 [Cognitive Behavioral Therapy]
CCT: 来談者中心療法 [Client-Centered Therapy]
CDD: 小児期崩壊性障害 [Childhood Disintegrative Disorder]
CFIDS: 慢性疲労免疫不全症候群 [Chronic Fatigue and Immune Dysfunction Syndrome]
CFS: 慢性疲労症候群 [Chronic Fatigue Syndrome]
CP: 臨床心理士 [Clinical Psychologist] / 脳性麻痺 [Cerebral palsy] / 厳格な親の心 [Critical Parent]（エゴグラム）
C-PTSD: 複雑性PTSD [Complex post-traumatic stress disorder]
CT: 認知療法 [Cognitive Therapy] / コンピュータ断層撮影 [Computed Tomography]
DA: 発達年齢 [Developmental Age]
DBT: 弁証法的行動療法 [Dialectical Behavior Therapy]
DCD: 発達性協調運動障害 [Developmental coordination disorder]
DESNOS: 特定不能の極度ストレス障害 [Disorder of Extreme Stress not otherwise specified]
DD: 解離性障害 [Dissociative Disorder] / 気分変調性障害 [Dysthymic Disorder] / 発達障害 [Developmental disability]
DDNOS: 特定不能の解離性障害 [Dissociative disorders not otherwise specified]
DD-NOS: 特定不能のうつ病性障害 [Depressive disorder not otherwise specified]
DID: 解離性同一性障害 [Dissociative Identity Disorder]
DIQ: 偏差知能指数 [Deviation IQ]
DMDD: 破壊的気分調節不全障害 [Disruptive Mood Dysregulation Disorder]
DPD: 依存性パーソナリティ障害 [Dependent Personality Disorder] / 抑うつ性パーソナリティ障害 [Depressive Personality Disorder]
DSM: 精神障害の診断と統計マニュアル [Diagnostic and Statistical Manual of Mental Disorders]
DSPS: 睡眠相後退症候群 [Delayed sleep phase syndrome]
DQ: 発達指数 [Developmental Quotient]
ECT: 電気痙攣療法 [Electroconvulsive therapy]
ED: 摂食障害 [Eating Disorder] / 勃起障害 [Erectile Dysfunction]
EEG: 脳波 [Electroencephalogram]
EFT: 感情焦点化療法 [Emotionally focused therapy]
EMDR: 眼球運動による脱感作と再処理法 [Eye Movement Desensitization and Reprocessing]
EPS: 錐体外路症状 [extrapyramidal symptom]
EUPD: 情緒不安定性人格障害 [Emotionally Unstable Personality Disorder]
FAS: 胎児性アルコール症候群 [Fetal alcohol syndrome]
FASD: 胎児性アルコール・スペクトラム障害 [Fetal Alcohol Spectrum Disorders]
FC: 自由な子どもの心 [Free Child]（エゴグラム）
FD: 注意記憶 [Freedom from Distractibility]（WISC）
FM: 線維筋痛症 [Fibromyalgia]
FMS: 線維筋痛症 [Fibromyalgia Syndrome]
FT: 家族療法 [Family therapy]
FXS: 脆弱X症候群 [fragile X syndrome]
GAD: 全般性不安障害 [Generalized Anxiety Disorder]
GH: 幻聴 [Gehörshalluzination]
GID: 性同一性障害 [Gender Identity Disorder]
GLA: 全般性不安障害 [Generalized Anxiety Disorder]
HFA/HA: 高機能自閉症 [High-Functioning Autism]
HFPDD: 高機能広汎性発達障害 [High Functioning Pervasive Developmental Disorder]
HPD: 演技性パーソナリティ障害 [Histrionic Personality Disorder]
IBS: 過敏性腸症候群 [Irritable Bowel Syndrome]
ICD: 疾病及び関連保健問題の国際統計分類 [International Statistical Classification of Diseases and Related Health Problems]
ID: 知的障害 [Intellectual Disability]
IP: 患者とみなされた人 [Identified Patient]（家族療法での用語）
IQ: 知能指数 [Intelligence Quotient]
K-ABC: [Kaufman Assessment Battery for Children]
LD: 学習障害 [Learning Disabilities]
MAO: モノアミン酸化酵素 [monoamine oxidases]
MAOI: MAO阻害剤 [monoamine oxidase inhibitor]
MBCT: マインドフルネス認知療法 [Mindfulness-based cognitive therapy]
MBSR: マインドフルネス・ストレス低減法 [Mindfulness Based Stress Reduction]
MDD: 大うつ病性障害 [major depressive disorder]
MDI: 躁うつ病 [Manic Depressive Illness]
MR: 精神発達遅滞 [mental retardation]
MRI: 核磁気共鳴画像法 [magnetic resonance imaging]
MSLT: 反復睡眠潜時検査 [multiple sleep latency test]
MTBI: 軽度外傷性脳損傷 [mild Traumatic Brain Injury]
NaSSA: ノルアドレナリン作動性・特異的セロトニン作動性抗うつ薬 [Noradrenergic and specific serotonergic antidepressant]
NDRI: ノルアドレナリン・ドパミン再取り込み阻害薬 [Norepinephrine-Dopamine Reuptake Inhibitors]
NLP: 神経言語プログラミング [Neuro-Linguistic Programming]
NP: 保護的な親の心 [Nurturing Parent]（エゴグラム）
NPD: 自己愛性パーソナリティ障害 [Narcissistic Personality Disorder]
NT: 物語療法/ナラティブ・セラピー [Narrative therapy]
OCD: 強迫性障害 [Obsessive Compulsive Disorder]
OCPD: 強迫性パーソナリティ障害 [Obsessive-Compulsive personality Disorder]
OT: 作業療法 [Occupational therapy] / 光トポグラフィ [optical topography]
PANSS: 陽性・陰性症状評価尺度 [Positive and Negative Symptom Scale]
PCA: 人間中心療法/パーソンセンタードアプローチ [Person-Centered Approach:PCA]
PD: パニック障害 [Panic disorder] / パーソナリティ障害 [Personality disorder]
PDD: 広汎性発達障害 [Pervasive Developmental Disorder]
PDD-NOS: 特定不能の広汎性発達障害 [Pervasive Developmental Disorder - Not Otherwise Specified]
PDNOS: 特定不能のパーソナリティ障害 [Personality Disorder Not Otherwise Specified]
PE: 持続エクスポージャー法 [Prolonged Exposure]
PET: ポジトロン断層法 [positron emission tomography]
PIQ: 動作性IQ [performance IQ]
PMDD: 月経前不快気分障害 [Premenstrual Dysphoric Disorder]
PMS: 月経前症候群 [Premenstrual Syndrome]
PMT: 月経前緊張症 [Premenstrual Tension]
PO: 知覚統合 [perceptual organization]（WAIS / WISC）
PPD: 妄想性パーソナリティ障害 [Paranoid Personality Disorder]
PS: 処理速度 [processing speed]（WAIS / WISC）
PSD: 心身症 [Psychosomatic disease]
PTG: 外傷後成長 [Post Traumatic Growth]
PTSD: 心的外傷後ストレス障害 [Post-traumatic Stress Disorder]
REBT: 理性感情行動療法 [Rational emotive behavior therapy]
RLS: むずむず脚症候群 [restless legs syndrome]
RT: 現実療法 [Reality therapy] / 論理療法 [Rational therapy]
SA: システムズ・アプローチ [Systems Aproach]
SAD: 社会不安障害 [Social Anxiety Disorder] / 季節性情動障害 [Seasonal Affective Disorder]
SARI: トリアゾロピリジン系抗うつ薬 [Serotonin antagonist and reuptake inhibitor]
SAS: 睡眠時無呼吸症候群 [Sleep apnea syndrome]
SD: 身体表現性障害 [Somatoform Disorder]
SDA: セロトニン・ドパミン拮抗薬 [Serotonin-Dopamine Antagonist]
SLD: 限局性学習症/限局性学習障害 [Specific learning disorder]
SLTA: 標準失語症検査 [Standard Language Test of Aphasia]
SMIT: 自己洞察瞑想療法 [Self Insight Meditation Technology/Therapy]
SNRI: セロトニン・ノルアドレナリン再取り込み阻害薬 [Serotonin and Norepinephrine Reuptake Inhibitors]
SPECT: 単一光子放射断層撮影 [Single photon emission computed tomography]
SPD: スキゾイドパーソナリティ障害 [Schizoid Personality Disorder] / サディスティックパーソナリティ障害 [Sadistic Personality Disorder]
SRS: 性別適合手術 [Sex Reassignment Surgery]
SSRE: 選択的セロトニン再取り込み促進薬 [Selective serotonin reuptake enhancer]
SSRI: 選択的セロトニン再取り込阻害薬 [Selective serotonin reuptake inhibitors]
SST: ソーシャルスキルトレーニング/社会生活技能訓練 [Social Skills Training]
TA: 交流分析 [Transactional Analysis]
TBI: 外傷性脳損傷 [Traumatic brain injury]
TCA: 三環系抗うつ薬 [Tricyclic Antidepressants]
TS: トゥレット症候群 [Tourette Syndrome]
VC: 言語理解 [verbal comprehension]（WAIS / WISC）
WAIS: ウェクスラー成人知能検査 [Wechsler Adult Intelligence Scale]
WISC: WISC知能検査 [Wechsler Intelligence Scale for Children]
WPPSI: WPPSI知能診断検査 [Wechsler Preschool and Primary Scale of Intelligence]
WM: 作動記憶 [working memory]（WAIS）
Auditory Processing Disorderかもしれないよ。耳自体は正常なんだけれど、その信号を脳でうまく処理できない。
なんか偉そうに書いてみた。
SFCには頭がおかしいプログラミング言語使いがたくさんいる。特に研究室に入ると、バイトでバリバリ書いている人間や、研究や趣味でライブラリを量産する人間に出会うこともあるだろう。彼らに惑わされてはいけない。最初は彼らの言っていることは一つも理解できないだろう、理解する必要は無い。彼らはプロダクションで安定するかどうかという縛りから自由だ。流行り廃りに敏感で、昨日言ってることと今日言ってることが違う。
これは実際に手を動かして使ってみて好感触かどうかささっと確かめられる人間だからできることで、プログラミングできない人がこれについていこうとしたら間違いなくプログラミングが嫌いになる。
こういう言葉に惑わされるな、コードを書くための勉強をするな、コードを書け。
できる人は概ね、できない人の気持ちがわからない。受動的になるな。積極的に書け。
「プログラミングなんて特殊技能で、少なくとも教養じゃないでしょ..」という認識が横行している今だけのチャンスとも言える。
webプログラミングができると「技術的には簡単だがアイデア一発で作ってみた」もので、ほんのちょっとだけ有名になれる可能性がある。論文を書いて学会に投稿したりニュースになったりするよりも、よっぽどお手軽に(一部での)社会的ステータスを高めることができる(かもしれない)。
↓ こういうのでいい（失礼だが）。
こう言っている人間を見て何を思うだろうか。
「いや少しずつでいいから今やれよ」とか「英語できたらもっと世界ひろがるのに..」とか「大学生なのにそれで恥ずかしくないの」とか思うかもしれない。
知らない世界を知らずにいることは大いなる機会損失である。プログラミングに金はいらない。金はないけど時間はある、時間を大量投入できる最後の機会、大学生である内に学んでおいた方が望ましい。
基本的なスタンスとして、講義ではプログラミングを教えてはくれない。講義に期待するな。プログラミングに限らず、全ての講義は自習への足がかりであり、興味のとっかかりである。実際に意思を持って積極的にコードを書かない限りプログラミングのことは好きになれない。自分で考えながら手を動かしてコードを書かなければ覚えないし、初学者が配られたプリントを写経しても血肉にならない。
「今日から俺は！」という感じでプログラミング講義を受けると爆死は約束された未来である。「腕試ししよう」「これなら楽勝じゃろ」という意気込みで講義を受けると、意外に学ぶことが多い。完全な初学者の域は脱しておいた方が講義は有効的に活用できる。少なくとも、最初の2週間をインストールと環境構築のみで終わらせるスジの悪い講義を取得してはいけない。
また、講師によってはJavaScriptのことをJavaと呼称したり、JavaScriptはLispに比べて読解が平易であるためハッキングを受けやすいと言ったことを平然と言ってのける。選別にあたっては「講義名」と「講師名」を明言した上で「先輩に聞く」「Twitterを活用する」等の手段をとるべきである。十二分に注意されたし。
道具を選ばないのはプロだけである。初学者は多少高くても自分をサポートしてくれる良いマシンを入手すべきである。1行のコードを書くだけでも恐ろしい手数が必要なアーキテクチャを選択するのは愚行だ。
モデルは何でもいい、無理して上位機種を買う必要は無い。お金が余ってるならMacBookProを買えばいいし、勿論一番安いMacBookAirでも全く問題ない。特にweb系のコードを書く際、インターネットで検索して出てくる記事はだいたい「OSがUNIX系であること」を前提としたサンプルである。これをWindowsの開発環境に読み替えるのは、初学者に取ってつらいだろう。
また、Macならばパフォーマンスは多少犠牲になるがwindowsも起動できる。どうしても光学機器が必要になればCNSコンサルタントで外部接続式の光学機器を貸し出してくれる。Macが気に入らなくてもどうせ研究が射程に入る3年生に上がったぐらいのタイミングでPCを買い替えるだろう。バイトして稼いだ金で「俺の考えた最強のマシン」に買い替えればいい。それまではMacを使え。
OSに固有の使い方なんて学ぶ価値はない、覚える価値も無い、操作時間が短縮されるだけだ。「普通の会社はWindowsなんでしょう？」というくだらない理由でWindowsPCを選択肢の第一候補にするな。Windowsを買うなら積極的選択としてWindowsを買え。
SFCにおいて、PCは毎日抱えて通学し、毎日開いて講義を受け、苦楽を共にする相棒だ。消極的に選択するな。
SFCには「共同購入PC」という制度がある、これを利用してはいけない。
もし要件が変更され、Macがラインナップに入れば積極的に利用するべきである。
条件を示す。
見た目に変化が無いと楽しくないだろう、こんなのを実行しても何も楽しくないはずだ。
#include <stdio.h> int main() { int a; a = 1 + 1; printf("%d", a); }
マイナーな言語を選択してはいけない。「ライトウェイト言語」と呼ばれるくくりから選択肢するのがいいだろう、以下のようなものがある。
中でもjavascriptとrubyは推薦できる、SFCでも書いている人間は多い。
phpとperlはおすすめできない。ドキュメントは多いが、不慣れであればロジック以外に割かれる労力が非常に多い。pythonは日本語のドキュメントが少ないため最初はつらいだろう。
最初にjavascriptをやるのは理に適っている。index.htmlというファイルを作り、scriptタグの中にコードを書き、ブラウザでindex.htmlを開けばもう実行されている。web上のドキュメント量も豊富だ。
rubyも推薦できるが、少なくとも「自分でHTTPサーバを立てる」という言葉にピンと来るようになってから使い始めた方がいいだろう。きっと何をしていいかわからないはずだ。
他にもProcessing(http://processing.org)などが推薦できる。ダウンロードに時間がかかるだけでインストール作業は必要ない。こちらに関しては旧プロダクト名である「proce55ing」をキーワードに検索すると記事が引っかかりやすいという暗黙のルールがあった、今はどうだか知らない。
最近ではnode.jsの採用事例も増えてきた（他に比べれば圧倒的少数、増加傾向にあるという意味）。クライアントでもサーバでも活躍できるjsは学習コストパフォーマンスが高いと思われる。
書ける言語は一つにしぼってはいけない。なるべくたくさんの言語を使ってみよ。ブログ記事を読みあさり、「その言語は何が得意なのか」調査しろ。不得意なことをその言語にやらせるな。
下記のような上達ストーリーが考えられる。
例えばpythonは音響処理や数学計算が得意だったりする。そういった特徴を徐々につかみながら書ける言語の種類を増やし、好きな言語を見つけて好きな言語のことをもっと好きになればいい。
自分が好きな言語のことを胸を張って自慢できるようになったなら、あなたは既に初学者ではない。
人に聞くとvimやemacsを推薦されるかもしれない。もしそれを使ったことが無いなら、あるいは「プラグインの導入方法がわからない」なら、やめろ。Terminalを開かなくても書けるGUIアプリのテキストエディタを使え。
具体的にはSublimeText(http://www.sublimetext.com/3)を使うのがよい、無料である。
ライセンスが必要だが、起動時に「買ってね！」というダイアログが出続けるだけで無料で使用し続けられる。信頼できるエディタだと思ったら買えばいい。
SublimeText3にPackageControlというものを導入すると、標準で備わっていない機能を拡張できるようになる。こちらのブログ(http://p.tl/Ev7b)の「インストール手順」セクションのみを実行する。たとえば「Jadeという言語を、文法に従って色付けしてほしい(SyntaxColoring)が、その機能が無い」という時に、「Jade用プラグイン」をSublimeText内で検索し、インストールすることができる。
もし使い方がわからないければ、回りにいる「プログラミングができる優しい人」に上の記事を見せ「インストールしてくれませんか？」と頼んでみろ。きっと戸惑いながらも正しい操作をしてくれるだろう、一挙手一投足を見逃さず学べ。
エロ画像を集め続けるツールが欲しいとする。どうやったらいいか考える。クライアントjsだけでは限界が来る。rubyなど別の言語を試すステップを踏む。
http://www.slideshare.net/shokai/ss-26387303
プログラマ同士じゃないと伝わりにくい用語が頻発すると思う。逐一人に聞いていてはラチが開かない。人に聞くな、適当に読み飛ばせ。
ブログ記事は本ではない、それを読解しなければならない理由はない。適当にはてブでもつけといて、次の記事を読め。たくさん読めば共通項が見えるだろう、コードが書けるようになるに従い読めるようになるだろう。
みんなが息をするようにコード書いてさ、みんなでしあわせになろうよ。
「スタートアップ系」と言った舌の根が乾かないうちにIT系に限定し始めるのもどうかと思うが。
まぁIT系エンジニアの男を落としたいなら、前も似たような話があったけど、簡単だよ。
これで若手エンジニアから起業家、大企業でそこそこのポジションについてるオッサンまで入れ食い間違いなしなので後は好きに選べば良い。
うまいこと釣り上げてもナイショにしてしばらくtwitterは続けること。嫉妬でキモい行動に出る奴がいる可能性があるからね。
右クリック禁止は不便だな
アップロード時にプロフィールで設定した透かしを埋め込むようにしたら著作権の保護と利便性が両立できると思う
http://www.script-tutorials.com/watermark-processing-on-images-using-php-and-gd/
Watermark processing on images using PHP and GD
If users want to prolong battery the efficient use of the time, in addition to the quality of the charger to have the guarantee, the right skills and charging is essential, because of low quality charger or wrong charging methods would affect battery time and life cycle, the following is about to charge skills:
1. The battery before they leave the factory, manufacturers were activated processing, and the charge, so the battery are more electricity, my friends say battery charging adjustment period in accordance with the time, standby still seriously insufficient, assuming that the battery is really quality goods battery of words, this kind of circumstance should extend the setting and then 3 ~ 5 times fully charge and discharge.
2. If new phone is lithium ion battery, so before 3 ~ 5 times charging commonly known as adjustment period, should be charged more than 14 hours, in order to ensure that the fully activate lithium ion activity. The lithium ion battery no memory effects, but have very strong sui sex, should give full activated PANASONIC CGR-D220 Battery, to guarantee the use of after can reach the right performance.
3. Some automation intelligent quick charger when instructions lights change, said only full of 90%. The charger will automatically change with slow charge will batteries. Best will use after batteries, otherwise, it will shorten use time.
4. Before charging and discharging lithium battery does not need special, but will not discharge damage to the battery. As far as possible when charging at the slow ChongChongDian, reduce the way quick charge; Time don't more than 24 hours. The battery after three to five times fully recharge cycles of internal after chemical will be all "activate" to achieve the best use effect.
5. Please use the original or the reputation of the good brand charger, li-ion battery to lithium battery charger with special, and follow the instructions, otherwise, it will damage to the battery, and even dangerous.
6. Have many users often in charge still leave her cell phone, actually such will be very easy to PANASONIC CGA-S101E/1B Battery damage the service life of the mobile phone, because in charge of the process, the circuit boards of mobile phone can calorific, if this time more exotic phone, may produce instant backflow current, internal parts to mobile phone damage.
7. The battery life depends on the number repeatedly charging and discharging, so should try to avoid more battery electric charge when, this will shorten battery life. Cell phone time more than 7 days, supposed to completely discharge the cell phone battery, enough electricity before use.
8. The cell phone battery have self-discharge, need not when the nimh batteries will press the residual capacity every day, about 1% of the discharge, lithium battery every day to 0.2% ~ 0.3% discharge. In for the battery, try to use the special socket, don't will the home appliance such as the Shared and the TV charger socket.
9. Though the phones in the network coverage area, but in the cell phone charge, cell phones have been unable to accept and call. At this time, can use of the mobile phone is not transfer function, will be transferred to the mobile phone side of fixed telephone in order to prevent calls lost, this kind of method for mobile phone is not in the network coverage of the area or weak signal and temporarily unable to the applicable also.
10. Don't will be exposed to high temperature or cold PANASONIC DMW-BCG10E Battery , as the dog, should not put the phone on the car, and the sun blazed through the; Or get air conditioning room, in air conditioning to be blown continuously place. When charging, the battery is a little heat is normal, but can't let it what the high temperature "suffer". In order to avoid the happening of this kind of circumstance, had better be in charge at room temperature, and don't cover anything on the mobile phone.
11. Nickel cadmium (N iCd) before the battery must ensure that the batteries are no electricity, recharging the battery must ensure that sufficient electricity after.
12. If the cell phone battery placed too long and not use, the best maintenance department to cell phones to the application for a live processing, also can use a constant dc voltage is the voltage adjustment for 5 ~ 6 V, current 500 ~ 600 mA reverse connect battery. Note that a touch namely release, the most repeated three times can, through such treatment after another, with the original adapter to "adaptation" charge.
13. Charge is not as long as possible, to no protection circuit batteries that should stop after charging, or the battery will with fever or overheating impact performance.
14. Lithium ion battery must choose special charger, otherwise may not reach the saturated state, affect their performance. Charging completes, should avoid to place in charger on more than 12 hours or more, long-term need not when should make a battery and cell phone separation.
Digital cameras are made in a wide range of sizes, prices and capabilities. The majority are camera phones, operated as a mobile application through the cellphone menu. Professional photographers and many amateurs use larger, more expensive digital single-lens reflex cameras (DSLR) for their greater versatility. Between these extremes lie digital compact cameras and bridge digital cameras that "bridge" the gap between amateur and professional cameras. Specialized cameras including multispectral imaging equipment and astrographs continue to serve the scientific, military, medical and other special purposes for which digital photography was invented.
Subcompact with lens assembly retracted
Compact cameras are designed to be tiny and portable and are particularly suitable for casual and "snapshot" uses. Hence, they are also called point-and-shoot cameras. The smallest, generally less than 20 mm thick, are described as subcompacts or "ultra-compacts" and some are nearly credit card size.[2]
Most, apart from ruggedized or water-resistant models, incorporate a retractable lens assembly allowing a thin camera to have a moderately long focal length and thus fully exploit an image sensor larger than that on a camera phone, and a mechanized lens cap to cover the lens when retracted. The retracted and capped lens is protected from keys, coins and other hard objects, thus making it a thin, pocketable package. Subcompacts commonly have one lug and a short wrist strap which aids extraction from a pocket, while thicker compacts may have two lugs for attaching a neck strap.
Compact cameras are usually designed to be easy to use, sacrificing advanced features and picture quality for compactness and simplicity; images can usually only be stored using lossy compression (JPEG). Most have a built-in flash usually of low power, sufficient for nearby subjects. Live preview is almost always used to frame the photo. Most have limited motion picture capability. Compacts often have macro capability and zoom lenses but the zoom range is usually less than for bridge and DSLR cameras. Generally a contrast-detect autofocus system, using the image data from the live preview feed of the main imager, focuses the lens.
Typically, these cameras incorporate a nearly silent leaf shutter into their lenses.
For lower cost and smaller size, these cameras typically use image sensors with a diagonal of approximately 6 mm, corresponding to a crop factor around 6. This gives them weaker low-light performance, greater depth of field, generally closer focusing ability, and smaller components than cameras using larger sensors.
Starting in 2011, some compact digital cameras can take 3D still photos. These 3D compact stereo cameras can capture 3D panoramic photos for play back on a 3D TV.[3] Some of these are rugged and waterproof, and some have GPS, compass, barometer and altimeter. [4]
Main article: Bridge camera
Bridge are higher-end digital cameras that physically and ergonomically resemble DSLRs and share with them some advanced features, but share with compacts the use of a fixed lens and a small sensor. Like compacts, most use live preview to frame the image. Their autofocus uses the same contrast-detect mechanism, but many bridge cameras have a manual focus mode, in some cases using a separate focus ring, for greater control. They originally "bridged" the gap between affordable point-and-shoot cameras and the then unaffordable earlier digital SLRs.
Due to the combination of big physical size but a small sensor, many of these cameras have very highly specified lenses with large zoom range and fast aperture, partially compensating for the inability to change lenses. On some, the lens qualifies as superzoom. To compensate for the lesser sensitivity of their small sensors, these cameras almost always include an image stabilization system to enable longer handheld exposures.
These cameras are sometimes marketed as and confused with digital SLR cameras since the appearance is similar. Bridge cameras lack the reflex viewing system of DSLRs, are usually fitted with fixed (non-interchangeable) lenses (although some have a lens thread to attach accessory wide-angle or telephoto converters), and can usually take movies with sound. The scene is composed by viewing either the liquid crystal display or the electronic viewfinder (EVF). Most have a longer shutter lag than a true dSLR, but they are capable of good image quality (with sufficient light) while being more compact and lighter than DSLRs. High-end models of this type have comparable resolutions to low and mid-range DSLRs. Many of these cameras can store images in a Raw image format, or processed and JPEG compressed, or both. The majority have a built-in flash similar to those found in DSLRs.
In bright sun, the quality difference between a good compact camera and a digital SLR is minimal but bridgecams are more portable, cost less and have a similar zoom ability to dSLR. Thus a Bridge camera may better suit outdoor daytime activities, except when seeking professional-quality photos.[5]
In low light conditions and/or at ISO equivalents above 800, most bridge cameras (or megazooms) lack in image quality when compared to even entry level DSLRs. However, they do have one major advantage: their much larger depth of field due to the small sensor as compared to a DSLR, allowing larger apertures with shorter exposure times.
A 3D Photo Mode was introduced in 2011, whereby the camera automatically takes a second image from a slightly different perspective and provides a standard .MPO file for stereo display. [6]
[edit]Mirrorless interchangeable-lens camera
Main article: Mirrorless interchangeable-lens camera
In late 2008, a new type of camera emerged, combining the larger sensors and interchangeable lenses of DSLRs with the live-preview viewing system of compact cameras, either through an electronic viewfinder or on the rear LCD. These are simpler and more compact than DSLRs due to the removal of the mirror box, and typically emulate the handling and ergonomics of either DSLRs or compacts. The system is used by Micro Four Thirds, borrowing components from the Four Thirds DSLR system.
[edit]Digital single lens reflex cameras
Cutaway of an Olympus E-30 DSLR
Main article: Digital single-lens reflex camera
Digital single-lens reflex cameras (DSLRs) are digital cameras based on film single-lens reflex cameras (SLRs). They take their name from their unique viewing system, in which a mirror reflects light from the lens through a separate optical viewfinder. At the moment of exposure the mirror flips out of the way, making a distinctive "clack" sound and allowing light to fall on the imager.
Since no light reaches the imager during framing, autofocus is accomplished using specialized sensors in the mirror box itself. Most 21st century DSLRs also have a "live view" mode that emulates the live preview system of compact cameras, when selected.
These cameras have much larger sensors than the other types, typically 18 mm to 36 mm on the diagonal (crop factor 2, 1.6, or 1). This gives them superior low-light performance, less depth of field at a given aperture, and a larger size.
They make use of interchangeable lenses; each major DSLR manufacturer also sells a line of lenses specifically intended to be used on their cameras. This allows the user to select a lens designed for the application at hand: wide-angle, telephoto, low-light, etc. So each lens does not require its own shutter, DSLRs use a focal-plane shutter in front of the imager, behind the mirror.
Main article: Rangefinder camera#Digital rangefinder
A rangefinder is a user-operated optical mechanism to measure subject distance once widely used on film cameras. Most digital cameras measure subject distance automatically using electro-optical techniques, but it is not customary to say that they have a rangefinder.
[edit]Line-scan camera systems
A line-scan camera is a camera device containing a line-scan image sensor chip, and a focusing mechanism. These cameras are almost solely used in industrial settings to capture an image of a constant stream of moving material. Unlike video cameras, line-scan cameras use a single row of pixel sensors, instead of a matrix of them. Data coming from the line-scan camera has a frequency, where the camera scans a line, waits, and repeats. The data coming from the line-scan camera is commonly processed by a computer, to collect the one-dimensional line data and to create a two-dimensional image. The collected two-dimensional image data is then processed by image-processing methods for industrial purposes.
Further information: Rotating line camera
Many devices include digital cameras built into or integrated into them. For example, mobile phones often include digital cameras; those that do are known as camera phones. Other small electronic devices (especially those used for communication) such as PDAs, laptops and BlackBerry devices often contain an integral digital camera, and most 21st century camcorders can also make still pictures.
Due to the limited storage capacity and general emphasis on convenience rather than image quality, almost all these integrated or converged devices store images in the lossy but compact JPEG file format.
Mobile phones incorporating digital cameras were introduced in Japan in 2001 by J-Phone. In 2003 camera phones outsold stand-alone digital cameras, and in 2006 they outsold all film-based cameras and digital cameras combined. These camera phones reached a billion devices sold in only five years, and by 2007 more than half of the installed base of all mobile phones were camera phones. Sales of separate cameras peaked in 2008. [7]
Integrated cameras tend to be at the very lowest end of the scale of digital cameras in technical specifications, such as resolution, optical quality, and ability to use accessories. With rapid development, however, the gap between mainstream compact digital cameras and camera phones is closing, and high-end camera phones are competitive with low-end stand-alone digital cameras of the same generation.
A Canon WP-1 waterproof 35 mm film camera
Waterproof digital cameras are digital cameras that can make pictures underwater. Waterproof housings have long been made but they cost almost as the cameras. Many waterproof digital cameras are shockproof and resistant to low temperatures; one of them is Canon PowerShot D10, one of the first underwater digital cameras.
These cameras become very popular during the holiday season, because many people want to save the best moments from their holidays at the seaside. Waterproof watches and mobile phones were produced earlier. Most makers of digital cameras also produce waterproof ones and every year they launch at least one new model, for example Sony, Olympus, Canon, Fuji.
Healthways Mako Shark, an early waterproof camera,[8] was launched in 1958 and cost around 25 dollars. It was a huge camera and pictures were black and white.
___________________________
http://www.gobatteryonline.com/canon-nb-9l-digital-camera-battery-gose.html
http://www.gobatteryonline.com/canon-lp-e5-digital-camera-battery-gose.html
http://www.gobatteryonline.com/canon-powershot-sd500-battery-charger-gose.html
やー。面倒でした。
古い情報だと Outlook Express を経由しろと書いてあるので、後継であるらしいWindows Live Mail を経由して（Windows Live Mail からエクスポートする方法で）
Outlook に移行したのだが、どういうわけか宛名が文字列として移行されてしまい、xxx@example.com というメールアドレスの移行ができなかったんです。
で eml → msg もしくは pst 形式への変換ソフトを探すのですが、無料のものが見つからなくてあんまり情報もありませんでした。が、ありましたよ！お兄さん。
====
MAPI data collection and parsing tool. Supports property tag lookup, error translation, smart view processing, rule tables, ACL tables, contents tables, and MAPI<->MIME conversion. MrMAPI currently knows: 3916 property tags 801 dispids 35 types 58 guids 148 errors 27 smart view parsers Usage: MrMAPI -? MrMAPI [-Search] [-Dispids] [-Number] [-Type <type>] <property number>|<property name> MrMAPI -Guids MrMAPI -Error <error> MrMAPI -ParserType <type> -Input <input file> [-Binary] [-Output <output file>] MrMAPI -Flag <flag value> [-Dispids] [-Number] <property number>|<property name> MrMAPI -Rules [-Profile <profile>] [-Folder <folder>] MrMAPI -Acl [-Profile <profile>] [-Folder <folder>] MrMAPI [-Contents | -HiddenContents] [-Profile <profile>] [-Folder <folder>] [-Output <output directory>] [-Subject <subject>] [-MessageClass <message class>] [-MSG] [-List] MrMAPI -ChildFolders [-Profile <profile>] [-Folder <folder>] MrMAPI -XML -Input <path to input file> -Output <path to output file> MrMAPI -FID [fid] [-MID [mid]] [-Profile <profile>] MrMAPI -MAPI | -MIME -Input <path to input file> -Output <path to output file> [-CCSFFlags <conversion flags>] [-RFC822] [-Wrap <Decimal number of characters>] [-Encoding <Decimal number indicating encoding>] [-AddressBook] [-Unicode] [-Charset CodePage CharSetType CharSetApplyType] All switches may be shortened if the intended switch is unambiguous. For example, -T may be used instead of -Type. Help: -? Display expanded help. Property Tag Lookup: -S (or -Search) Perform substring search. With no parameters prints all known properties. -D (or -Dispids) Search dispids. -N (or -Number) Number is in decimal. Ignored for non-numbers. -T (or -Type) Print information on specified type. With no parameters prints list of known types. When combined with -S, restrict output to given type. -G (or -Guids) Display list of known guids. Flag Lookup: -Fl (or -Flag) Look up flags for specified property. May be combined with -D and -N switches, but all flag values must be in hex. Error Parsing: -E (or -Error) Map an error code to its name and vice versa. May be combined with -S and -N switches. Smart View Parsing: -P (or -ParserType) Parser type (number). See list below for supported parsers. -B (or -Binary) Input file is binary. Default is hex encoded text. Rules Table: -R (or -Rules) Output rules table. Profile optional. ACL Table: -A (or -Acl) Output ACL table. Profile optional. Contents Table: -C (or -Contents) Output contents table. May be combined with -H. Profile optional. -H (or -HiddenContents) Output associated contents table. May be combined with -C. Profile optional -Su (or -Subject) Subject of messages to output. -Me (or -MessageClass) Message class of messages to output. -Ms (or -MSG) Output as .MSG instead of XML. -L (or -List) List details to screen and do not output files. Child Folders: -Chi (or -ChildFolders) Display child folders of selected folder. MSG File Properties -X (or -XML) Output properties of an MSG file as XML. MID/FID Lookup -Fi (or -FID) Folder ID (FID) to search for. If -FID is specified without a FID, search/display all folders -Mid (or -MID) Message ID (MID) to search for. If -MID is specified without a MID, display all messages in folders specified by the FID parameter. MAPI <-> MIME Conversion: -Ma (or -MAPI) Convert an EML file to MAPI format (MSG file). -Mi (or -MIME) Convert an MSG file to MIME format (EML file). -I (or -Input) Indicates the input file for conversion, either a MIME-formatted EML file or an MSG file. -O (or -Output) Indicates the output file for the convertion. -Cc (or -CCSFFlags) Indicates specific flags to pass to the converter. Available values (these may be OR'ed together): MIME -> MAPI: CCSF_SMTP: 0x02 CCSF_INCLUDE_BCC: 0x20 CCSF_USE_RTF: 0x80 MAPI -> MIME: CCSF_NOHEADERS: 0x0004 CCSF_USE_TNEF: 0x0010 CCSF_8BITHEADERS: 0x0040 CCSF_PLAIN_TEXT_ONLY: 0x1000 CCSF_NO_MSGID: 0x4000 CCSF_EMBEDDED_MESSAGE: 0x8000 -Rf (or -RFC822) (MAPI->MIME only) Indicates the EML should be generated in RFC822 format. If not present, RFC1521 is used instead. -W (or -Wrap) (MAPI->MIME only) Indicates the maximum number of characters in each line in the generated EML. Default value is 74. A value of 0 indicates no wrapping. -En (or -Encoding) (MAPI->MIME only) Indicates the encoding type to use. Supported values are: 1 - Base64 2 - UUENCODE 3 - Quoted-Printable 4 - 7bit (DEFAULT) 5 - 8bit -Ad (or -AddressBook) Pass MAPI Address Book into converter. Profile optional. -U (or -Unicode) (MIME->MAPI only) The resulting MSG file should be unicode. -Ch (or -Charset) (MIME->MAPI only) Character set - three required parameters: CodePage - common values (others supported) 1252 - CP_USASCII - Indicates the USASCII character set, Windows code page 1252 1200 - CP_UNICODE - Indicates the Unicode character set, Windows code page 1200 50932 - CP_JAUTODETECT - Indicates Japanese auto-detect (50932) 50949 - CP_KAUTODETECT - Indicates Korean auto-detect (50949) 50221 - CP_ISO2022JPESC - Indicates the Internet character set ISO-2022-JP-ESC 50222 - CP_ISO2022JPSIO - Indicates the Internet character set ISO-2022-JP-SIO CharSetType - supported values (see CHARSETTYPE) 0 - CHARSET_BODY 1 - CHARSET_HEADER 2 - CHARSET_WEB CharSetApplyType - supported values (see CSETAPPLYTYPE) 0 - CSET_APPLY_UNTAGGED 1 - CSET_APPLY_ALL 2 - CSET_APPLY_TAG_ALL Universal Options: -I (or -Input) Input file. -O (or -Output) Output file or directory. -F (or -Folder) Folder to scan. Default is Inbox. See list below for supported folders. Folders may also be specified by path: "Top of Information Store\Calendar" Path may be preceeded by entry IDs for special folders using @ notation: "@PR_IPM_SUBTREE_ENTRYID\Calendar" MrMAPI's special folder constants may also be used: "@12\Calendar" "@1" -Pr (or -Profile) Profile for MAPILogonEx. -M (or -MoreProperties) More properties. Tries harder to get stream properties. May take longer. -No (or -NoAddins) No Addins. Don't load any add-ins. -On (or -Online) Online mode. Bypass cached mode. -V (or -Verbose) Verbose. Turn on all debug output. Smart View Parsers: 1 Additional Ren Entry IDs Ex 2 Appointment Recurrence Pattern 3 Conversation Index 4 Entry Id 5 Entry List 6 Extended Folder Flags 7 Extended Rule Condition 8 Flat Entry List 9 Folder User Fields Stream 10 Global Object Id 11 Property 12 Property Definition Stream 13 Recipient Row Stream 14 Recurrence Pattern 15 Report Tag 16 Restriction 17 Rule Condition 18 Search Folder Definition 19 Security Descriptor 20 SID 21 Task Assigners 22 Time Zone 23 Time Zone Definition 24 Web View Persistence Object Stream 25 Nickname Cache 26 Encode Entry ID 27 Decode Entry ID Folders: 1 Calendar 2 Contacts 3 Journal 4 Notes 5 Tasks 6 Reminders 7 Drafts 8 Sent Items 9 Outbox 10 Deleted Items 11 Finder 12 IPM_SUBTREE 13 Inbox 14 Local Freebusy 15 Conflicts 16 Sync Issues 17 Local Failures 18 Server Failures 19 Junk E-mail Examples: MrMAPI PR_DISPLAY_NAME MrMAPI 0x3001001e MrMAPI 3001001e MrMAPI 3001 MrMAPI -n 12289 MrMAPI -t PT_LONG MrMAPI -t 3102 MrMAPI -t MrMAPI -s display MrMAPI -s display -t PT_LONG MrMAPI -t 102 -s display MrMAPI -d dispidReminderTime MrMAPI -d 0x8502 MrMAPI -d -s reminder MrMAPI -d -n 34050 MrMAPI -p 17 -i webview.txt -o parsed.txt
CPU（central processing unit）パソコンのいちばんだいじなところ
Intel（会社）のX86（win）と IBM（会社）のPowerPC（Mac）は動かすための命令がぜんぜんちがう
でもいろいろあってつかえるようになった。
AppleがPowerPCをすてた。←マカーにとっては大事（MacOSのあたらしいver.はPowerPCはもうでなくて、Intel版しかでなくなるから。）（いまいちばんあたらしいのが10.6（スノウレパードってやつ＝Intel版しかない）も iBookはPowerPCで、最近のやつはIntelだから入らない。）
一因としてIntelは性能やコスパがいいCPU。PowerPCは
そうでもなくなってきた。そしてIntelはノートPC向きでもあった。
でもどこの会社もIntel X86をすてるかもしれない（微妙なとこ）。
それでARMに移行するかもしれない。
（ARMはもともと省電力がうりで性能がうりのCPUではない。）
演算装置（processing unit）がいろいろ計算している
パソコンだけではなく業務用の大きなコンピュータとかつくっている。
（業務用の大きいコンピュータと、パソコンの基本的なしくみは一緒。）
こわれてもだいじょうぶ、こわれにくい、そういうのをつくっているんですよ
省電力というテーマでつくったCPUという枠組みでARMというのがある
ARMという規格に適合したものをいろんなところがつくっている
Intelがつくる可能性もある（まだきいたことはない とだは）
次期windowsもARM版が出る方向にあって 世界的なながれ
PowerBookは金属（仕事用）（接続端子があますところなくついてる）（CPUがはやいのがのってる）
When the diesel generators were gone, the reactor operators switched to emergency battery power. The batteries were designed as one of the backups to the backups, to provide power for cooling the core for 8 hours. And they did.
Within the 8 hours, another power source had to be found and connected to the power plant. The power grid was down due to the earthquake. The diesel generators were destroyed by the tsunami. So mobile diesel generators were trucked in.
This is where things started to go seriously wrong. The external power generators could not be connected to the power plant (the plugs did not fit). So after the batteries ran out, the residual heat could not be carried away any more.
At this point the plant operators begin to follow emergency procedures that are in place for a “loss of cooling event”. It is again a step along the “Depth of Defense” lines. The power to the cooling systems should never have failed completely, but it did, so they “retreat” to the next line of defense. All of this, however shocking it seems to us, is part of the day-to-day training you go through as an operator, right through to managing a core meltdown.
It was at this stage that people started to talk about core meltdown. Because at the end of the day, if cooling cannot be restored, the core will eventually melt (after hours or days), and the last line of defense, the core catcher and third containment, would come into play.
But the goal at this stage was to manage the core while it was heating up, and ensure that the first containment (the Zircaloy tubes that contains the nuclear fuel), as well as the second containment (our pressure cooker) remain intact and operational for as long as possible, to give the engineers time to fix the cooling systems.
Because cooling the core is such a big deal, the reactor has a number of cooling systems, each in multiple versions (the reactor water cleanup system, the decay heat removal, the reactor core isolating cooling, the standby liquid cooling system, and the emergency core cooling system). Which one failed when or did not fail is not clear at this point in time.
So imagine our pressure cooker on the stove, heat on low, but on. The operators use whatever cooling system capacity they have to get rid of as much heat as possible, but the pressure starts building up. The priority now is to maintain integrity of the first containment (keep temperature of the fuel rods below 2200°C), as well as the second containment, the pressure cooker. In order to maintain integrity of the pressure cooker (the second containment), the pressure has to be released from time to time. Because the ability to do that in an emergency is so important, the reactor has 11 pressure release valves. The operators now started venting steam from time to time to control the pressure. The temperature at this stage was about 550°C.
This is when the reports about “radiation leakage” starting coming in. I believe I explained above why venting the steam is theoretically the same as releasing radiation into the environment, but why it was and is not dangerous. The radioactive nitrogen as well as the noble gases do not pose a threat to human health.
At some stage during this venting, the explosion occurred. The explosion took place outside of the third containment (our “last line of defense”), and the reactor building. Remember that the reactor building has no function in keeping the radioactivity contained. It is not entirely clear yet what has happened, but this is the likely scenario: The operators decided to vent the steam from the pressure vessel not directly into the environment, but into the space between the third containment and the reactor building (to give the radioactivity in the steam more time to subside). The problem is that at the high temperatures that the core had reached at this stage, water molecules can “disassociate” into oxygen and hydrogen – an explosive mixture. And it did explode, outside the third containment, damaging the reactor building around. It was that sort of explosion, but inside the pressure vessel (because it was badly designed and not managed properly by the operators) that lead to the explosion of Chernobyl. This was never a risk at Fukushima. The problem of hydrogen-oxygen formation is one of the biggies when you design a power plant (if you are not Soviet, that is), so the reactor is build and operated in a way it cannot happen inside the containment. It happened outside, which was not intended but a possible scenario and OK, because it did not pose a risk for the containment.
So the pressure was under control, as steam was vented. Now, if you keep boiling your pot, the problem is that the water level will keep falling and falling. The core is covered by several meters of water in order to allow for some time to pass (hours, days) before it gets exposed. Once the rods start to be exposed at the top, the exposed parts will reach the critical temperature of 2200 °C after about 45 minutes. This is when the first containment, the Zircaloy tube, would fail.
And this started to happen. The cooling could not be restored before there was some (very limited, but still) damage to the casing of some of the fuel. The nuclear material itself was still intact, but the surrounding Zircaloy shell had started melting. What happened now is that some of the byproducts of the uranium decay – radioactive Cesium and Iodine – started to mix with the steam. The big problem, uranium, was still under control, because the uranium oxide rods were good until 3000 °C. It is confirmed that a very small amount of Cesium and Iodine was measured in the steam that was released into the atmosphere.
It seems this was the “go signal” for a major plan B. The small amounts of Cesium that were measured told the operators that the first containment on one of the rods somewhere was about to give. The Plan A had been to restore one of the regular cooling systems to the core. Why that failed is unclear. One plausible explanation is that the tsunami also took away / polluted all the clean water needed for the regular cooling systems.
The water used in the cooling system is very clean, demineralized (like distilled) water. The reason to use pure water is the above mentioned activation by the neutrons from the Uranium: Pure water does not get activated much, so stays practically radioactive-free. Dirt or salt in the water will absorb the neutrons quicker, becoming more radioactive. This has no effect whatsoever on the core – it does not care what it is cooled by. But it makes life more difficult for the operators and mechanics when they have to deal with activated (i.e. slightly radioactive) water.
But Plan A had failed – cooling systems down or additional clean water unavailable – so Plan B came into effect. This is what it looks like happened:
In order to prevent a core meltdown, the operators started to use sea water to cool the core. I am not quite sure if they flooded our pressure cooker with it (the second containment), or if they flooded the third containment, immersing the pressure cooker. But that is not relevant for us.
The point is that the nuclear fuel has now been cooled down. Because the chain reaction has been stopped a long time ago, there is only very little residual heat being produced now. The large amount of cooling water that has been used is sufficient to take up that heat. Because it is a lot of water, the core does not produce sufficient heat any more to produce any significant pressure. Also, boric acid has been added to the seawater. Boric acid is “liquid control rod”. Whatever decay is still going on, the Boron will capture the neutrons and further speed up the cooling down of the core.
The plant came close to a core meltdown. Here is the worst-case scenario that was avoided: If the seawater could not have been used for treatment, the operators would have continued to vent the water steam to avoid pressure buildup. The third containment would then have been completely sealed to allow the core meltdown to happen without releasing radioactive material. After the meltdown, there would have been a waiting period for the intermediate radioactive materials to decay inside the reactor, and all radioactive particles to settle on a surface inside the containment. The cooling system would have been restored eventually, and the molten core cooled to a manageable temperature. The containment would have been cleaned up on the inside. Then a messy job of removing the molten core from the containment would have begun, packing the (now solid again) fuel bit by bit into transportation containers to be shipped to processing plants. Depending on the damage, the block of the plant would then either be repaired or dismantled.
Now, where does that leave us?
・The plant is safe now and will stay safe.
・Japan is looking at an INES Level 4 Accident: Nuclear accident with local consequences. That is bad for the company that owns the plant, but not for anyone else.
・Some radiation was released when the pressure vessel was vented. All radioactive isotopes from the activated steam have gone (decayed). A very small amount of Cesium was released, as well as Iodine. If you were sitting on top of the plants’ chimney when they were venting, you should probably give up smoking to return to your former life expectancy. The Cesium and Iodine isotopes were carried out to the sea and will never be seen again.
・There was some limited damage to the first containment. That means that some amounts of radioactive Cesium and Iodine will also be released into the cooling water, but no Uranium or other nasty stuff (the Uranium oxide does not “dissolve” in the water). There are facilities for treating the cooling water inside the third containment. The radioactive Cesium and Iodine will be removed there and eventually stored as radioactive waste in terminal storage.
・The seawater used as cooling water will be activated to some degree. Because the control rods are fully inserted, the Uranium chain reaction is not happening. That means the “main” nuclear reaction is not happening, thus not contributing to the activation. The intermediate radioactive materials (Cesium and Iodine) are also almost gone at this stage, because the Uranium decay was stopped a long time ago. This further reduces the activation. The bottom line is that there will be some low level of activation of the seawater, which will also be removed by the treatment facilities.
・The seawater will then be replaced over time with the “normal” cooling water
・The reactor core will then be dismantled and transported to a processing facility, just like during a regular fuel change.
・Fuel rods and the entire plant will be checked for potential damage. This will take about 4-5 years.
・The safety systems on all Japanese plants will be upgraded to withstand a 9.0 earthquake and tsunami (or worse)
・I believe the most significant problem will be a prolonged power shortage. About half of Japan’s nuclear reactors will probably have to be inspected, reducing the nation’s power generating capacity by 15%. This will probably be covered by running gas power plants that are usually only used for peak loads to cover some of the base load as well. That will increase your electricity bill, as well as lead to potential power shortages during peak demand, in Japan.
If you want to stay informed, please forget the usual media outlets and consult the following websites:
http://www.world-nuclear-news.org/RS_Battle_to_stabilise_earthquake_reactors_1203111.html
http://bravenewclimate.com/2011/03/12/japan-nuclear-earthquake/
http://ansnuclearcafe.org/2011/03/11/media-updates-on-nuclear-power-stations-in-japan/
海外に電話をかける必要があり、スカイプから海外の固定電話や携帯電話と通話できるサービスを使おうと思って、スカイプのクレジットを購入したつもりだった。
つもりだったというのは、決済したのにいまだにクレジットが加算されていないからだ。
いつものようにやたらと重いマイアカウントのページを開き、クレジットカード情報を入力して、
煩雑な本人確認サービスをかいくぐってやっとのことでクレジット購入手続きを済ませたつもりだった。
決済完了の画面が出て、「通常、クレジットカードで直接申し込んだ注文の処理は15分以内に完了します」と書かれている。
文句の一つでも言いたいと思い、問い合わせ窓口を探したが、日本語のページには問い合わせ窓口へのリンクが一切ない。
英語のページでヘルプデスクを探すも、いっこうに直接問い合わせる窓口へたどり着かない。
クレジットカードでカネを客に払わせ、フォローがないまま完全放置である。
30分ほどして、メールが届いた。
決済完了か？ と思ったら、英文で
we're processing your order
（注文を処理中）
という件名だった。
本文には
Credit card transactions usually clear within one hour, but can take up to 24 hours.
（クレジットカード決済には通常一時間以内に完了しますが、24時間かかることもあるよ）
と書いてある。
15分で終わると書いていたのは、どこの誰なのか。口あたりのよい嘘か。
メールには続きがある。
Few things to try out while you wait
（待っている間に試すべきいくらかのことがら）
http://www.skype.com/share/stories/
（他のユーザーがどうスカイプを使っているか、スカイプストーリーズで読もう）
これは客を怒らせたくてやっていることなのだろうか。
それともP2Pネットワークの背後にはじつは誰もいなかったりするのだろうか。
有料サービスはあまりにも胡散臭くて後悔した。
http://b.hatena.ne.jp/entry/http://www.lifehacker.jp/2009/03/keyholetv.html
苫米地氏が関係。
http://ja.wikipedia.org/wiki/KeyHoleTV
「ノート」内にある「SCOPE第1回成果発表会プログラム」へのリンク。
http://www.soumu.go.jp/joho_tsusin/scope/event/bessi.html
ページの最後に「次世代P2P型コンテンツ流通高度化技術に関する研究開発 コグニティブリサーチラボ株式会社 苫米地 英人」という発表。
http://www.soumu.go.jp/joho_tsusin/scope/event/yokousyu/session10/kokusai3.pdf
pdfから抜粋。
[1] Yasuaki Takebe,Hideki Mima,Hideto Tomabechi, “Conference on Natural Language Processing, An Efficient Information Retrieval Technique for P2P Content Sharing Systems”,The first International Joint(2004/3)
[2] Yasuaki Takebe,Hideki Mima,Hideto Tomabechi,“A Novel Method for Content Consistency and Efficient Full-Text Search for P2P Content Sharing Systems”,ACM SIGCOMM2004
[3] Yasuaki Takebe,Hideki Mima,Hideto Tomabechi,” Conference of Parallel and Distributed Systems, A New Method of Content Consistency Maintenance and Full-Text Search towards Secure and High-Performance P2P Content Sharing”,IEEE The 10th International
他2編
SIGCOMMに通ってるとはすごい、と思って調べてみた。
[1] http://www.rcl.cityu.edu.hk/ijcnlp04/prelimprogram.htm には見つからない。
[2] http://conferences.sigcomm.org/sigcomm/2004/conf_program.html には見つからない。
[3] http://www.informatik.uni-trier.de/~ley/db/conf/icpads/icpads2004.html には見つからない。
ひょっとして「出しました」ということか？
(For Beginners)
(For Windows)
(For Mac)
(In case you are using shared computer)
(Information)
（語学学習サイト個人的リンクメモ / Lists of Language Learning Links）
Table of Contents： ||||||
| オープンソースソフトウェアとGIS | Open Source software and GIS | Open Source software and GIS | 1 (6) |
| オープンソース概念 | Open Source concept | 1 (2) | |
| オープンソースGISとしてのGRASS | GRASS as an Open Source GIS | 3 (2) | |
| ノースカロライナサンプルデータセット | The North Carolina sample data set | 5 (1) | |
| この本の読み方 | How to read this book | 5 (2) | |
| GISの概念 | GIS concepts | GIS concepts | 7 (14) |
| 一般的なGISの原理 | General GIS principles | 7 (6) | |
| 地理空間データモデル | Geospatial data models | 7 (4) | |
| GISデータとシステムの構成 | Organization of GIS data and system | 11 (2) | |
| 機能 | functionality | ||
| 地図投影法と座標系 | Map projections and coordinate systems | 13 (8) | |
| 地図投影原理 | Map projection principles | 13 (3) | |
| 一般的な座標系とdatums | Common coordinate systems and datums | 16 (5) | |
| GRASSをはじめよう | Getting started with GRASS | Getting started with GRASS | 21 (32) |
| 第一歩 | First steps | 21 (16) | |
| GRASSのダウンロードとインストール | Download and install GRASS | 21 (2) | |
| データベースとコマンドの構造 | Database and command structure | 23 (3) | |
| GRASS6のためのグラフィカルユーザインタフェイス: | Graphical User Interfaces for GRASS 6: | 26 (1) | |
| QGISとgis.m | QGIS and gis.m | ||
| ノースカロライナを用いてGRASSを開始 | Starting GRASS with the North Carolina | 27 (3) | |
| データセット | data set | ||
| GRASSデータ・ディスプレイと3D可視化 | GRASS data display and 3D visualization | 30 (4) | |
| プロジェクトデータ管理 | Project data management | 34 (3) | |
| 新しいプロジェクトでGRASSを開始 | Starting GRASS with a new project | 37 (7) | |
| aのための座標系の定義 | Defining the coordinate system for a | 40 (4) | |
| 新しいプロジェクト | new project | ||
| 空間投影されていないxy座標系 | Non-georeferenced xy coordinate system | 44 (1) | |
| 座標系の変換 | Coordinate system transformations | 44 (9) | |
| 座標系のリスト | Coordinate lists | 45 (2) | |
| ラスタとベクトル地図の投影 | Projection of raster and vector maps | 47 (1) | |
| GDAL/OGRツールで、再投影 | Reprojecting with GDAL/OGR tools | 48 (5) | |
| GRASSデータモデルとデータの交換 | GRASS data models and data exchange | 53 (30) | |
| ラスターデータ | Raster data | 54 (16) | |
| GRASSの2Dの、3Dのラスターデータモデル | GRASS 2D and 3D raster data models | 54 (2) | |
| 領域の統合と境界 | Managing regions and boundaries | raster map resolution | |
| ジオコードされたラスターデータのインポート | Import of georeferenced raster data | 58 (8) | |
| スキャンされた歴史的地図のインポートとジオコーディング | Import and geocoding of a scanned | 66 (3) | |
| ラスターデータエクスポート | Raster data export | 69 (1) | |
| ベクトルデータ | Vector data | 70 (13) | |
| GRASSベクトルデータモデル | GRASS vector data model | 70 (3) | |
| ベクトルデータのインポート | Import of vector data | 73 (5) | |
| xy CAD描画のための座標変換 | Coordinate transformation for xy CAD drawings | 78 (2) | |
| ベクトルデータのエクスポート | Export of vector data | 80 (3) | |
| ラスターデータを使う | Working with raster data | 83 (86) | |
| ラスター地図を表示、管理 | Viewing and managing raster maps | 83 (22) | |
| ラスターデータの表示と、カラーテーブルの割り当て | Displaying raster data and assigning a color table | 83 (3) | |
| ラスター地図に関するメタデータを管理 | Managing metadata of raster maps | 86 (2) | |
| ラスター地図のクエリとプロファイル | Raster map queries and profiles | 88 (2) | |
| ラスター地図の統計 | Raster map statistics | 90 (1) | |
| ラスター地図のズームと、部分集合の生成 | Zooming and generating subsets from | 91 (1) | |
| 簡単なラスター地図の生成 | Generating simple raster maps | 92 (2) | |
| 再分類と再スケーリング | Reclassification and rescaling of | 94 (3) | |
| ラスター地図 | raster maps | ||
| ラスター地図タイプの記録と値の置換 | Recoding of raster map types and value replacements | 97 (2) | |
| カテゴリラベルの割り当て | Assigning category labels | 99 (4) | |
| マスキングとノーデータ値の取り扱い | Masking and handling of no-data values | 103(2) | |
| ラスター地図の計算 | Raster map algebra | 105(10) | |
| 整数と浮動小数点データ | Integer and floating point data | 107(1) | |
| 基本的な計算 | Basic calculations | 108(1) | |
| “if"状態を使う | Working with ``if'' conditions | 109(1) | |
| r.mapcalcのNULL値の取り扱い | Handling of NULL values in r.mapcalc | 110(1) | |
| r.mapcalcでMASKを作成 | Creating a MASK with r.mapcalc | 111(1) | |
| 特別なグラフ演算子 | Special graph operators | 112(1) | |
| 相対的座標での近傍演算 | Neighborhood operations with relative coordinates | 113(2) | |
| ラスタデータの変換と内挿 | Raster data transformation and interpolation | 115(11) | |
| 離散的ラスターデータの自動的ベクトル化 | Automated vectorization of discrete raster data | 115(3) | |
| 連続フィールドの等値線の描画を生成 | Generating isolines representing continuous fields | 118(1) | |
| ラスタデータのリサンプリングと内挿 | Resampling and interpolation of raster data | 119(5) | |
| ラスター地図のオーバーレイとマージ | Overlaying and merging raster maps | 124(2) | |
| ラスターデータの空間分析 | Spatial analysis with raster data | 126(29) | |
| 近傍分析とクロスカテゴリー統計 | Neighborhood analysis and cross-category statistics | 126(7) | |
| ラスタフィーチャのバッファリング | Buffering of raster features | 133(2) | |
| コストサーフェイス | Cost surfaces | 135(5) | |
| 地勢と分水界分析 | Terrain and watershed analysis | 140(13) | |
| ランドスケープ構造解析 | Landscape structure analysis | 153(2) | |
| ランドスケーププロセスモデリング | Landscape process modeling | 155(11) | |
| 水文学的、地下水のモデル | Hydrologic and groundwater modeling | 155(3) | |
| 浸食と宣誓証言モデル | Erosion and deposition modeling | 158(8) | |
| ラスタベースのモデルと解析に関するまとめ | Final note on raster-based modeling and analysis | 166(1) | |
| ボクセルデータを使う | Working with voxel data | 166(3) | |
| ベクトルデータを使う | Working with vector data | 169(94) | |
| 地図の表示とメタデータ管理 | Map viewing and metadata management | 169(4) | |
| ベクトル地図を表示 | Displaying vector maps | 169(3) | |
| ベクトル地図メタデータ維持 | Vector map metadata maintenance | 172(1) | |
| ベクトル地図属性管理とSQLのサポート | Vector map attribute management and SQL support | 173(14) | |
| GRASS6でのSQLサポート | SQL support in GRASS 6 | 174(7) | |
| サンプルSQLクエリと属性変更 | Sample SQL queries and attribute modifications | 181(4) | |
| 地図再分類 | Map reclassification | 185(1) | |
| 複数の属性があるベクトル地図 | Vector map with multiple attribute tables: layers | 186(1) | |
| ベクトルデータをデジタル化 | Digitizing vector data | 187(5) | |
| 位相的データのデジタル化の一般原理 | General principles for digitizing topological data | 187(2) | |
| GRASSでの対話的なデジタイジング | Interactive digitizing in GRASS | 189(3) | |
| ベクトル地図クエリと統計 | Vector map queries and statistics | 192(4) | |
| 地図のクエリ | Map queries | 192(2) | |
| ベクトルオブジェクトに基づくラスター地図統計 | Raster map statistics based on vector objects | 194(2) | |
| ポイントベクトル地図統計 | Point vector map statistics | 196(1) | |
| 幾何学操作 | Geometry operations | 196(20) | |
| 位相的な操作 | Topological operations | 197(6) | |
| バッファリング | Buffering | 203(1) | |
| フィーチャの抽出と境界のディゾルブ | Feature extraction and boundary dissolving | 204(1) | |
| ベクトル地図を修理 | Patching vector maps | 205(1) | |
| ベクトル地図のインターセクディングとクリッピング | Intersecting and clipping vector maps | 206(3) | |
| ベクトルの幾何の変換と3Dベクトルの作成 | Transforming vector geometry and creating 3D vectors | 209(2) | |
| 点からのコンベックスハルとトライアンギュレーション | Convex hull and triangulation from points | 211(1) | |
| 同じ位置の掘り出し物の複数のポイント | Find multiple points in same location | 212(2) | |
| 一般的な多角形境界の長さ | Length of common polygon boundaries | 214(2) | |
| ベクトルネットワーク分析 | Vector network analysis | 216(11) | |
| ネットワーク分析 | Network analysis | 216(5) | |
| 直線的な参照システム(LRS) | Linear reference system (LRS) | 221(6) | |
| ラスタへのベクトルデータ変化 | Vector data transformations to raster | 227(3) | |
| 空間的な内挿と近似 | Spatial interpolation and approximation | 230(19) | |
| 内挿方法を選択 | Selecting an interpolation method | 230(5) | |
| RSTによる内挿と近似 | Interpolation and approximation with RST | 235(2) | |
| RSTパラメタの調整: テンションとスムージング | Tuning the RST parameters: tension and smoothing | 237(4) | |
| RSTの精度を評価 | Estimating RST accuracy | 241(3) | |
| セグメント化処理 | Segmented processing | 244(3) | |
| RSTとのトポグラフィー分析 | Topographic analysis with RST | 247(2) | |
| ライダーポイントのクラウドデータを使う | Working with lidar point cloud data | 249(8) | |
| ボリュームに基づくは内挿 | Volume based interpolation | 257(6) | |
| 3番目の変数の追加: 高度のある降水量 | Adding third variable: precipitation with elevation | 258(3) | |
| ボリュームとボリューム-時間内挿 | Volume and volume-temporal interpolation | 261(1) | |
| 地球統計学とスプライン | Geostatistics and splines | 262(1) |
プログラミングなんて、人に教わろうなんて思っちゃ駄目だぜ。師匠はいてもいい。人には、わからないところを聞くもんだぜ。プログラミングなんて習うより慣れろ、だぜ。
とりあえず、目に見える形が出るものをやってみるのが一番だぜ。昔なら、Basicマガジンのゲームのソースを打ち込んで、改造したけど、これって、目に見えて、変化するから、覚えられるんだぜ。
つまりだな、以下のプログラミング環境を触ってみるのがいいんだぜ。
とにかく、わからなくても、サンプルとかネットのコードを弄ってみて、改造して、覚えるもんだぜ。
とりあえず、プログラミングに詳しいリアル友達がいなかったら、2chの初心者スレで聞きまくるんだぜ。聞くコツは、「初心者ですが、よろしくお願いします」なんてわかりきったこと言わないことだぜ。あとは、エラー内容とかは、詳細まで貼り付けることだぜ。
