taskGNU Astronomy Utilities - Tasks: task #14869, Move NoiseChisel's segmentation...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #14869: Move NoiseChisel's segmentation into new program

Submitter:  Mohammad Akhlaghi <makhlaghi>
Submitted:  Sat 17 Feb 2018 11:31:07 PM UTC
   
 
Should Start On:  Sat 17 Feb 2018 11:00:00 PM UTC Should be Finished on:  Sat 17 Feb 2018 11:00:00 PM UTC
Category:  NoiseChisel Priority:  5 - Normal
Item Group:  Enhancement Status:  Done
Privacy:  Public Assigned to:  makhlaghi
Percent Complete:  100% Open/Closed:  Closed
Effort:  0.00

Fri 06 Apr 2018 12:20:42 AM UTC, comment #1: 

NoiseChisel is now only in charge of detection. All of NoiseChisel's segmentation steps have been moved to a new program called Segment. The process also involved a major fix to MakeCatalog (which uses the outputs of these programs).

With the new limited scopes, adding new features to NoiseChisel or Segment is much more easier.

The changes have been pushed to the main repo. In a few weeks, we will have a beta-release to ask interested people for trying out the new NoiseChisel, Segment and MakeCatalog. But if you have already been using NoiseChisel, it would be great if you could try it before that and report the bugs/problems that might have been caused during this major change and I haven't noticed yet.

It is recommended to read the sections of these programs in the book again. As always, the most recent tarball and the PDF manual is available in the links below:

http://akhlaghi.org/gnuastro-latest.tar.lz
http://akhlaghi.org/gnuastro.pdf

Mohammad Akhlaghi <makhlaghi>
Group administrator
Sat 17 Feb 2018 11:31:07 PM UTC, original submission:  

Detection and segmentation are two separate problems: one is for separating signal from noise and the other is for partitioning/segmenting the detections. For example in some conditions (especially very crowded fields), it can be useful to have separate kernels used for detection and segmentation.

But adding yet another option (and more later) to NoiseChisel to do something like this will only make it more complicated. This issue came up in a recent discussion with Aaron Watkins.

To enable easier management of NoiseChisel and more user flexibility in detection and segmentation, it would thus be good to break NoiseChisel into two progarms, one for detection (still called NoiseChisel), and another for segmentation (maybe called "Segment" with executable name `astsegment').

This is also in line with the Gnuastro' design philosophy.

I don't have time to do this right now, but if any thoughts or suggestions come up, please share it here.

Mohammad Akhlaghi <makhlaghi>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by makhlaghi (Submitted the item)
  • -email is unavailable- added by makhlaghi
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-04-06 makhlaghi StatusPostponed Done
        Percent Complete0% 100%
        Assigned toNone makhlaghi
        Open/ClosedOpen Closed
    2018-02-17 makhlaghi Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code