4 ms·
It is not about the table, but the placing of the table. If you want a table that spans both columns in a double column document, it is annoying to do it in wor
by tapia 7y ago
It is not about the table, but the placing of the table. If you want a table that spans both columns in a double column document, it is annoying to do it in word, while in LaTeX it is as easy as \begin{table*}. Creating a content of a table is something different, and there are multiple approaches. I normally need result from python scripts, so I just export my results to latex format with pandas.
- godelski 7y agoUse minipages. I completely understand where you're coming from. But once I started using minipages I found that it is a great way to hack around almost all of these weird and uncommon placement issues.
- patrick5415 7y agoThe ability to have your simulation code automatically update the data and figures in the manuscript is hugely valuable. Another neat trick is a latex package called Catchfilebetweentags. This let’s you have a text file with named data fields that you can insert into your document, like when you want to state a parameter that was used in a paragraph. Generating that text file as an artifact of the rest of the data processing means, e.g., that parameters my paper says I used are the ones that I actually used.
- BeetleB 7y ago>so I just export my results to latex format with pandas. In other words, you don't do it by hand. I too rely on a tool to create my tables, which was my point. Doing it by hand is painful.