gnuastro-commits
[Top][All Lists]
Advanced

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

[gnuastro-commits] master 49f62ec4 1/2: Book: corrected typos in NoiseCh


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master 49f62ec4 1/2: Book: corrected typos in NoiseChisel optimization for storage
Date: Tue, 4 Oct 2022 10:00:34 -0400 (EDT)

branch: master
commit 49f62ec4a213a7c4c27dbd764a24e21b732aa502
Author: Sepideh Eskandarlou <sepideh.eskandarlou@gmail.com>
Commit: Mohammad Akhlaghi <mohammad@akhlaghi.org>

    Book: corrected typos in NoiseChisel optimization for storage
    
    Until now, In the section of "NoiseChisel optimization for storage" there
    were two typos in the text.
    
    With this commit, both of these typos are corrected.
---
 doc/gnuastro.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index 152f0ee6..e8e5f1da 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -3065,9 +3065,9 @@ $ ls -lh nc-for-storage.fits
 See how @file{nc-for-storage.fits} has four HDUs, while 
@file{nc/xdf-f160w.fits} had five HDUs?
 As explained above, the missing extension is @code{INPUT-NO-SKY}.
 Also, look at the sizes of the @code{SKY} and @code{SKY_STD} HDUs, unlike 
before, they are not the same size as @code{DETECTIONS}, they only have one 
pixel for each tile (group of pixels in raw input).
-Finally, you see that @file{nc-for-storage.fits} is just under 8 mega byes 
(while @file{nc/xdf-f160w.fits} was 100 mega bytes)!
+Finally, you see that @file{nc-for-storage.fits} is just under 8 mega bytes 
(while @file{nc/xdf-f160w.fits} was 100 mega bytes)!
 
-But we are are not yet finished!
+But we are not yet finished!
 You can even be more efficient in storage, archival or transferring 
NoiseChisel's output by compressing this file.
 Try the command below to see how NoiseChisel's output has now shrunk to about 
250 kilo-byes while keeping all the necessary information as the original 100 
mega-byte output.
 



reply via email to

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