taskGNU Astronomy Utilities - Tasks: task #14167, Calculating the upper limit...

 
 

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

task #14167: Calculating the upper limit magnitude for each detection

Submitter:  Mohammad Akhlaghi <makhlaghi>
Submitted:  Thu 29 Sep 2016 01:50:33 PM UTC
   
 
Should Start On:  Wed 28 Sep 2016 03:00:00 PM UTC Should be Finished on:  Wed 28 Sep 2016 03:00:00 PM UTC
Category:  MakeCatalog Priority:  7 - High
Item Group:  New feature Status:  Done
Privacy:  Public Assigned to:  makhlaghi
Percent Complete:  100% Open/Closed:  Closed
Effort:  0.00

Sun 02 Oct 2016 10:43:56 PM UTC, comment #1: 

This feature has been added and pushed to the main repository. See the commit message and updated book for a thorough discussion.

Mohammad Akhlaghi <makhlaghi>
Group administrator
Thu 29 Sep 2016 01:50:33 PM UTC, original submission:  

One very important factor in measuring the magnitude of an object is this: what is the faintest acceptable magnitude for a given object (segmentation map) in an image? This depends on various things like the depth of the image, image correlated noise, or the shape and size of the object.

The standard way of finding this upper limit for an object is to measure the flux in a large number of randomly positioned (but identical in shape) segments over un-detected regions of the image.

For another project, I recently wrote an implementation of this process using Gnuastro's newly installed libraries. So I am now busy implementing it within MakeCatalog as a new column that the user can ask for.

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)
  •  

    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 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-10-02 makhlaghi StatusIn Progress Done
        Percent Complete70% 100%
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code