\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.

Notes since Documentation release of Version 2.6, dated  May 26th, 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 may not be distributed 
in any monthly Gildas release yet.  
\begin{itemize}
\item{13-Nov-2020} \com{MAP\_SMOOTH} command
\item{26-Oct-2020} \com{UV\_SMOOTH} command 
\item{11-Sep-2020} \com{KEPLER}{/MASK} command for Mask creation
\item{03-Sep-2020} Better behaviour of command \com{UV\_TIME}
\item{01-Sep-2020} Improve \com{FIT} command for Mosaics
\end{itemize}

\subsection{Known Bugs}
This section contains the list of bugs known as of \today, or recently
corrected.
\begin{enumerate}
\item{Discovered and Corrected 10-Dec-2020} \com{MODEL} after \com{UV\_FIT} was
ending with an undue error (bug present since 2-Jun-2020).
\item{corrected 8-Dec-2020} Mosaic offsets were not accounted for properly
since 19-Jun-2019.  The reason was a misplaced exclamation mark that
transformed a key instruction into a comment in the code file. 
Anomalous behaviour of the Mosaic mode were reported end of November, 
and a test case isolated on Dec 7 for analysis, leading a prompt correction. 
\item{corrected 26-Oct-2020} Several bugs in \com{UV\_MERGE}
made it fail on some (usually large) data files, sometimes depending
on the order in which they were given (discovered 15-Oct-2020).
\item{corrected 14-Sep-2020} Incorrect transfer of self-calibration solution in \com{APPLY}
and \com{SELFCAL}{APPLY} on some UV data set from ALMA.
\item{corrected 11-Sep-2020} \com{KEPLER} was off by 1 pixel.
\item{corrected 11-Sep-2020} Blanking was not updated in \comm{MASK}{APPLY} 
\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, still pending, difficult to reproduce).
\item{corrected 10-Jul-2020} \imager{} occasionally crashed after
a sequence of \comm{UV\_MAP}{/CONT} and \com{UV\_RESTORE} commands,
because of a map size mismatch. This size mismatch occured when the
baseline min-max of the UV data set are inconsistent with the UV data.
(discovered 07-Jul-2020).
\item{corrected 10-Jun-2020}   
  \com{KEPLER} does not handle \sicvar{KEPLER\_X0} and \sicvar{KEPLER\_Y0} properly.
\end{enumerate}


\subsection{Functional changes from previous versions}

Changes since Version 2.5 of Feb 27th, 2020, and older ones.
\begin{itemize}
\item{13-Nov-2020} Speed-up the \com{UV\_RESTORE} command.
\item{30-Jul-2020} Miscellaneous improvements in the \com{KEPLER} command
\item{26-May-2020} Implementation of the \com{UV\_DETECT} command,
  that encapsulates all actions needed for matched filtering in UV
  plane.
\item{14-May-2020} Proper implementation of the \com{UV\_CORRRELATE} command,
  that performs matched filtering in the UV plane
\item{13-May-2020} \com{MODEL} defines the \sicvar{UV\_MODEL} variable
\item{25-Mar-2020} Implementation of the \com{KEPLER} command,
that allows optimal detection of spectral lines in Keplerian disks,
and estimates of radial profiles.
\item{19-Mar-2020} Proper implementation of the \com{MODEL} command,
with the \comm{MODEL}{/MODE} option and several channels.
\item{11-Mar-2020} Command EXPLORE added to language BUNDLES
\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.
\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}

\subsection{Latest Bug corrections}
This section contains the list of bugs corrected since last documentation release.
\begin{enumerate}
\item{corrected 20-May-2020}
  \com{FITS} fails on large (300 GBytes..) UVFITS files. 
  (discovered 15-Feb-2020).
\item{corrected 19-Mar-2020} \comm{MODEL}{/MINVAL} threshold was erroneously
transformed between Jy/beam and K.
\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} could not be used after.
\end{enumerate}
