-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with nan in catalogues from deep stack #687
Comments
2025-01-15 14:25:21.68: vvvDetectionRaw202400 aperFlux2 25 16525 : -nan: NaN value found:deepstackcat Look in FITS catalogue and find how often. Find position on image and look at image. Is it weird values in image or conf? |
for ii, hdu in enumerate(hdulist): data.field('X_coordinate')[mask] data.field('Y_coordinate')[mask] |
Struggling to use Gaia or ds9. ds9 loads up an image but in the past I could open other extensions, but clicking on File doesn't work. |
Tried looking at image/conf data values around 1665, 2012 on extNum=3. All values seem reasonable - min/max/isnan checks? Tried reversing x/y. Have I looked at the wrong extension. I checked out to 15 pixels either side. Need to do this more systematically. |
24/JAN/25
|
Got Gaia to work - ( setenv LD_LIBRARY_PATH '' && gaia /disk67/vsa/products/stacks/20241114_v2/e20241114_00170007310_dp_st_conf.fit ) & So far can't see anything. Need to check more systematically. Might be worth running imcore again more verbosely to see the issues. Check headers too... |
Looking at extNum=3, the image and confidence. data.field('X_coordinate')[mask] data.field('Y_coordinate')[mask] I have looked at the first 5 objects and their confidence. All the pixels around have reasonable values - no confidence of 0, no NaN in the arrays or extreme values. The first object has a weird almost triangular blob on the confidence image that might give odd values, although I would be very surprised if it gave NaN. The others all look fine. The only strange thing is that all have y=2012. I will look at the headers. Aper_flux_1 are all fine. Aper_flux_3 and Aper_flux_8 are all nan. The sequence numbers are 8197-8200, 8202, 8203, 8209. |
When I ran it imcore again in verbose mode, extNum=3 had some strange estimated background values: Computing background.... Background values: Filtered background values: Computing background statistics.... Sky level = 6716.70 |
In imcore_background.c: if(nnp[j] > 0.25nbsizenbsize){
I think that the background estimator fails because nnp[j] <= 0.25nbsizenbsize. Why? I think that nnp is number of useful background measurements and it must be> a quarter of the local background area. |
Check code and email Jonathon/Mike Irwin? |
/unas/njc/usr/local/wsa/casutools/bin/imcore e20241114_00170007310_dp_st.fit e20241114_00170007310_dp_st_conf.fit test_cat3.fits 4 1.25 --crowd 1 --rcore 3 --nbsize 64 --noell --filtfwhm 2 --verbose --cattype 6 Seems that the issue is mflag == MF_ZEROCONF in thousands of pixels in each background square Confidence image values do go low, but always above 0. Is there a minimum level? |
05/MAR/25
|
2025-01-15 14:25:13.86: exnumeric -tables /ibi/tmp/scos_2013062.0002/schema_17
0.dat -files /ibi/tmp/scos_2013062.0002/filelist_170_0.dat -cuEvent 506442 -csvp
ath /ibi/samba/share -sqlpath /ibi/scos/VDFS/trunk/sql -csvprefix cu04id506442_
ibi-1-202400_VSAVVV15_wfau -illumname /ibi/tmp/scos_2013062.0002/illumTables.dat
-outtables vvvDetectionRaw202400 -newobjid -1 -archive VSA
2025-01-15 14:25:21.68: vvvDetectionRaw202400 aperFlux2 25 16525 : -na
n : NaN value found:deepstackcat
What is causing this.
Other oddity, which may or may not be related. This is from processing these files:
/disk67/vsa/products/stacks/20241114_v2/e20241114_00170007310_dp_st.fit
/disk67/vsa/products/stacks/20241114_v2/e20241114_00170007310_dp_st_cat.fits
/disk68/vsa/products/stacks/20241204_v2/e20241204_00170007310_dp_st.fit
/disk68/vsa/products/stacks/20241204_v2/e20241204_00170007310_dp_st_cat.fits
But productID=7310 is in twice. Once processed on 20241114 and once on 20241204. Why? See issue #688
The text was updated successfully, but these errors were encountered: