Addressed Colin Slater's comments. Rotated caption to match Figure 4.

lsst-dmsst · Apr 5, 2019 · 2af3ec3 · 2af3ec3
1 parent 0631deb
commit 2af3ec3
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/LSE-319.tex b/LSE-319.tex
@@ -1,4 +1,5 @@
 \documentclass[SE,toc,lsstdraft]{lsstdoc}
+\usepackage{rotating}
 
 %% Journal abbreviations
 

diff --git a/user.tex b/user.tex
@@ -42,7 +42,7 @@ \subsection{Portal Aspect\label{sec:portal}}
 
 \subsection{Notebook (JupyterLab) Aspect\label{sec:jupyter}}
 
-\begin{figure}
+\begin{sidewaysfigure}
 	\centering
 	\scalebox{0.6}{\includegraphics[scale=0.9]{images/fig-notebook-imagequality}}
 	\caption{A screen capture of the Notebook interface running LSST image processing code within a notebook. \label{fig:JupyterLab}}
@@ -125,7 +125,7 @@ \subsection{Integrated environment}
 
 As an example of how these connections can aid a user in exploring the LSST data, data queries will be shareable across the Portal, Notebook, and Web API Aspects.
 This will allow a user to build a query using the Portal's TAP query UI component, view the (possibly preliminary) results by browsing them in place in the Portal, and then access the final results from a JupyterLab notebook or a remotely connected client (e.g., TOPCAT) for further analysis.
-The reverse flow will also be enabled; a user can code and submit a complex SQL query in the Notebook, and then browse and visualize the results in the Portal.
+The reverse flow will also be enabled; a user can code and submit a complex ADQL query in the Notebook, and then browse and visualize the results in the Portal.
 
 By making the environments integrated, we allow for a shallower learning curve and a gradual transition to more complex environments at the point they are needed.
 For example, a user may begin interacting with the LSST dataset using the Portal Aspect but may ultimately reach the limitations of the selection and analysis tools it provides.