\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage[natbibapa]{apacite}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[ngerman,english]{babel}










\begin{document}

\title{Big Data Astronomy}



\author[1]{Josh Peek}%
\affil[1]{Space Telescope Science Institute}%


\vspace{-1em}



  
  \date{May 26, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup








\sloppy


Hey, welcome. Double click anywhere on the text to start writing. In addition to simple text you can also add text formatted in \textbf{boldface}, \textit{italic}, and yes, math too: $E  =  mc^{2}$! Add images by drag'n'drop or click on the "Insert Figure" button.


Okay here are some ideas that might go in this paper:

\begin{itemize}
\tightlist
\item
  \textbf{Geert's tech progress}
\end{itemize}

I'd want to add in home internet DL law, and define a raw data rate /
data download rate unitless parameter (epsilon? ??) for each of these
telescopes. Should we have radio data in here too, just to show that it
is massively accelerating? We could also talk about space physical
limitations -- bandwidth from L2 does not scale based on how many people
want to watch 4K videos from their phone.

\begin{itemize}
\tightlist
\item
  \textbf{Implications}
\end{itemize}

A major implication at ST is ``what it means to bring software to the
data''. Everyone and their mother is making some kind of ``science
cloud'', but that seems ill considered to me \emph{if} it is based on
the value of ? for optical astro which is declining. Makes sense for
LOFAR, and ASKAP of course.

\begin{itemize}
\tightlist
\item
  \textbf{The role of theory}
\end{itemize}

This all has gotten me thinking about theory and simulation. Simulations
are the ultimate big data as they are bounded in data volume only by the
data computers can produce, so they scale directly with `tech progress',
though this needs to be further worked out. Molly's ``Mocking the
Universe'' workshop put this into stark relief for me, and my work with
WFIRST has made me realize that many physics-like astro experiments --
BAO, weak lensing, SN cosmology, HI reionization -- need very high
throughput \emph{data simulations} to take advantage of the data sets
they use. So that the real bottleneck for doing science with ``big
data'' is the simulations of the universe, instrument, and data
reduction that need to go into an (essentially) Monte Carlo of what you
expect from your big survey given a cosmology (or popuation statistic,
or whatever)

\begin{itemize}
\tightlist
\item
  \textbf{The Mobile Environment}
\end{itemize}

This realization is what motivated what is (was?) called the ``Personal
Science Archive'' in the WFIRST concept. The idea started out as a
generic science cloud, but I quickly realized that wasn't going to cut
it. We needed two things -- a real instrument simulator and a way for
people to get their data to said simulator. This is where the mobile
environment becomes important. Normally, we think of ``bringing the
software to the data'' as bringing your python data reduction or
analysis code to some astronomy database, but we can flip the idea on
its head. Instead, bring the entire data management environment of an
instrument or survey to the simulation code by packaging it in an
instantiatable environment and plopping it onto whatever supercomputer
the theorists are using to make their fake universes. This is both
``bigger'' software and bigger data.

Citing other papers is easy. Voil\selectlanguage{ngerman}à: \cite{2012} or \cite{Holstein_2009}. Click on the \verb|cite| button in the toolbar to search articles and cite them. Authorea also comes with a powerful commenting system. Don't agree that $E  =  mc^{3}$?!? Highlight the text you want to discuss or click the comment button. Find out more about using Authorea on \href{https://www.authorea.com/help}{our help page}.

\selectlanguage{english}
\FloatBarrier
\bibliographystyle{apacite}
\bibliography{bibliography/converted_to_latex.bib%
}

\end{document}

