[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gnuastro-commits] master 15a33af: Book: Corrected old name of gal_qsort
From: |
Mohammad Akhlaghi |
Subject: |
[gnuastro-commits] master 15a33af: Book: Corrected old name of gal_qsort_index_single_d in example |
Date: |
Wed, 30 Jan 2019 13:01:33 -0500 (EST) |
branch: master
commit 15a33afc22cf8130903ba43c028d501b33346054
Author: Mohammad Akhlaghi <address@hidden>
Commit: Mohammad Akhlaghi <address@hidden>
Book: Corrected old name of gal_qsort_index_single_d in example
While introducing the ` gal_label_grow_indexs' function in the book, I
noticed that we were mistakenly suggesting to use
`gal_qsort_index_float_decreasing'. However, this function has since been
renamed to `gal_qsort_index_single_d'. So it was necessary to correct this
in the book.
---
doc/gnuastro.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index 4e61463..8143082 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -28863,8 +28863,8 @@ The next major difference with over-segmentation is
that when there is only
one label in growth region(s), it is not mandatory for @code{indexs} to be
sorted by values. If there are multiple labeled regions in growth
region(s), then values are important and you can use @code{qsort} with
address@hidden to sort the indexs by values in a
-separate array (see @ref{Qsort functions}).
address@hidden to sort the indexs by values in a separate
+array (see @ref{Qsort functions}).
This function looks for positive-valued neighbors of each pixel in
@code{indexs} and will label a pixel if it touches one. Therefore, it is
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [gnuastro-commits] master 15a33af: Book: Corrected old name of gal_qsort_index_single_d in example,
Mohammad Akhlaghi <=