Archive for 7월, 2011

얼음꽃 (아이유 & 김연아)



아저씨들이 가장 좋아하는 탑2, 연아 & 아이유

Git User’s Manual

Git is a distributed revision control system with an emphasis on speed. Git was initially designed and developed by Linus Torvalds for Linux kernel development. Every Git working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Git’s current software maintenance is overseen by Junio Hamano. Git is free software distributed under the terms of the GNU General Public License version 2.

Git User’s Manual
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html

Git 사용자 설명서
번역 : 김남형 2009-04-13 ~ 2009-08-26
http://namhyung.springnote.com/pages/3132772

Introduction to LaTex

LaTeX is a document preparation system for high-quality typesetting. It is most often used for medium-to-large technical or scientific documents but it can be used for almost any form of publishing.

LaTeX is not a word processor! Instead, LaTeX encourages authors not to worry too much about the appearance of their documents but to concentrate on getting the right content.

A (Not So) Short Introduction to LaTeX2e

A short introduction to LaTeX 2e (Korean)

워드 프로세서 사용자를 위한 LaTeX

Online converter – ps to pdf

GhostScript/GhostView 설치할 필요없이 PS 파일을 PDF 문서로 온라인에서 변환해줌

http://ps2pdf.com/convert.htm

Linux Flash File Systems

Choosing a venue: conference or journal?

From:
http://www.cs.washington.edu/homes/mernst/advice/conferences-vs-journals.html

by Michael Ernst (mernst@cs.washington.edu)
December, 2006

Why to prefer a conference

In computer science, your preference should be for conference
publication. Here are some reasons.

  • Conferences have higher status. In part this is a historical artifact of
    the field of computer science, but it is self-perpetuating since that makes
    the best researchers want to send their papers to conferences rather than
    journals.
  • Conferences provide higher visibility and greater impact. Many people will
    attend your talk, you will have the opportunity to answer questions, and
    people will talk to both you and to one another in the hallways. Even
    disregarding the event itself, more non-attendees read conference
    proceedings than read journals.
  • Conferences have higher quality. Acceptance rates to good conferences are
    often around 10% (at least in software engineering, which is my field),
    whereas even the best journals are less selective. Naturally, there exist
    low-quality conferences (and journals), but if your c.v. is cluttered with
    them, then you will appear to be incapable of good work (even if the work
    you published in those venues really is good!), and your good publications
    will not stand out. A good rule of thumb is that the best conferences are
    sponsored by ACM.
  • Conferences are more timely. It can take years for a journal publication
    to appear (or even for reviews to come back), whereas the turnaround time
    for conference reviews is a few months, and the proceedings also appear
    quickly.
  • Conferences have higher standards of novelty. Journals often only require
    20-30% of the material to be new, compared to an earlier conference version.

Why to prefer a journal

There are situations in which journal publication is desirable.

  • Journals may have longer page limits. If you have too many experimental
    results to fit in a conference publication, then a journal affords an
    opportunity to include them. You can also include proofs that are too long
    (or boring) for a shorter publication. A journal paper could recap or
    given an overview of an entire research area.
  • Journal reviews tend to be more detailed. A journal reviewer may spend
    days on a paper, whereas a conference reviewer cannot afford to do so for
    each of the many papers he or she is assigned. This is in part
    because conference reviewers often believe the authors’ claims (regarding a
    proof, for example), whereas journal reviewers are expected to verify them.
    It may also be in part because of the expectation that the paper will be
    revised and re-submitted to the same journal. In any event, the extra
    details can help you to improve your work or to understand its shortcomings.
  • Journals give the opportunity to revise your work and re-submit it for
    review. Actually, conferences give this too: if a paper is rejected from
    one conference, then you can revise based on the reviewers’ comments and
    submit to a different conference, or the same one the next year.
  • Journals have higher acceptance rates, giving the opportunity to get your
    research published. The same is true of workshops. These are particularly
    good venues for people who are just starting their research careers.
  • Some lesser-ranked universities evaluate faculty on the basis of
    journal publications, because the Dean of Engineering is unable or unwilling to
    understand computer science. In most scientific fields, journals have
    higher standards than conferences; computer science is a rare exception.
    A top-ranked CS department can
    convince the dean to use the proper evaluation metric. A lower-ranked CS
    department cannot (the dean may think the department is trying to fool him
    or her).
    If you are at one of these universities, you will need to publish in
    journals, probably by submitting slightly revised versions of your
    conference papers to journals.
    The rush for people at lower-ranked universities (some of whom are
    excellent researchers, and some of whom are not) to submit even marginal
    results to journals is another regrettable factor that tends to lower the
    overall quality of journals.

The best papers at a conference are often solicited for expedited journal
publication.
I sometimes decline these opportunities, but your circumstances may be different.
Whether you accept this invitation should be based on the
factors above, such as whether there is value to the community of an
expanded version of the paper, and how much more work it is to prepare the
journal version. (For example, is there a thesis, technical report, or
other document with additional material beyond the conference paper? Even
better, are there additions that were suggested by reviewers or during
discussions at the conference?)

The journal version of a publication will be cited more than the conference
version, because the journal version has a later date and thus seems more
authoritative. This is a good thing if the journal version adds real value
(or corrects problems!). However, if you have cluttered the paper with a
lot of details that aren’t crucial (like extra tables of results,
experiments that support your point slightly less strongly than the main
ones, or discussions of tangential issues), then your paper may actually
have less impact because readers will get mired in the irrelevant details.
Good writing can avoid such problems.

How to write good engineering papers

How to write good engineering papars

Papers in Conference vs Journal vs Magazine

* Conference vs Journal
  - Conference 
    Need a meeting
    One of the authors requires to come to the conference
    7 ~ 8 pages
  - Journal
    Printed
    Not happened

* Conference vs Workshop
  - Conference
    broad topics
    3 ~ 4 days
    Big
  - Workshop
    narrow topics
    1 ~ 2 days
    small
    2, 3 Workshops become Conference

* Magazine vs Journal
  - Magazine
    simple, not technical
    introduction
  - Journal
    very technical

* Process: Magazine -> Conference (or workshop) -> Journal