My Mathematics PhD research workflow: LaTeX notes and instant pdf referencing
castel.dev
castel.dev
Downloading the LaTeX source also has the advantage that you can see the comments the authors made that don't show in the pdf version. Sometimes appalling: "% Author 1: Is this lemma even true? This proof seems like bs to me % Author 2: Eh screw it who knows, it's probably true."
This is the perception non-IT-people have of PDF in comparison to e.g. .docx or similar editable formats those people know.
Perhaps we should move to sandboxed webpages embedded within electron, where each paper is its own page?
To me, the place for the real time savings is organizing your teaching workflow. If you're a grad student, make sure to get on top of that ASAP. A lot of it is very repetitive both within a given semester and also from year to year. I have a ton of scripts built up over the years for things like organizing lecture notes (especially if you are teaching a class you have taught before, you don't want to have to rewrite all your lectures), creating problem sets / solutions, inputting grades into the LMS,... I even have automatic solution generators for a few rote calculations that I assign many problems about (Gaussian elimination, for example).
paper, like.. pieces of paper.. yes, that is old-fashioned! however, in deep math, maybe this is something.. I was told after attending a world-class lecture week in pure math, that it is common for PhDs and post-docs in math to have very little to talk about between each other.. since their interest and subject area is almost certainly deeply buried in some specialty. Aside from the quip "all roads lead to cryptography" perhaps just an excuse for certain people, I can see how this "different worlds" problem in post-doc math might be real..
The fellow writing this post is first-year however.. maybe its different.. Also I just cloned and built pdfgrep .. I am definitely going to try that out immediately .. thx!
I keep questions, slides, written notes, etc. controlled and semester-specific things in a directory that isn't tracked.
It really is amazing how hard it is just to retrieve the currently opened pdf file and its page number in a pdf viewer. Some pdf viewers (Like Zathura) provide this via DBus, but even very common ones like Evince don't. I managed to find a way using gvfs, although it's a bit of a hack.
For others (e.g. Mendeley), I have no idea on how to do this... Anybody have ideas? it is Qt based, maybe I can hook into that via some debugging tool?
https://emacsconf.org/2021/talks/research/
Your old post with instantly rendering latex snippets actually inspired me to start using vim/LaTeX. This opened up a whole new world for me. I started programming, got back into my engineering degree, started using emacs/org-mode and have nearly finished the degree. Thank you, from the bottom of my heart. I don’t know what I’d be doing if I hadn’t seen your post. It revealed a way of using computers that I had never seen before.
For organizing a personal library of academic papers, use Zotero, which has a great interface for sorting the papers, annotating the PDFs, and exporting them as BibTeX. (It would presumably be harder to get the OP's single-click PDF links working, though.)
In particular, the Scite add-on for Zotero can also tell you which other papers have cited the the paper you are reading in a supporting way vs. a disputing ("contrasting") way, which is really cool.
https://medium.com/scite/introducing-the-scite-plug-in-for-z...
I personally find LaTeX a little too friction-full (is that a word?) on the input side. The output looks beautiful but the lack of feedback when writing stuff keeps me from actually adding stuff to it. Although your daily notes seems like it might help with this tendency a little bit.
This is a problem I'm currently trying to solve with my current project (https://topictrails.com/ if you're interested).
And that's excluding Word line-breaking which always looked rather poor to me: some lines were left very empty and others overcrowded. It just didn't look professional to me. Perhaps that was been fixed too.
It's a personal preference, but I think it easily beats the typical LaTeX workflow for most people I know, which starts with copying an old project or some template with a ~50 line preamble and then constantly having to turn to Google for literally anything that's a bit out of the ordinary - including a lot of things that really shouldn't be extraordinary for a math software, like typesetting optimization problems, conditional expectation, argmin, table footnotes,... all of which have multiple options and most don't look great. Heck, you even need to define a theorem environment manually in the preamble to get them to look like you're used to.
Since you complain about moving around figures, in LaTeX the workflow for most users is trial-and-error multiple option combinations to get them roughly where you want them. Just check the Google autocomplete options for latex and tell me that people aren't confused by those things.
Anything becomes easy if you practice it enough, but I find both the 'onboarding' as well as the 'steady-state' productivity higher in Word, because you spend next to no time looking for how stuff works and instead focus on your content. Yes, LaTeX formatting generally looks better (eg spacing, LaTeX even lets you adjust the spacing between individual characters), but looks come second to content imho.
https://github.com/ahrm/sioyek
Disclaimer: I am the developer of sioyek
[1]: https://zealdocs.org
Probably possible to convert pdfs to html (with the default pdf tools on nix - pdftotext pdf2txt et al) and pull them into zeal.
I just started using the iPad to make handwritten notes. What I really want is a way for the handwritten stuff to be integrated into a knowledge graph, or even automatically generating tex/diagrams for me.
On top of that, daily scribbles don’t necessarily go anywhere, or are even wrong, so it can generate noise anyway. What was more valuable was consolidating a few weeks+ of progress into a more complete summary or set of notes. You can still explain the reasoning of how you got to something finished, but it’s just all correct.
As for writing documents with lots of math, absolutely no problem. I can churn that our faster than peers can with Word.
The second best is to look for a similar figure on TeXample https://texample.net/tikz/examples/ or stack overflow https://tex.stackexchange.com/questions/tagged/tikz-pgf
The third best option is to use squared paper to draw by hand, then transfer hand-drawn stuff into TikZ code. It's slow as hell, but works well if you build up a collection of components you can copy-paste into other figs later.
There are also some GUI tools you could try: https://www.mathcha.io/ https://homepages.inf.ed.ac.uk/cheunen/freetikz/freetikz.htm... https://tikzit.github.io/ etc. (more links in this thread https://tex.stackexchange.com/questions/84890/does-there-exi... )
I am more looking for tips and tricks that have helped people build their skills and streamline the process.
The advantage of working at the university of Lübeck: his office is next to my office.
If he writes me a snippet, I just copy paste it.
Let's say in undergraduate I would say: Calculus I - understand what is derivative. Calculus II - understand what is an integral.
Math is broad, so maybe 1 or 2 takeaways from some topics in upper division math that I might find useful.
- Multiple linear equations over the rationals/reals => linear algebra
- Solve equations over the integers / integers mod p / factor numbers => number theory
- Solve polynomial equations / factor polynomials => algebra
- (Partial) differential equations => (partial) differential equations
- Approximate solutions to various equations over the reals => numerical analysis
- Counting the sizes of various finite sets => combinatorics
- Integrate wild functions => measure theory
- Formal understanding of real numbers => real analysis
- General framework for differential equations => functional analysis
- General framework for continuous functions and limits => point-set topology
- Prove that two elastic shapes are different => algebraic topology
- Prove that a knot in a circular piece of string cannot be untied without cutting the string => knot theory
- Determine optimum strategy in a game with incomplete information => game theory
- Describe very big sets / prove that certain things can't be proved => set theory
- etc.
The thing about math is that regardless of which field you work in the treatment is the same. You start by stating a set of axioms. Based on these axioms you set up definitions and then prove lemmas, corrolaries and theorems. This approach isn't really necessary or directly useful for computer science though. But it is very beautiful. For example, if you truly want to appreciate, in it's full force, why a player playing a fair game against a casino will always eventually lose (theorem called Gambler's ruin) you can study stochastic processes with full rigour (this is also a very useful area). But that full rigour isn't necessary to not blow your savings on games of chance :)