comp-physics / group-docs Goto Github PK

things worth adding

• be specific with references to sections and figures
• many quotes to the new text that was added to address reviewer concerns (these should be in a different color than the main reply)
• be deferent to the reviewer unless there is a very good reason not to be. many issues can be solved by simply agreeing with the reviewer, thanking them for the comment, and correcting the manuscript accordingly.
  • if the reviewer is explicitly and clearly wrong and misunderstanding the paper, this is on you - perhaps you should have been more clear in your exposition! You should apologize for any confusion, clarify what you really meant, and then bolster that part of the paper with references, discussion, and clarity. include all of this in your reply to them!
• This is a formal document. Treat it as such. Do not be lax with your grammar or writing broadly.
• Notice when the reviewer notices something important and thank them for it!

Add paragraph about seminar expectations.

• CSE seminar
• short and sweet seminar

• use of bibtools/bibstyle

• bibliography style files

• what to include/not include in your bib entries

• what certain things do (like the tilde) and other important packages (microtype for example)

• use of macros for math

• use of \citet

• the importance of figure 1

• acknowledgments in the last section

• abstract (what it should and should not include)

• intro (what it should and should not include)

• future work (what should or should not be included)

• common writing pitfalls (extra [unnecessary] words and phrases people often use)

• learn the difference between hyphen, en dash, and em dash

• Make sure documents do not compile with errors (overleaf) and understand where the warnings come from

• Tikz figures compile standalone

• Use of git with Overleaf

Formatting, slides, etc.

Some random things on my mind

Slides themselves

• Page/slide numbers
• References and how to include them
• Amount of text per slide
• Consistency
• Examples of good/bad slides
• Table of contents (when to have / not have)
• How to include figures
• Final slide(s): Acknowledgment/"Questions?"
• So little text that you don't need bullet points!
• All text should be super readable, almost cartoonishly large
• Less is more (overall and per slide)
  • Related: information density per slide

Presentation

• Bring a pointer
• Avoid speaking in second person (teach)

Refs
https://www.seckington.com/the-art-of-slide-design-maximise-signal-minimise-noise/

Need documentation on how to go about traveling to conferences.

includes:

• workday spend authorization (with worktag #) for grad students
• hotels/flights (stay at conference-subsidized hotel)
• When to pair-up with someone
• Registration (always get early registration)
• link to PURA Travel for undergrads (done)

Need links and guidelines for PURA Salary and Travel.

How to include figures from other people/papers in your talks and papers.

Add note about 2d paraview plots and lighting - link to @wilfonba's document.

Add relevant info on student hardware

• "who" owns it
• how it is paid for
• what we usually order
• etc

wip

Need

• document on responding to journal reviews.
• template

Need a document on how to do research as an undergraduate.

includes

• hours "expected"
• turn around time before journal/conference paper
• when/where of working
• internships
• grad school options

Create a document directing UG and Graduate students to a template of some kind that outlines expectations and helps plan research in the short and long term.