\section{Bugs and Release Notes}
This section lists known bugs (or strange features) that are known
at the date of release of the documentation, and the list of changes
since previous releases.

Documentation release of Version 2.5, dated  Feb 27th, 2020.

\subsection{Recent changes in repository}
This section gives the changes made 
since the last documentation release (as dated above). The changes 
are available in the working repository, but not yet distributed 
in any monthly Gildas release.  

\begin{enumerate}
\item{10-Mar-2020} CASA to GILDAS interface\\
  The \texttt{casagildas()} tool has been totally re-written in pure Python
  to avoid issues with incompatible releases of Fortran compilers and
  Python between CASA and GILDAS
\item{27-Feb-2020} 	\com{UV\_SHORT} now allows to use images with non-circular
  beams as short spacings data. Such images can be, for example,
  an ACA image to be combined with ALMA data.
\end{enumerate}


\subsection{Known Bugs}
This section contains the list of bugs known as of \today.
\begin{enumerate}
\item 	\comm{UV\_SHORT}{/REMOVE} does not properly delete the SHORT\% 
  variable in some cases, in particular if command \com{XY\_SHORT} is (or has been)
  used (discovered 15-Feb-2020).
\item
  \com{FITS} fails on large (300 GBytes..) UVFITS files. 
  (discovered 15-Feb-2020).
\item{corrected 10-Mar-2020} \com{MAP\_RESAMPLE} may crash on some combination of values
 (discovered 10-Mar-2020).
\item{corrected 10-Mar-2020} 
  \com{VIEW} may fails the \sicvar{RANGE} is
non zero and the 3rd axis increment is negative.
\item{corrected 05-Mar-2020}
  \com{UV\_MAP} fails after \com{UV\_RESIDUAL} and \comm{SELECT}{UV\_RESIDUAL}
if the initial UV data set was not sorted in XY.
\item{corrected 05-Mar-2020}
	\com{MULTI} with non-zero value for \sicvar{CLEAN\_NITER} did not set up 
  properly the number of components (it finds 0). \comm{SHOW}{CCT} and
  \com{UV\_RESTORE} cannot be used after.
\end{enumerate}


\subsection{Changes from previous versions}
\begin{itemize}
\item{24-Feb-2020} \texttt{imager-linedb.sic} script converted to 
Python 2 and 3 compatible syntax
\item{21-Feb-2020} \com{UV\_MAP} was crashing on Mosaic in Robust weighting. Linked to a 
	missing (although optional !) argument to call doweig, despite the
	interface was used.
\item{18-Feb-2020} 
	3D size was incorrectly set by \com{UV\_MAP} on "huge" file (1200 x 1200 x 3840).
\item{14-Feb-2020} 
  Normalize message colours. 
\item{14-Feb-2020} Suppress blanking when not needed
\item{ 13-Feb-2020} Make \com{UV\_MERGE} compliant with its Help: 
	allow to merge Line data sets in Continuum mode.
\item{10-Feb-2020} \com{SLICE} command changes. \\
	The \texttt{SLICE} buffer had to be renamed to \texttt{SLICED}, as "slice()" is a 
  built-in Python method. The axis starts now from the closest point to 
  (0,0), leading to more intuitive slices.
\item{06-Feb-2020} \com{MAP\_COMPRESS} syntax was incorrectly handled. 
	The \texttt{HELP MAP\_COMPRESS} is still unclear, however.
\item{18-Dec-2019}
  \comm{VIEW}{CCT} optimized by coding the component compression after
    a \com{MULTI}.
\item{17-Dec-2019} \com{SELFCAL} optimization (was using slow mode
in \com{UV\_RESTORE}  by default).
\item{27-Nov-2019} \comm{UV\_CHECK}{/FILE} implemented.
\item{27-Nov-2019} \comm{UV\_TIME}{/FILE} implemented.
\item{27-Nov-2019} \comm{UV\_SHIFT}{/FILE} implemented.
\item{20-Nov-2019} Make sure \com{UV\_PREVIEW} also works for 1 channel.
%
\end{itemize}
