Welcome to iraf.net Saturday, April 27 2024 @ 08:26 PM GMT


 Forum Index > Help Desk > General IRAF New Topic Post Reply
 Coordinate file generated by daofind is empty
   
Arghya
 05/24/2022 01:38PM (Read 1542 times)  
+----
Newbie
sad

Status: offline


Registered: 05/24/2022
Posts: 3
Hi ,
I am currently a beginner with IRAF and am trying to overplot the coordinate file generated by Daofind package , but unfortunately the file has no data , only the header names ,format and units. I have tried experimenting with different parameters but to no avail. Daofind works fine for my image in python so my image file is not the issue. Any help is appreciated. Smile

 
Profile Email
 Quote
fitz
 05/25/2022 12:03AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
Without seeing the image or the parameters you used I can't offer any specific advice. An empty coordinate file usually means there was some kind of error in how the DATAPARS or FINDPARS parameters were set, e.g. a bad FWHM value or sky level, finding threshold set inappropriately, etc. You might have a look at pg 38-45 of the "Guide to Stellar CCD Photometry" (https://iraf.net/irafdocs/daophot2/) for info on how to set the parameters for DAOFIND.

I assume when you say "DAOFIND in python" you're referring to something like the astropy photutils tasks? I'm not familiar with those, but note there may be differences in how parameters are set (e.g. pixel sizes vs arcsec, are values in ADU, etc).

 
Profile Email
 Quote
Arghya
 05/25/2022 04:57PM  
+----
Newbie

Status: offline


Registered: 05/24/2022
Posts: 3
So i used daofind in interactive mode and used the curson option (spacebar) and that resulted in a coordinate file but its clearly not accurate. (see image) . Running daofind in non interactive mode gives empty coordinate file.


 
Profile Email
 Quote
Arghya
 05/25/2022 05:01PM  
+----
Newbie

Status: offline


Registered: 05/24/2022
Posts: 3
Here is the image

https://ibb.co/DgXHG7W

 
Profile Email
 Quote
fitz
 05/26/2022 07:17PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
The multiple detections in saturated features is usually seen when the parameters aren't set properly for the data (i.e. the DATAPARS pset) or the detection limits are off. The screenshot isn't clear enough for me to read the terminal, by "see the image" I meant I would need the actual FITS file as well as a dump of the parameters you used (e.g. "cl\$this-\$this->_split2($m[0])_split2($m[0]) dpar daofind", and same for datapars/findpars).

Also suspicious is the image name being "3.fits", in general numeric image name should be avoided since image extensions are sometimes removed to create other filenames which can get confused with a numeric value. Did you end up changing any of your initial parameter values after reading the documentation of how they should be set or were you pretty close already?

 
Profile Email
 Quote
   
Content generated in: 0.16 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login