Layout improvements for etable, in particular for LaTex output

[dsliwka]

Changes to generate publication-ready LaTex Tables:

• Use of MultiIndex for column heads
• Allow custom model headlines
• Allow custom table notes
• Improved LaTex output

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[s3alfisc]

Thank you Dirk (@dsliwka)! The examples look phenomenal. I'll review this over the weekend =)

On the testing error - I think it is obsolete now because we are now supporting "tex" with the "\n" command (this was not the case before).

        with pytest.raises(ValueError):
>           etable([fit1, fit2], coef_fmt="b (se)\nt [p]", type="tex")
E           Failed: DID NOT RAISE <class 'ValueError'>

[s3alfisc]

Got the tex to run! Looks super nice:

[codecov]

Codecov Report

Attention: Patch coverage is 90.98361% with 11 lines in your changes missing coverage. Please review.

Files	Patch %	Lines
pyfixest/report/summarize.py	90.09%	11 Missing ⚠️

Files	Coverage Δ
tests/test_errors.py	98.89% <ø> (+1.80%)	⬆️
tests/test_summarise.py	94.20% <100.00%> (-5.80%)	⬇️
pyfixest/report/summarize.py	93.70% <90.09%> (ø)

... and 26 files with indirect coverage changes

[dsliwka]

Thanks for the feedback @s3alfisc! I have added the print_tex option & extended the documentation in the Stargazer notebook. Initially I had set the default option for print_tex=True but then realized that this may have unwanted side-effects. For instance, for pdf rendering to work in quarto the table must apparently be printed in the respective code chunk. When print_tex=True the pdf not only includes the table but also the latex code.

[dsliwka]

I apologize @s3alfisc for the confusion I cause! Apparently the issue is caused by including a quarto example. I first had it in the Stargazer notebook. I had hoped to solve the issue by taking this out and just adding a sample qmd file and the resulting pdf. But apparently some code is running which tries to render the respective document to pdf and then misses a TeX installation. Is it possible to just keep the document as an example in the repository without having it automatically rendered? Otherwise I can of course simply erase it and take out the respective description in the Stargazer notebook.

[s3alfisc]

Hi @dsliwka, no worries at all! Looks indeed like quartodoc by default runs the QuartoExample.qmd. I have now added a section to the github action to install tinytext and the docs now build properly! Do you want to try to include the quarto part into the stargazer.ipynb again? Either way, I think this is pretty close to being ready to be merged =)

[dsliwka]

Thanks @s3alfisc! I think it is perfectly fine to stick to the sample document.
When looking at the output again today I added two small features: the possibility to hide the fe and standard error type rows (this allows the user to describe both in the table notes when they are the same for all models) and the possibility to add further custom model information or statistics at the bottom of the table.

[s3alfisc]

Hi Dirk, thank you! All of this looks outstanding, and I am more than happy to merge this later today. The etable() functionality and aesthetics have improved a lot, thank you so much!