Jekyll2023-12-16T14:36:23-08:00https://liuxt.github.io/feed.xmlXutong LiuPostdoc at CUHKXutong Liuliuxt@cse.cuhk.edu.hkThe Art of Presentation2022-12-05T00:00:00-08:002022-12-05T00:00:00-08:00https://liuxt.github.io/posts/2022/12/presentation<p>My personal notes on presentation & meeting. Keep updating…</p>
<p>The following is a quick summary of Prof. Baochun Li’s talk <a href="https://www.bilibili.com/video/BV1PM4y1P7N3?spm_id_from=333.999.0.0">The Art of Presentation</a>.</p>
<h1 id="the-art-of-presentations">The Art of Presentations</h1>
<h1 id="motivation">Motivation</h1>
<p>When most people cannot give good presentations, you can stand out and take advantage!</p>
<h1 id="preparation">Preparation</h1>
<ol>
<li>You should be very excited about your work, be enthusiastic.
<ol>
<li>Use <strong>hand gestures.</strong></li>
<li>Use <strong>maximum power</strong> in voice and a microphone.</li>
<li><strong>Avoid</strong> a tone that feels <strong>boring</strong>.</li>
</ol>
</li>
</ol>
<p><strong>Three tips</strong></p>
<ol>
<li>Keep it simple (KIS).
<ol>
<li>Your audience needs to see the <strong>big picture</strong>. (This is something for the audience to remember).</li>
<li>Answer two questions:
<ol>
<li><strong>What’s my point</strong>.</li>
<li><strong>Why does it matter</strong>.</li>
</ol>
</li>
<li>Design your <strong>take away message.</strong>
<ol>
<li>Why? Presentation is like filling water into a plastic bottle (that only has a narrow neck) — <strong>don’t pour too much too quickly</strong>.</li>
<li>If you want to go <strong>deeper</strong>, <strong>reduce</strong> your scope.</li>
<li>If you want to cover <strong>more</strong>, be <strong>less</strong> technical.</li>
</ol>
</li>
</ol>
</li>
<li>Work hard on the <strong>flow of ideas.</strong>
<ol>
<li>Organize how to deliver the take away message.</li>
</ol>
</li>
<li>Practice your presentation.
<ol>
<li>It is a performance show — every performance show needs rehearsal. The practice only makes your presentation better
<ol>
<li>First in your mid.</li>
<li>Then out loud to yourself.</li>
<li>In front of a friendly audience (like a research group).</li>
<li>Get feedback and improve your talk.</li>
</ol>
</li>
</ol>
</li>
</ol>
<h1 id="design">Design</h1>
<p>1 min of talk ⇒ 50 mins design.</p>
<p><strong>Two tips about design</strong></p>
<ol>
<li>You are the boss, not the slides. Your slides are your assistants.
<ol>
<li>Most speakers include <strong>all</strong> the information they are going to talk about in the slides.</li>
</ol>
</li>
<li>Keep your slides simple.
<ol>
<li>Have plenty of empty space.</li>
<li>Don’t use bullets. <strong>If you have bullets, show them one at a time. (make your audience nervous)</strong></li>
<li>Use huge sans serif fonts.</li>
<li>Use photos and graphics.</li>
<li>Use <strong>builds and overlays</strong>.</li>
</ol>
</li>
</ol>
<h1 id="deliver">Deliver</h1>
<ol>
<li>Open and close your talk well.
<ol>
<li>Like chess, <strong>good opening</strong> is critical— it draws <strong>attention</strong>.</li>
<li>The audience is most alert during the <strong>first several mininutes</strong> of your talk, <strong>use it wisely</strong></li>
<li>Straight to your message as soon as you open</li>
<li>Closing is like gymnastics, <strong>never rush</strong>. Repeating take away messages.</li>
</ol>
</li>
<li>Control the pace very very well.
<ol>
<li>Slow down — the one-way communication channel from you to the audience is <strong>lossy</strong>. If you speed up, everything will be lost. Warm up phases.</li>
<li>Be on time — Know how much time you have left. You have to close <strong>right on time</strong>!</li>
<li>Use a remote control with only the <strong>forward</strong> button. <strong>Never</strong> revisit past slides.</li>
</ol>
</li>
<li>Connect with the audience
<ol>
<li>Talk to the audience.</li>
<li>Make eye contact.</li>
<li>Use gestures.</li>
<li>Move away from the podium.</li>
</ol>
</li>
</ol>Xutong Liuliuxt@cse.cuhk.edu.hkMy personal notes on presentation & meeting. Keep updating…Useful Algorithm/Proof Tricks for Combinatorial Multi-Armed Bandits (CMAB)2022-11-15T00:00:00-08:002022-11-15T00:00:00-08:00https://liuxt.github.io/posts/22/11/CMAB_Trick<p>Some notes about ALgorithm/Proof Tricks for CMAB. Keep updating…</p>
<h1 id="must-read-cmab-papers">Must-read CMAB papers</h1>
<p><a href="https://mycuhk-my.sharepoint.com/:f:/g/personal/1155098137_link_cuhk_edu_hk/Ep6lmvV5ZLdCqR1DxjYJtrQBbUBxCZ_8ub09xjhJO99bDg?e=DS3wkG">These</a> are some must-read papers for CMAB, including different <strong>models</strong> (semi-bandit, full-bandit, cascading bandit, CMAB with triggering arms/CMAB-T, contextual CMAB), different <strong>methods</strong> (ucb, ucb-variance, ucb-distribution, Thompson sampling, policy-randomization, optimzation-based), and <strong>tutorials</strong> (for CMAB before 2017).</p>Xutong Liuliuxt@cse.cuhk.edu.hkSome notes about ALgorithm/Proof Tricks for CMAB. Keep updating…Useful Proof Tricks for Multi-armed Bandits2022-11-14T00:00:00-08:002022-11-14T00:00:00-08:00https://liuxt.github.io/posts/2022/11/MAB_Trick<p>Some notes for algorithm/proof tricks for MAB. Keep updating…</p>
<h1 id="probability">Probability</h1>
<ol>
<li>If A then B, or A implies B, or A⇒B, then $\Pr(B) \ge \Pr(A)$. This is because B occurs every time A occurs, but B might also occur at some other times as well. E.g., A=”dice 1”, B=”dice 1” or “dice 6”, A⇒B.</li>
<li>Only If A occurs, B occurs, or B⇒A, then $\Pr(A)\ge \Pr(B).$</li>
<li>$\Pr(A_1>A_2 \cap B_1>B_2)\le \Pr(A_1+B_1>A_2+B_2)\le\Pr(A_1>A_2) + \Pr(B_1>B_2)$. This is because $A_1+B_1>A_2+B_2$ implies $A_1>A_2$ or $B_1>B_2$ (the reverse cannot happen).</li>
</ol>Xutong Liuliuxt@cse.cuhk.edu.hkSome notes for algorithm/proof tricks for MAB. Keep updating…On Writing Good Research Paper2022-11-14T00:00:00-08:002022-11-14T00:00:00-08:00https://liuxt.github.io/posts/2022/11/Writing<p>My personal notes on writing. Keep updating…</p>
<p>This is a quick summary of Prof. Baochun Li’s talk <a href="https://www.bilibili.com/video/BV18v411n7mr?share_source=copy_web">How to Write Perfect Papers</a>. Another sharing of <a href="https://mycuhk-my.sharepoint.com/:b:/g/personal/1155098137_link_cuhk_edu_hk/EceRe6XzicRNsenQ0NxkVqIBWtw1reTR1epd6cbGQ3vmqg?e=esyZaI">writing tips</a> is also quite useful, will summarize that later.</p>
<h1 id="writing-perfect-papers">Writing Perfect Papers</h1>
<h1 id="story">Story</h1>
<ol>
<li>It’s about how we advance the state of the art.
<ol>
<li><strong>What is the problem.</strong>
<ol>
<li>Following the trend? Could be incremental.</li>
<li>Contrarian, against the trend</li>
</ol>
</li>
<li><strong>What’s new.</strong>
<ol>
<li>First, briefly introduce the state-of-the-art in the literature, solving the same problem you wish to solve.</li>
<li>Talk about what is new in your work.</li>
<li>If the problem is <strong>different from previous work - different assumptions for example,</strong> provide justifications why this assumption is important and necessary.</li>
</ol>
</li>
<li><strong>How is it better.</strong>
<ol>
<li>theoretical properties or better experimental results.</li>
</ol>
</li>
</ol>
</li>
<li>What does a <strong>good</strong> paper look like?
<ol>
<li>Rule #1: Be as <strong>clear</strong> as possible
<ol>
<li>A small misunderstanding can get your paper rejected.</li>
<li>you need to guide the reviewer into your work, and anticipate what will be difficult to understand or could lead to misunderstanding.</li>
<li>and don’t obfuscate</li>
</ol>
</li>
<li>Rule #2: Convince the reader your work is worth publishing (advancing the state of the art)</li>
</ol>
</li>
</ol>
<h1 id="work">Work</h1>
<ol>
<li>Read
<ol>
<li>Become an expert on the problem we want to solve.</li>
<li>How?
<ol>
<li>Start from a single paper.</li>
<li>Do an expanded-ring search: BFS
<ol>
<li>cite, cited, same authors</li>
</ol>
</li>
</ol>
</li>
</ol>
</li>
<li>Write
<ol>
<li>write about what you understood</li>
<li>write every day</li>
<li>writing is the best way to force yourself to <strong>think clearly</strong> and be <strong>focused</strong></li>
<li>idea⇒write a paper⇒do research
<ol>
<li>write related works ⇒ what’s new</li>
<li>write what’s challenging.</li>
<li>write why the problem is important</li>
<li>write what needs to be fixed</li>
</ol>
</li>
<li>Crystallized that you don’t quite understand yet</li>
<li>Writing opens a dialogue, for others to read what you wrote.</li>
</ol>
</li>
<li><strong>Feedback loop</strong>
<ol>
<li>You do not sequentially finish your paper from title, abstr, intro, …, conclusion.</li>
<li>Write⇒ get feedback⇒ write ⇒ get feedback …</li>
<li>The importance of feedback
<ol>
<li>a small misunderstanding can get your paper rejected</li>
<li>it is difficult to read your own paper with the reviewer’s mindset</li>
</ol>
</li>
<li>Each reader can only read your paper for the first time once! Use them carefully.</li>
<li>If reviewers did not understand something, it is because you did not
explain it clearly enough.</li>
</ol>
</li>
</ol>
<h1 id="art">Art</h1>
<ol>
<li>Your paper is the only thing the reviewers (and the readers) see of your work.
<ol>
<li></li>
</ol>
</li>
<li>Pay attention to the title, abstract, intro, and flow of the ideas
<ol>
<li>Title, 2 line, 10000 readers
<ol>
<li>as simple and short as possible</li>
<li>the one that is the easiest to understand at a glance</li>
<li>E.g., local sgd converges fast and communicates little.</li>
</ol>
</li>
</ol>
</li>
<li>Abstract.
<ol>
<li>One sentence to state the background.</li>
<li>One sentence to state ⇒ <strong>what the problem is?</strong> (an interesting and unsolved problem)</li>
<li>Two to four sentences to state the original contributions in the paper⇒<strong>what’s new</strong> (here is my idea, and my idea works)</li>
<li>One sentence to state <strong>how the solution is better</strong>, validated using analyses, simulations or experiments.</li>
</ol>
</li>
<li>Intro
<ol>
<li>First impressions are very important.
<ol>
<li>After reading the intro, the reviewer is <strong>likely to have already decided</strong> (maybe unconsciously) if they will accept the paper or not (if no technical issues)</li>
</ol>
</li>
<li>Self contained: do not need to read the rest of the paper.</li>
<li>Be clear on what the problem is, why our solution is new and how it’s better.</li>
<li>Don’t do…
<ol>
<li>Too long.</li>
<li>spend too much space on the background and related work.</li>
<li>Don’t boost the contribution.</li>
</ol>
</li>
<li>Structure
<ol>
<li>First paragraph: a general overview of the research field, warm up the reader and to prepare for the problem statement, 2-3 sentences.</li>
<li>1-2 paras, state the problem, and existing solutions</li>
<li>limitations of existing solutions that motivate this paper.</li>
<li>Proposed solution: high level idea</li>
</ol>
</li>
<li>What’s new
<ol>
<li>why is the proposed solution different from and better than existing solutions?</li>
<li>1-2 most impressive highlights.</li>
<li>Make the originality of the paper crystal clear and stand out</li>
</ol>
</li>
<li>Hey, if they can really deliver this, that will be very exciting. I will read the rest of the paper.</li>
<li>Include a <strong>table.</strong></li>
<li>Use examples: how main idea works in a special case.</li>
<li>For DL paper
<ol>
<li>1 para: why is the problem is important
<ol>
<li>Don’t discuss related work too much here</li>
</ol>
</li>
<li>2 para: why is the problem difficult</li>
<li>3 para: what is your key idea (you can point to the teaser figure)
<ol>
<li>Give the intuition of your idea, get the reader hooked.</li>
</ol>
</li>
<li>4 para: give important technical details.</li>
<li>5 para: How do you evaluate. What are most impressive results.</li>
<li>6 para: a summary of your contribution (using <strong>bullets</strong>)</li>
</ol>
</li>
</ol>
</li>
<li>Flow of ideas
<ol>
<li>One paragraph contains one complete idea.</li>
<li>Method section:
<ol>
<li>start with an overview of the section</li>
<li>then, give a general description of the method</li>
<li>end with the technical details</li>
<li>always from the more general to the more detailed explanation</li>
</ol>
</li>
<li>Related work
<ol>
<li>not a mere description of the state-of-the-art</li>
<li>show you know the state of the art</li>
<li>show your method solves a new problem, or the problem that were not solved perfectly.</li>
</ol>
</li>
</ol>
</li>
<li>General rules of thumb for the length
<ol>
<li>abstr 200 words</li>
<li>intro 1 page</li>
<li>related work half a page</li>
</ol>
</li>
</ol>
<h1 id="details">Details</h1>
<ol>
<li>Git: track all histories, and <strong>LATEX CODE IS CODE</strong>.</li>
<li>Eliminate grammar and typos</li>
<li>Keep a clear structure.</li>
<li>Use the active form.</li>
<li><strong>Transitional words,</strong>
<ol>
<li>Two half sentences, <strong>as since, or else</strong></li>
<li>Two sentences.
<ol>
<li>However, In addition, Further, Nevertheless, Fortunately, Unfortunately, Surprisingly.</li>
<li>To make matters worse, to further exacerbate the problem the bad news is</li>
<li>The implications are two-fold, It turns out that, As an example, to take … a step further</li>
</ol>
</li>
<li>Sections and paras: It only remains to see …, The simple anser to this question is, the only challenge that remains now is, to address this challenge, we first present, next, we evaluate, we are now ready to.</li>
</ol>
</li>
<li>Don’t use long sentences</li>
<li>Don’t be too colloquial, too formal, or too emotional</li>
<li>Counts and uncounts
<ol>
<li>A few, a number of, fewer</li>
<li>less, lower</li>
</ol>
</li>
<li>Oxford Dictionary of English, Thesaurus</li>
<li>Typeset your paper correctly and beautifully</li>
<li>draw.io</li>
</ol>
<h1 id="write-good-papers-fast">Write good papers FAST</h1>
<p>$\max Q(p) \text{ s.t. } t(p) \le T$</p>
<p>Maximize the quality of your paper, subject to deadline constraint</p>
<h2 id="know-your-deadline">Know your deadline</h2>
<ol>
<li>Work towards your deadline</li>
<li>Set your dealine realistically, 1-3 months.</li>
</ol>
<h2 id="allocate-your-time-well">Allocate your time well</h2>
<ol>
<li>Think seriously why you miss your mileatone deadlines.</li>
<li>Don’t procrastinate and delay all the work to the days before deadline.</li>
</ol>
<h2 id="dont-follow-be-the-lead">Don’t follow, be the lead</h2>
<ol>
<li>Start your team at the begining of your project</li>
<li>Only invite <strong>trustworthy</strong> collaborators when building your team</li>
<li>Get them to commit their time</li>
<li>Warn them the <strong>though</strong> work ahead along the way</li>
<li>Promise them an <strong>exciting</strong> outcome</li>
<li>Remind them about <strong>their</strong> milestone <strong>deadlines</strong> often</li>
<li><strong>Persist</strong> if they forget about your requests</li>
<li><strong>Cancel</strong> thier membership if they consistently fail</li>
<li>Have <strong>backup plans</strong></li>
</ol>
<h2 id="choose-a--problem-with-the-right-size">Choose a problem with the right size</h2>
<ol>
<li>It must be <strong>feasible</strong> to be completed <strong>before deadline</strong></li>
<li><strong>Goal</strong>: make <strong>solid improvments</strong> over one paper, and <strong>one</strong> paper only</li>
<li>Choose a paper you <strong>enjoy</strong> reading; But if it may take a long time, <strong>give up</strong> and choose choose another paper</li>
<li>Know your problem and pick ahead of time the conference where your paper’s scope fits into</li>
</ol>Xutong Liuliuxt@cse.cuhk.edu.hkMy personal notes on writing. Keep updating…Misc2022-10-10T00:00:00-07:002022-10-10T00:00:00-07:00https://liuxt.github.io/posts/2022/10/Misc<p>Temporary notes.</p>Xutong Liuliuxt@cse.cuhk.edu.hkTemporary notes.Future Blog Post1999-01-01T00:00:00-08:001999-01-01T00:00:00-08:00https://liuxt.github.io/posts/2012/08/future-post<p>This post will show up by default. To disable scheduling of future posts, edit <code class="language-plaintext highlighter-rouge">config.yml</code> and set <code class="language-plaintext highlighter-rouge">future: false</code>.</p>Xutong Liuliuxt@cse.cuhk.edu.hkThis post will show up by default. To disable scheduling of future posts, edit config.yml and set future: false.