2012+前半

6th Jan. 文章作成の三つ段階
 * 第一阶段：提笔，总结，把作好的东西通通搬上纸面. 改n遍，n>10. 这叫搭粗架子.
 * 第二阶段：写累了，改累了，就不要再改了. 这时，把所有写好的东西扔掉，重新写. 重新搭更美的架子. 把食之无味，弃置可惜的东西扔掉. 把禁不起推敲的结果扔掉. 如此改至少15遍，直到. . . ..
 * 第三阶段：会有一天，你会**突然**特别喜欢你自己写的东西了，这时别人让你停你都舍不得停下来，觉得太美太艺术了，觉得自己是个语言的匠人了. 你就象米开朗琪罗完成一个塑像，从雕像上抠下一个小芝麻大小的泥块，又把这个小芝麻分成一半，慢慢加回去，这才满意. **这时您就进入下一个境界**. 这以后再改十遍，就可以考虑投出去. 如果改到你把昨天改掉的东西今天又改回来了，你的“推敲”功夫就花的差不多了，可以几乎无悔的投稿了.

11th, Jan.
How to deal with the comments and judgments from the reviewers （ 1 ）审稿人是上帝，不管是挖苦还是赞美你的工作，先虚心接受, 来一句： Thank the reviewers for these precious comments and suggestions. （ 2 ）所有 comments ，必须一一响应： Point by point: comments and response (3) 当能容易满足审稿人要求时，必须尽量满足，补充实验，补充结果比较，补充文献参考，补充实验描述，补充各色各样的内容. (4) 当根本无法满足审稿人要求时，比如要你比较算法性能，而你实在无法操作，你得说你已经努力的实施这个实验，但是因为很多的客观原因而无法实施，把过程和结果在报告里列出来，而且我已经在论文里 review 了相关于比较对象或者相似实验的论文给读者提供更多参考性意见，同时列举在 Responding Report 里，需要说明将来一旦可行了，必然完整进行这个实验. (5) 当审稿人质疑你的模型和实验结果时，就需要旁征博引（其他文献），补充过程和实验细节，额外的在 Responding Report 里增加一些容易实现的实验结果来增强审稿人信心. (6) 当审稿人需要你验证某些方法和结论时，而你无法说明的时候，除了补充一些引用说明外，还需要特别指出： This is an interesting open issue, and we will continue to …... . （ 7 ）当审稿人指出你的英文质量有问题时（发表了几十个文章，我还是经常被质疑）：需要在文章里尽量找错误，但是同时要在 response report 里一一列出来，使得审稿人认为你已经尽力了（我是中国人，洋文能看懂就可以了）. （ 8 ）尽量把 revision part 一一列在 response report 里相应的地方，而不要让审稿人到文章中去找你修改的地方. （ 9 ）尽量使得文章格式符合该期刊格式 （ 10 ）顶级期刊往往有多于 3 个审稿人，必须认真对待，留足够的修改时间， 1 年 1-2 个顶级期刊(专业前五，非NSC之类)发表足矣，就少费点心思在次点的期刊上吧，或者就放弃（这个需要等到了一定层次，呵呵）. （ 11 ）字体一般 11 号和 1.5 倍行距刚好，大了或小了都感觉累，累了自然就给刁钻的 Judgement 了

13th, Jan.
How to chose the right route of your career life 1. 成长优先 2. 雪中送炭 3. 先舍后得 4. 先人后己 5. 身心合一

16th, Jan.
[|A good summary of Chinglish!]

18th, May
There is only One machine The web is its OS All screens look into the One No bits will live out of the web To share is to gain Let the One read it The One is us

Kevin Kelly- The next 5000 days of the web

19th, May
実装工程を意識した基板設計 http://www.kumikomi.net/archives/2010/11/ep36pri2.php?page=5

オンライン計算シート プロのエンジニアが設計現場で使っている計算式を入手し，整理しました． 電子回路の値がパッと求まります． 電気工学の原理理解に利用できる. お試しください． http://toragi.cqpub.co.jp/tabid/316/Default.aspx

20th, May
第五维空间的革命 当牛顿写下三大定律时，他把天和地统一了起来. 天上的星球和地上的物体遵守着同样的规则. 当爱因斯坦创立相对论后，时间和空间通过光速成了一体. 三维空间加上时间成了四维. 现在，IT的发展把正在现实与计算机里的虚拟界限打破，将四维空间进一步扩展到五维. 一场新的革命正在孕育.

23th, May
关于信号与系统基本概念的一个明了概述. 卷积，频率，傅里叶变化，拉式变换，复数，小波等. http://bbs.sciencenet.cn/thread-554282-1-1.html

An evolving Concept Map for Cyber-Physical Systems (CPS) which concisely highlight the problems for every region related with CPS. http://cyberphysicalsystems.org/

下面这本书和讲义PPT可以在作者网站免费下载，Youtube上有授课视频 A introduction to embedded systems, a Cyber-physical system approach.

在分层结构中，抽象作为人类认识事物的常用方法，可以对上层使用者隐藏下层的实现细节， 从而利于模型的使用. 但在传统的分层结构中，利于网络，嵌入式系统等，各层没有对时间定义给予充分的重视，导致很难精确预测，控制，和评价应用系统的实时特性. 本身作者强调通过系统开发中正确的Modeling的方法来集中解决这个难题.

29th, May
最近、思っているのは個人の研究活動がプロジェクトとして、マネジメントすることができるでしょうか. いままで進化してきたクラウド技術、と便利なツール（Toodlede, evernote, dropbox, imindmap）などを試しながら、具体的な解決案を探って見ます.

これがグループの研究活動を管理する時に原則. 以下が抜粋です. (ii) Do a few things well [That’s what you’ll be remembered for] (vii) Understand your place in the broader national and international research context (ix) [Don’t become complacent; it’s easier to get to the top than to stay there]

(i) Minimize soft money; a lesser amount of hard money is almost always better in the long run

(i) [There is no substitute for one very competent person] (iii) Personnel decisions are the most important actions taken (iv) It is better to not fill a vacancy than to compromise quality; patience always pays off (v) Don’t be afraid to go after promising young people who haven’t yet made their reputation; this is much better than getting senior well known scientists who may be over the hill (vi) Get good people and give them their head within broad guidelines and constraints [and don’t micro manage them—it’s a sign of supervisor’s weakness] (viii) Get rid of weak people; they will have no future with your organization; until they leave, place them where they can do a minimum of damage (ix) Reward those who make effective use of resources, such as travel [funds], computer time, support staff (xi) Avoid unnecessary meetings and reporting (xiii) The administrative structure [should] exist to serve the scientific staff which is responsible for the primary product of the organization (iii) [I find that] there is a maximum effective size of groups; beyond which office communication breaks down (5–25 scientists) (iii) [You never win a battle permanently, it always has to be re-fought

13th, Jun
The definition of several model in cloud computing Providers of CaaS (known as CaaS vendors) are responsible for the management of hardware and software required for delivering Voice over IP (VoIP) services, Instant Messaging (IM), and video conferencing capabilities to their customers. This model began its evolutionary process from within the telecommunications (Telco) industry, not unlike how the SaaS model arose from the software delivery services sector.

Infrastructure-as-a-Service (IaaS) is the delivery of computer infrastructure (typically a platform virtualization environment) as a service. IaaS leverages significant technology, services, and data center investments to deliver IT as a service to customers.

IaaS VS CaaS From the provider point of view, both of the two cases need to provide and manage the hardware and software infrastructure. service supported by IaaS is not limited to communication service listed above.

IaaS VS traditional outsourcing model requires extensive due diligence, negotiations ad infinitum, and complex, lengthy contract vehicles, IaaS is centered around a model of service delivery that provisions a predefined, standardized infrastructure specifically optimized for the customer’s applications. Simplified statements of work and à la carte service-level choices make it easy to tailor a solution to a customer’s specific application requirements. IaaS providers manage the transition and hosting of selected applications on their infrastructure. Customers maintain ownership and management of their application(s) while off-loading hosting operations and infrastructure management to the IaaS provider.

On-demand computing VS Cloud computing On-demand computing is an increasingly popular enterprise model in which computing resources are made available to the user as needed. Computing resources that are maintained on a user’s site are becoming fewer and fewer, while those made available by a service provider are on the rise. The on-demand model evolved to overcome the challenge of being able to meet fluctuating resource demands efficiently. Because demand for computing resources can vary drastically from one time to another, maintaining sufficient resources to meet peak requirements can be costly.

The PaaS model makes all of the facilities required to support the complete life cycle of building and delivering web applications and services entirely available from the Internet, all with no software downloads or installation for developers, IT managers, or end users.

PaaS VS IaaS Unlike the IaaS model, where developers may create a specific operating system instance with homegrown applications running, PaaS developers are concerned only with web-based development and generally do not care what operating system is used. PaaS services allow users to focus on innovation rather than complex infrastructure.

PaaS VS on-premises model On-premises model needs to control every aspects in the application development and maintained by yourselves. PaaS offers a faster, more cost-effective model for application development and delivery.

Software-as-a-Service is a software distribution model in which applications are hosted by a vendor or service provider and made available to customers over a network, typically the Internet.

SaaS VS SaaP The traditional model of software distribution, in which software is purchased for and installed on personal computers, is sometimes referred to as Software-as-a-Product.

SaaS VS our proposal SaaS enable users to use the needed software, and free from the software implementation and deployment. Most of existed SaaS solution is developed to work within a web-browser.

SaaS VS four maturity level Level 1: no maturity Level 2: configurability Level 3: Multitenant Efficiency Level 4: Scalable

What is service? A service is, in essence, a function that is well defined, self-contained, and does not depend on the context or state of other services.

Load Balancing: a technique to spread work between two or more computers, network links, CPUs, hard drives, or other resources, in order to get optimal resource utilization, maximize throughput, and minimize response time. In most common server load balancing architectures, an incoming request is redirected to a load balancer that is transparent to the client making the request. Based on predetermined parameters, such as availability or current load, the load balancer typically uses a round-robin scheduling algorithm to determine which server should handle the request and then forwards the request on to the selected server. To make the final determination, the load balancing algorithm, the load balancer retrieves information about the candidate server’s health and current workload in order to verify its ability to respond to a request.

Linux Virtual Server Load Balancer (LVS): A popular load balancer The LVS employs a common three-tier architecture that consists of the load balancer, which acts as a front end to the cluster and balances (or distributes) requests from clients across a set of servers (sometimes called a bank) so that the client’s perception is that all the services come from a single IP address. The second tier, the server cluster, is a group of servers running network services, such as HTTP, POP3, SMTP, FTP, or DNS. The third tier is shared storage, which provides a shared storage space for the servers so it is easy for them to use/reuse the same contents and provide the same services for each client request.

19th, Jun. Teleglass の接続問題 Ipodと接続にはアナログ変換Adapterが必要、購入先はイギリスアマゾンのWebsiteでDexim社の製品を検索 パソコンとの接続はダウンスキャンコンバータが必要、日本アマゾンから購入できる. http://www.mikimoto-japan.com/beans/solution/sol-hmd01.htm

20th, Jun. **//Memory footprint//** refers to the amount of main //memory// that a program uses or references while running.

25th, Jun. Apache Web ServerとMySQL、PHP、Perlのインストールと連携が難しいと知っています. XAMPPはMySQLやPHPやPerlを含んだApacheディストリビューションとして簡単にインストールすることができます. インストールは、「ダウンロードして、展開して、実行するだけ」. 本当にとても簡単です.
 * XAMPP**:

27th, Jun. 最好的休息，是让你重燃生活的热情 http://tieba.baidu.com/p/1295485461