.config.org

+# ################################################################################
+# ################################################################################
+# Description: org config to be shared across different org files.
+#
+# Usage: Place this in your org file header.
+#
+# #+SETUPFILE: ../.config.org
+# #+TITLE: Your title
+# #+SUBTITLE:
+# #+DATE: <2023-03-08 Wed>
+# #+ARCHIVE: your-filename_archive.org::
+# #+OPTIONS: audo-id:t
+#
+# ################################################################################
+#
+# Side notes.
+# ##########
+#
+#
+# Org-mode Export LaTeX Customization Notes:
+# - Interpret 'bla_bla' as LaTeX Math bla subscript bla: #+OPTIONS ^:t. Interpret literally bla_bla: ^:nil.
+# - org export: turn off heading -> section numbering: #+OPTIONS: num:nil
+# - org export: change list numbering to alphabetical, sources:
+#   - https://orgmode.org/manual/Plain-lists-in-LaTeX-export.html
+#   - https://tex.stackexchange.com/a/129960
+#   - must be inserted before each list:
+#     #+ATTR_LATEX: :environment enumerate
+#     #+ATTR_LATEX: :options [label=\alph*)]
+# - allow org to recognize alphabetical lists a)...: M-x customize-variable org-list-allow-alphabetical
+#
+#
+#
+# # In Emacs org-mode: before exporting, comment this out START
+# ;; Local Variables:
+# ;; ispell-check-comments: exclusive
+# ;; ispell-local-dictionary: "english"
+# ;; End:
+# # In Emacs org-mode: before exporting, comment this out FINISH
+# ################################################################################
+# ################################################################################
+
+
+
+# -----------------------
+# General Export Options:
+#+OPTIONS: ^:nil ':nil *:t -:t ::t <:t H:3 \n:nil arch:headline
+#+OPTIONS: broken-links:nil c:nil creator:nil d:(not "LOGBOOK") date:t e:t
+#+OPTIONS: f:t inline:t p:nil pri:nil prop:nil stat:t tags:t
+#+OPTIONS: tasks:t tex:t timestamp:t title:t todo:t |:t
+
+#+OPTIONS: author:Johannes Wasmer
+#+OPTIONS: email:johannes.wasmer@gmail.com
+#+AUTHOR: Johannes Wasmer
+# #+EMAIL: johannes.wasmer@gmail.com
+#+LANGUAGE: en
+#+SELECT_TAGS: export
+#+EXCLUDE_TAGS: noexport
+#+CREATOR: Emacs 28.2 (Org mode 9.6.1)
+
+
+# for org for web (eg gitlab, github): num:nil, toc:nil. using custom Table of Contents below.
+# for tex/pdf export, temporarily: num:t, toc:t. replace * Table of Contents -> * COMMENT Table of Contents.
+#+OPTIONS: num:nil
+# t or nil: disable export latex section numbering for org headings
+#+OPTIONS: toc:nil
+# t or nil: no table of contents (doesn't work if num:nil)
+
+# ---------------------
+# LaTeX Export Options:
+#+LATEX_CLASS: article
+#+LATEX_CLASS_OPTIONS:
+#+LATEX_HEADER: \usepackage[english]{babel}
+#+LATEX_HEADER: \usepackage[top=0.5in,bottom=0.5in,left=1in,right=1in,includeheadfoot]{geometry} % wider page; load BEFORE fancyhdr
+#+LATEX_HEADER: \usepackage[inline]{enumitem} % for customization of itemize, enumerate envs
+#+LATEX_HEADER: \usepackage{color}
+#+LATEX_HEADER: \usepackage{bm} % bold math. prefer \bm over \mathbf. also works with Greek symbols.
+#+LATEX_HEADER: \usepackage{mathtools}
+#+LATEX_HEADER: \usepackage{amsmath}
+#+LATEX_HEADER: \usepackage{siunitx} % SI units
+# #+LATEX_HEADER: \usepackage{mchem} % chemical formulae % commented out, crashed org-latex-preview 2023-09-24
+#+LATEX_HEADER: \usepackage{braket} % dirac braket notation, prefer over physics package https://tex.stackexchange.com/a/214731
+#+LATEX_HEADER: % override 'too deeply nested error'
+#+LATEX_HEADER: % reference: https://stackoverflow.com/a/13120787
+#+LATEX_HEADER: \usepackage{unicode-math}
+#+LATEX_HEADER: % unicode-math for math double prime etc. ref. https://tex.stackexchange.com/a/210300
+#+LATEX_HEADER: % note: unicode-math only works with unicode-LaTeX compiler (XeTeX, LuaTeX), pdflatex won't work.
+#+LATEX_HEADER: \usepackage{enumitem}
+#+LATEX_HEADER: \setlistdepth{9}
+#+LATEX_HEADER: \setlist[itemize,1]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,2]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,3]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,4]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,5]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,6]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,7]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,8]{label=$\bullet$}
+#+LATEX_HEADER: \setlist[itemize,9]{label=$\bullet$}
+#+LATEX_HEADER: \renewlist{itemize}{itemize}{9}
+#+LATEX_HEADER:
+#+LATEX_HEADER_EXTRA:
+#+DESCRIPTION:
+#+KEYWORDS:
+#+LATEX_COMPILER: pdflatex
+
+# auto-id: get export-safe org-mode headline IDs
+# References:
+# - web: https://writequit.org/articles/emacs-org-mode-generate-ids.html
+# - local:
+#   - Emacs Config Notes > get export-safe org-mode headline IDs
+#   - emacs dotfile > =JW 220419 org-mode headlines CUSTOM_ID=
+# Notes:
+# - this property is not inherited through #+SETUPFILE: ...
+#+OPTIONS: auto-id:t
+
+# --------------------
+# Agenda Config.
+# Notes:
+# - tags:
+#   - :TOC: automatic table of contents generation via https://github.com/snosov1/toc-org.
+#     (Note: this is for org/markdown etc. For latex/html export, prefer #+OPTIONS: toc:t.)
+
+# TODO keywords default.
+#+TODO: TODO(1) NEXT(2) DOING(3) WAITING(4) ONHOLD(5) POSTPONED(6) SHELVED(7) | DONE(0) MOVED(8) ABANDONED(9) FAIL
+
+# # Tags default.
+# #+TAGS: URGENT(0) PRIO1(1) PRIO2(2) PRIO3(3) ADMIN(a) CODING(c) WRITING(w) TOC(t)
+
+# Tags phd-project-wasmer main
+#+TAGS: [ org : TOC(t) ]
+#+TAGS: [ project : wasmer judft collab rse ]
+#+TAGS: [ wasmer : theo data code rep ops doc mgmt side ]
+#+TAGS: [ theo : phys dft aml ml ]
+#+TAGS: [ data : sidb(1) didb(2) aii ]
+#+TAGS: [ code : jij(3) vimp(4) dsm(5) ]
+#+TAGS: [ ops : pack man it ]
+#+TAGS: [ doc : notes(6) pres(7) prom pub(8) ref dsm(9) ]
+#+TAGS: [ judft : jutools kkr spirit fleur masci iffaii ]
+#+TAGS: [ collab : pis tip aidas casus cosmo daemon tcd contact ]
+#+TAGS: [ admin : pgi helm fzj rwth fund ]
+#+TAGS: [ pgi : office teach ]
+#+TAGS: [ event : meet conf sem tut ]

.gitattributes

+*.odt filter=lfs diff=lfs merge=lfs -text
+*.odp filter=lfs diff=lfs merge=lfs -text
+*.pptx filter=lfs diff=lfs merge=lfs -text
+*.tar.gz filter=lfs diff=lfs merge=lfs -text
+*.xlsx filter=lfs diff=lfs merge=lfs -text
+*.gif filter=lfs diff=lfs merge=lfs -text
+*.jpg filter=lfs diff=lfs merge=lfs -text
+*.pdf filter=lfs diff=lfs merge=lfs -text
+*.tar filter=lfs diff=lfs merge=lfs -text
+*.jpeg filter=lfs diff=lfs merge=lfs -text
+*.docx filter=lfs diff=lfs merge=lfs -text
+*.png filter=lfs diff=lfs merge=lfs -text
+*.svg filter=lfs diff=lfs merge=lfs -text
+*.zip filter=lfs diff=lfs merge=lfs -text
+*.html filter=lfs diff=lfs merge=lfs -text
+*.ods filter=lfs diff=lfs merge=lfs -text

.gitignore

+# # put this line in comment when presentation is finished
+# # (no need to clutter repo history with intermediate slides PDFs)
+**/presentation.pdf
+
+# emacs gitignore (_region_: auctex preview files)
+*.el
+_region_*
+
+# emacs org-mode latex preview tmp folder
+ltximg
+
+# MacOS files
+.DS_Store
+
+########################################################################
+########################################################################
+########################################################################
+
+# TeX Gitignore from https://github.com/github/gitignore/blob/master/TeX.gitignore.
+# Adapted slightly to this template, marked with # CHANGED.
+
+## Core latex/pdflatex auxiliary files:
+*.aux
+*.lof
+*.log
+*.lot
+*.fls
+*.out
+*.toc
+*.fmt
+*.fot
+*.cb
+*.cb2
+.*.lb
+
+## Intermediate documents:
+*.dvi
+*.xdv
+*-converted-to.*
+# these rules might exclude image files for figures etc.
+# *.ps
+# *.eps
+# *.pdf
+
+## Generated if empty string is given at "Please type another file name for output:"
+# CHANGED: do not ignore pdf
+# .pdf
+
+## Bibliography auxiliary files (bibtex/biblatex/biber):
+*.bbl
+*.bcf
+*.blg
+*-blx.aux
+*-blx.bib
+*.run.xml
+
+## Build tool auxiliary files:
+*.fdb_latexmk
+*.synctex
+*.synctex(busy)
+*.synctex.gz
+*.synctex.gz(busy)
+*.pdfsync
+
+## Build tool directories for auxiliary files
+# latexrun
+latex.out/
+
+## Auxiliary and intermediate files from other packages:
+# algorithms
+*.alg
+*.loa
+
+# achemso
+acs-*.bib
+
+# amsthm
+*.thm
+
+# beamer
+*.nav
+*.pre
+*.snm
+*.vrb
+
+# changes
+*.soc
+
+# comment
+*.cut
+
+# cprotect
+*.cpt
+
+# elsarticle (documentclass of Elsevier journals)
+*.spl
+
+# endnotes
+*.ent
+
+# fixme
+*.lox
+
+# feynmf/feynmp
+*.mf
+*.mp
+*.t[1-9]
+*.t[1-9][0-9]
+*.tfm
+
+#(r)(e)ledmac/(r)(e)ledpar
+*.end
+*.?end
+*.[1-9]
+*.[1-9][0-9]
+*.[1-9][0-9][0-9]
+*.[1-9]R
+*.[1-9][0-9]R
+*.[1-9][0-9][0-9]R
+*.eledsec[1-9]
+*.eledsec[1-9]R
+*.eledsec[1-9][0-9]
+*.eledsec[1-9][0-9]R
+*.eledsec[1-9][0-9][0-9]
+*.eledsec[1-9][0-9][0-9]R
+
+# glossaries
+# CHANGED: do not ignore some of the glossary files. will build locally,
+# then push to gitlab, and sharelatex will build from that. but
+# sharelatex probably can't build glossary files. so will give it the
+# readymade glossary auxialliary files from local build, then it should
+# work.
+*.acn
+*.acr
+# *.glg
+# *.glo
+# *.gls
+*.glsdefs
+*.lzo
+*.lzs
+
+# uncomment this for glossaries-extra (will ignore makeindex's style files!)
+# *.ist
+
+# gnuplottex
+*-gnuplottex-*
+
+# gregoriotex
+*.gaux
+*.glog
+*.gtex
+
+# htlatex
+*.4ct
+*.4tc
+*.idv
+*.lg
+*.trc
+*.xref
+
+# hyperref
+*.brf
+
+# knitr
+*-concordance.tex
+# TODO Uncomment the next line if you use knitr and want to ignore its generated tikz files
+# *.tikz
+*-tikzDictionary
+
+# listings
+*.lol
+
+# luatexja-ruby
+*.ltjruby
+
+# makeidx
+*.idx
+*.ilg
+*.ind
+
+# minitoc
+*.maf
+*.mlf
+*.mlt
+*.mtc[0-9]*
+*.slf[0-9]*
+*.slt[0-9]*
+*.stc[0-9]*
+
+# minted
+_minted*
+*.pyg
+
+# morewrites
+*.mw
+
+# newpax
+*.newpax
+
+# nomencl
+*.nlg
+*.nlo
+*.nls
+
+# pax
+*.pax
+
+# pdfpcnotes
+# *.pdfpc
+
+# sagetex
+*.sagetex.sage
+*.sagetex.py
+*.sagetex.scmd
+
+# scrwfile
+*.wrt
+
+# sympy
+*.sout
+*.sympy
+sympy-plots-for-*.tex/
+
+# pdfcomment
+*.upa
+*.upb
+
+# pythontex
+*.pytxcode
+pythontex-files-*/
+
+# tcolorbox
+*.listing
+
+# thmtools
+*.loe
+
+# TikZ & PGF
+*.dpth
+*.md5
+*.auxlock
+
+# todonotes
+*.tdo
+
+# vhistory
+*.hst
+*.ver
+
+# easy-todo
+*.lod
+
+# xcolor
+*.xcp
+
+# xmpincl
+*.xmpi
+
+# xindy
+# CHANGED: do not ignore xindy files. reason, see glossaries.
+# *.xdy
+
+# xypic precompiled matrices and outlines
+*.xyc
+*.xyd
+
+# endfloat
+*.ttt
+*.fff
+
+# Latexian
+TSWLatexianTemp*
+
+## Editors:
+# WinEdt
+*.bak
+*.sav
+
+# Texpad
+.texpadtmp
+
+# LyX
+*.lyx~
+
+# Kile
+*.backup
+
+# gummi
+.*.swp
+
+# KBibTeX
+*~[0-9]*
+
+# TeXnicCenter
+*.tps
+
+# auto folder when using emacs and auctex
+./auto/*
+*.el
+
+# expex forward references with \gathertags
+*-tags.tex
+
+# standalone packages
+*.sta
+
+# Makeindex log files
+*.lpz
+
+# xwatermark package
+*.xwm
+
+# REVTeX puts footnotes in the bibliography by default, unless the nofootinbib
+# option is specified. Footnotes are the stored in a file with suffix Notes.bib.
+# Uncomment the next line to have this generated file ignored.
+#*Notes.bib

.gitmodules

+[submodule "resources"]
+	path = resources
+	url = https://iffgit.fz-juelich.de/phd-project-wasmer/resources/latex-resources

README.md

-# 2025-02-26-how-to-research-visit
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://iffgit.fz-juelich.de/phd-project-wasmer/presentations/2025-02-26-how-to-research-visit.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://iffgit.fz-juelich.de/phd-project-wasmer/presentations/2025-02-26-how-to-research-visit/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

README.org

+* 2025-02-26-how-to-research-visit
+
+This repository contains a talk given in the HDS-LEE ([[https://www.hds-lee.de/][URL]]) coffee break, titled
+"How to Research Visit (And How Not To)", about Johannes Wasmer's reserach visit
+during his doctoral studies.
+
+[[file:presentation/presentation.pdf][Slides]].
+
+[[file:notes/speaking-notes.org][Speaking notes]].
+
+[[file:notes/how-to-research-visit-talk-notes.org][Development notes]].

resources @ b77470b7

+Subproject commit b77470b789cde8bf1732d6af327ac4f942f5dc4c