模版集 - 用LaTeX编写的模板、示例和文章

Template for abstract submission of the LPAW 23 conference. Based on a template from F. Cruz and F. Del Gaudio for other conferences.

T. Silva

University of South Florida (USF) Letterhead - November 1st, 2022

A LaTeX reconstruction of the USF official letterhead template (given in a Word document), as of November 1st, 2022.

Gene Louis Kim

Minkowski Spacetime Diagram Generator

Generates a Minkowski spacetime diagram with a given grid spacing, grid cell count, and velocity as a proportion of c.

Justin Babilino

IPGP-Letters-FromMid2022

Gabarit pour des lettres IPGP avec les nouveaux logos de 2022

G. Moguilny

IEEE ITherm Conference Template

This demo file is intended to serve as a "starter file'' for IEEE ITherm conference papers produced under LaTeX. This is one of a number of templates using the IEEE style that are available on Overleaf to help you get started - use the tags below to find more.

Jack Maddox (john.maddox@uky.edu)

Research Diary Template

Doing research and not getting lost in the nitty gritty details or becoming a master procrastinator can be hard sometimes. A research diary or journal, which helps you documenting your progress, feelings and learnings, can have a big impact on your research success. After reading a lot about journaling during a PhD I went about searching for a clean and simple latex template that would help me to get started. However, I only found either classic lab reports or overly complicated solutions. Thus, I set up my own document that provides a basic structure for doing daily journaling and also assists with reviewing one's progress on a weekly basis. This template is as easy as it gets. This is the whole purpose of this template - to facilitate your setup of your own research diary! How to contribute: If you wish to contribute to this repository - e.g. adding new languages or making this rudimentary template a bit more fancy -, you are welcome to do so! Just fork the repository (https://github.com/SimonHashtag/research_diary_latex_template) and propose your changes via a pull request. Please add sufficient documentation so that the changes are traceable and understandable.

Simon Haastert