Put text in separate directory

This commit is contained in:
Manos Katsomallos 2021-07-17 18:48:05 +02:00
parent 9b45f4af9a
commit 4fe2b59f30
12 changed files with 155 additions and 4 deletions

151
.gitignore vendored
View File

@ -1,3 +1,5 @@
# Latex
## Core latex/pdflatex auxiliary files:
*.aux
*.lof
@ -229,6 +231,153 @@ TSWLatexianTemp*
build
# ignore pdf files in root folder
/*.pdf
/text/*.pdf
# Python
# Byte-compiled / optimized / DLL files
__pycache__
*.py[cod]
*$py.class
# C extensions
*.so
# Distribution / packaging
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec
# Installer logs
pip-log.txt
pip-delete-this-directory.txt
# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/
cover/
# Translations
*.mo
*.pot
# Django stuff:
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal
# Flask stuff:
instance/
.webassets-cache
# Scrapy stuff:
.scrapy
# Sphinx documentation
docs/_build/
# PyBuilder
.pybuilder/
target/
# Jupyter Notebook
.ipynb_checkpoints
# IPython
profile_default/
ipython_config.py
# pyenv
# For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# .python-version
# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
#Pipfile.lock
# PEP 582; used by e.g. github.com/David-OConnor/pyflow
__pypackages__/
# Celery stuff
celerybeat-schedule
celerybeat.pid
# SageMath parsed files
*.sage.py
# Environments
.env
.venv
env/
venv/
ENV/
env.bak/
venv.bak/
# Spyder project settings
.spyderproject
.spyproject
# Rope project settings
.ropeproject
# mkdocs documentation
/site
# mypy
.mypy_cache/
.dmypy.json
dmypy.json
# Pyre type checker
.pyre/
# pytype static type analyzer
.pytype/
# Cython debug symbols
cython_debug/
# Misc
.DS_Store
*.class
*.vscode
.gradle

View File

@ -33,7 +33,7 @@
\setlength{\emergencystretch}{3em}
\hbadness=99999
\graphicspath{{graphics/}}
\graphicspath{{../graphics/}}
\DeclareGraphicsExtensions{.pdf, .png}
\definecolor{material_red}{HTML}{d50000}
@ -51,6 +51,8 @@
\newcommand{\thethings}{\thething s}
\newcommand{\Thethings}{\Thething s}
\newcommand*\includetable[1]{\input{../tables/#1.tex}}
\newtheorem{definition}{Definition}
\newtheorem{example}{Example}[section]
\newtheorem{proposition}{Proposition}

View File

@ -9,7 +9,7 @@ of the following works assume that data sets are privacy-protected \emph{indepen
On the other side, algorithms that are based on differential privacy are not concerned with so specific attacks as, by definition, differential privacy considers that the adversary may possess any kind of background knowledge.
Later on, data dependencies were also considered for differential privacy algorithms, to account for the extra privacy loss entailed by them.
\input{tables/table-micro}
\includetable{table-micro}
\subsection{Finite observation}

View File

@ -5,7 +5,7 @@ When continuously publishing statistical data, usually in the form of counts, th
In theory differential privacy makes no assumptions about the background knowledge available to the adversary.
In practice, as we observe in Table~\ref{tab:statistical}, data dependencies (e.g.,~correlations) arising in the continuous publication setting are frequently (but without it being the rule) considered as attacks in the proposed algorithms.
\input{tables/table-statistical}
\includetable{table-statistical}
\subsection{Finite observation}