\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{natbib}




\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
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

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



\usepackage{float}








\begin{document}

\title{Science Storms the Cloud}



\author[1,1,1,1]{Chelle Leigh Gentemann}%
\author[2,2,2,2]{Chris Holdgraf}%
\author[3,3,3,3]{Ryan Abernathey}%
\author[4,4,5,5]{Daniel Crichton}%
\author[2,2,2,2]{James Colliander}%
\author[6,6,6,6]{Edward Joseph Kearns}%
\author[2,2,2,2]{Yuvi Panda}%
\author[7,7,7,7]{Richard P. Signell}%
\affil[1]{Farallon Institute}%
\affil[2]{2i2c}%
\affil[3]{Columbia University}%
\affil[4]{Jet Propulsion Laboratory, NASA}%
\affil[5]{Jet Propulsion Laboratory}%
\affil[6]{First Street Foundation}%
\affil[7]{United States Geological Survey}%


\vspace{-1em}



  
  \date{May 25, 2024}


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





\selectlanguage{english}
\begin{abstract}
The core tools of science (data, software, and computers) are undergoing
a rapid and historic evolution, changing what questions scientists ask
and how they find answers. Earth science data are being transformed into
new formats optimized for cloud storage that enable rapid analysis of
multi-petabyte datasets. Datasets are moving from archive centers to
vast cloud data storage, adjacent to massive server farms. Open source
cloud-based data science platforms, accessed through a web-browser
window, are enabling advanced, collaborative, interdisciplinary science
to be performed wherever scientists can connect to the internet.
Specialized software and hardware for machine learning and artificial
intelligence (AI/ML) are being integrated into data science platforms,
making them more accessible to average scientists. Increasing amounts of
data and computational power in the cloud are unlocking new approaches
for data-driven discovery. For the first time, it is truly feasible for
scientists to bring their analysis to data in the cloud without
specialized cloud computing knowledge. This shift in paradigm has the
potential to lower the threshold for entry, expand the science
community, and increase opportunities for collaboration while promoting
scientific innovation, transparency, and reproducibility. Yet, we have
all witnessed promising new tools which seem harmless and beneficial at
the outset become damaging or limiting. What do we need to consider as
this new way of doing science is evolving?%
\end{abstract}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

