* docs/ref/uvh5_memo specify baseline direction

docs/references/uvh5_memo.tex

@@ -28,7 +28,8 @@
 \author{Paul La Plante, and the pyuvdata team}
 \date{November 28, 2018\\
 Revised April 2, 2021\\
-Revised July 14, 2022
+Revised July 14, 2022\\
+Revised April 17, 2024
 }
 
 \begin{document}
@@ -165,8 +166,10 @@ \subsection{Required Parameters}
 \item \textbf{Ntimes}: \textit{int} The number of time samples present in the
   data. (\textit{Ntimes})
 \item \textbf{uvw\_array}: \textit{float} An array of the uvw-coordinates
-  corresponding to each observation in the data. This is a two-dimensional array of
-  size (Nblts, 3). Units are in meters. (\textit{uvw\_array})
+  corresponding to each observation in the data. Baselines are specified as from
+  \verb+ant_1_array+ to \verb+ant_2_array+, implying the position of antenna 2
+  minus the position of antenna 1. This is a two-dimensional array of size
+  (Nblts, 3). Units are in meters. (\textit{uvw\_array})
 \item \textbf{time\_array}: \textit{float} An array of the Julian Date
   corresponding to the temporal midpoint of the corresponding baseline's
   integration. This is a one-dimensional array of size
@@ -274,7 +277,7 @@ \subsection{Required Parameters}
 	\end{itemize} (\textit{phase\_center\_catalog})
 \item \textbf{phase\_center\_id\_array}: \textit{int}
 A one dimensional array of length Nblts containing the cat\_id from the phase\_center\_catalog
-that each baseline-time is phased to. (\textit{phase\_center\_id\_array})
+that each baseline-time is phased to. \\(\textit{phase\_center\_id\_array})
 \item \textbf{phase\_center\_app\_ra}: \textit{float}
 Apparent right ascension of the phase center in the topocentric frame of the observatory, in radians.
 This is a one-dimensional array of size Nblts. In the event that there are multiple phase centers,
@@ -296,8 +299,8 @@ \subsection{Required Parameters}
 (\textit{phase\_center\_frame\_pa})
 
 \item \textbf{version}: \textit{string} The version of the HDF5 file. The latest
-  version (and the one described in this memo) is Version 1.0. Note it should be
-  a string, such as \verb+`1.0'+. See Sec.~\ref{sec:version_history} for the
+  version (and the one described in this memo) is Version 1.1. Note it should be
+  a string, such as \verb+"1.1"+. See Sec.~\ref{sec:version_history} for the
   version history of the HDF5 specification. (No corresponding UVData attribute)
 \end{itemize}
 
@@ -418,10 +421,12 @@ \subsubsection{Conjugation Convention}
 That is, the baseline vector defined by the $uvw$ coordinates is directed from
 antenna $i$ to antenna $j$ (so the baseline vector can be computed as
 $\vb{r_j} - \vb{r_i}$, where $\vb{r}$ is the position vector of a given
-antennas), and the data corresponding to antenna $j$ is conjugated. Note that if
-a file is generated with the opposite convention, it is usually sufficient to
-multiply $uvw$ coordinates by $-1$ to generate a self-consistent dataset, as
-well as conjugating the data in the \verb+data_array+.
+antennas), and the data corresponding to antenna $j$ is conjugated. Following
+the specification of the baselines, antenna $i$ is given by \verb+ant_1_array+
+and $j$ by \verb+ant_2_array+. Note that if a file is generated with the opposite
+convention, it is usually sufficient to multiply $uvw$ coordinates by $-1$ to
+generate a self-consistent dataset, as well as conjugate the data in the
+\verb+data_array+.
 
 \subsection{Flags Dataset}
 \label{sec:flags}