gnuastro-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnuastro-commits] master 59669d9 61/62: Book: new section on known issu


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master 59669d9 61/62: Book: new section on known issues with Crop
Date: Thu, 13 May 2021 22:20:56 -0400 (EDT)

branch: master
commit 59669d90b87c2f353356271a930e26015638943b
Author: Mohammad Akhlaghi <mohammad@akhlaghi.org>
Commit: Mohammad Akhlaghi <mohammad@akhlaghi.org>

    Book: new section on known issues with Crop
    
    Until now, there was only a "Known issues" section for the whole Gnuastro
    installation step. But in other cases, it may also happen that programs
    crash due to problems that are beyond Gnuastro itself (for example in
    dependency libraries) and thus we can't do anything about it! This
    situation happened recenty with a crash in the Crop program that was due to
    CFITSIO.
    
    With this commit, a new "Crop known issues" section has been added under
    the "Invoking Crop" section to describe that problem and propose
    solutions. If other similar problems occur, from now on, we'll have a place
    to let the users know.
    
    This issue was reported by Sepideh Eskandarloo.
---
 doc/gnuastro.texi | 29 ++++++++++++++++++++++++++++-
 1 file changed, 28 insertions(+), 1 deletion(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index acc89dc..f3f446f 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -433,6 +433,7 @@ Invoking Crop
 
 * Crop options::                A list of all the options with explanation.
 * Crop output::                 The outputs of Crop.
+* Crop known issues::           Known issues in running Crop.
 
 Arithmetic
 
@@ -11640,6 +11641,7 @@ This has no effect on each output, see @ref{Finding 
reddest clumps and visual in
 @menu
 * Crop options::                A list of all the options with explanation.
 * Crop output::                 The outputs of Crop.
+* Crop known issues::           Known issues in running Crop.
 @end menu
 
 @node Crop options, Crop output, Invoking astcrop, Invoking astcrop
@@ -11885,7 +11887,7 @@ The value must either be @option{img} or @option{wcs}, 
see @ref{Crop modes} for
 
 
 
-@node Crop output,  , Crop options, Invoking astcrop
+@node Crop output, Crop known issues, Crop options, Invoking astcrop
 @subsubsection Crop output
 
 The string given to @option{--output} option will be interpreted depending
@@ -11930,9 +11932,34 @@ A @code{0} if the central few pixels (value to the 
@option{--checkcenter} option
 When the crop was not defined by its center (see @ref{Crop modes}), or 
@option{--checkcenter} was given a value of 0 (see @ref{Invoking astcrop}), the 
center will not be checked and this column will be given a value of @code{-1}.
 @end enumerate
 
+@node Crop known issues,  , Crop output, Invoking astcrop
+@subsubsection Crop known issues
 
+When running Crop, you may encounter strange errors and bugs.
+In these cases, please report a bug and we will try to fix it as soon as 
possible, see @ref{Report a bug}.
+However, some things are beyond our control, or may take too long to fix 
directly.
+In this section we list such known issues that may occur in known cases and 
suggest the hack (or work-around) to fix the problem:
 
+@table @asis
+@item Crash with @samp{Killed} when cropping catalog from @file{.fits.gz}
+This happens because CFISTIO (that reads and writes FITS files) will 
internally decompress the file in a temporary place (possibly in the RAM), then 
start reading from it.
+On the other hand, by default when given a catalog (with many crops) and not 
specifying @option{--numthreads}, Crop will use the maximum number of threads 
available on your system to do each crop faster.
+On an normal (not compressed) file, parallel access will not cause a problem, 
however, when attempting parallel access with the maximum number of threads on 
a compressed file, CFITSIO crashes with @code{Killed}.
+Therefore the following solutions can be used to fix this crash:
+
+@itemize
+@item
+Decrease the number of threads (at the minimum, set @option{--numthreads=1}).
+Since this solution doesn't attempt to change any of your previous Crop 
command components or doesn't change your local file structure, it is the 
preferred way.
+
+@item
+Decompress the file (with the command below) and feed the @file{.fits} file 
into Crop without changing the number of threads.
 
+@example
+$ gunzip -k image.fits.gz
+@end example
+@end itemize
+@end table
 
 
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]