Warning, remaining image dimensions too low!

Stacking program, astrometric (plate) solver, fits file viewer

Brought to you by: han59

Warning, remaining image dimensions too low!

Forum: General discussions ASTAP

Creator: Axel Thomas

Created: 2024-07-11

Updated: 2024-07-26

<< < 1 2 (Page 2 of 2)

han.k - 2024-07-20

A have a development version ready. The photometric calibration is fixed. Furthermore you can filter the online annotation database on V and if you set the font size at 7 the annotation is just acceptable. Development for Windows version only:

http://www.hnsky.org/astap_setup.exe

See attached screenshot.

More next days. Tell me if something is not working

Cheers, Han

Untitled.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-21

I can reproduce the error. Now I'm looking to the cause.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-21

A new development version is ready:

http://www.hnsky.org/astap_setup.exe

The SD of each star is calculated and added to the variable dropdown list in the AAVSO report. The star with the highest SD is on top. Works okay for a few hundered stars but your Tu Nus images adds 2400 stars to the columns and the program is struggeling with that.

Requires more testing but noticed your images are too much undersampled. Since of your DSLR/OSC camera only 50% of the sensor area is green sensitive then often the peak of the star will be on the red or blue sensitive pixels. More out of focus would have been better.

Star Tu Mus is often to faint. Maybe the images series can be better analysed using all RGGB sensitive pixel.

Han

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-25

Hi Alex,

ASTAP version 2024.07.25 is ready. Many changes. It can now measure non-AAVSO stars in bulk. So there are three photometry modes:

Manually
All AAVSO annotations
All stars up to number....

For the last two modes, the stars are listed in the AAVSO report sorted on standard deviation. Descending for Var and ascending for check stars.

I tried one more time your TU Mus images series but there is too much noise in the stars due to undersampling. Too good seeing where they where taken.

Tell me if you find a problem.

Han

Last edit: han.k 2024-07-25

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Axel Thomas - 2024-07-26

Han,
I just ran the TU Mus images with the astap 2024.07.21 version again. Solving works fine but photometric calibration won't work (see below).
Not sure if you said that photometric calibration does not work at all with these images (undersampled?) or do I not use the most current version?
Sorry, I lost track with all those emails.

cs Axel

15:25:43 1073 stars, 830 quads selected in the image. 711 database stars, 550 database quads required for the 9.53° square search window. Step size 9.53°.
15:25:43 122 of 122 quads selected matching within 0.007 tolerance. Solution["] x:=23.055250x+ 2.332041y+ -30430.446917, y:=2.311655x+ -23.045727y+ 16026.444995
15:25:43 Solution found: 11: 29 33.84 -66° 40 32.3 Solved in 0.7 sec. Δ was 10.6". Used stars down to magnitude: 9.4
15:38:21 Can not calibrate G:\astro\Veränderliche\Mus\Mus TU\20230611\lc\lc.cmpack-files\tmp00001.fts. Add first an astrometrical solution.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-26

Hi Axel,

I tried with a magnitude limit of 8. You get magnitude measurements but very noisy. I assume that this is due to the missing red and blue pixels. If the star shines at the red or blue sensitive pixel you will loose a lot of flux since the calibrated images only contain the green channel. Since the the stars will move a little in the image due to a tracking error you get a noisy flux measurement when the star moves from red/blue to green sensitive pixels and reverse.

Maybe the full image with all RGGB pixels will work better. I have only maybe 20 of your full resolution images but I will have a quick look if it give less deviation. The TU Mus series was 90 images? Saturation occurs at about magnitude 6 if I remember well.

Han

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-26

For the 20 raw images so with all RGGB pixels, I get for star TU Mux a sigma/standard deviation of 0.035 magnitudes.

For the green channel (TG) only I get a sigma of 0.1 so much worse.

I can see that sometimes all the star light is concentrated at one pixel only. So you can't skip the red and blue channel in this situation. See attached

Ham

tu_mus green channel only.png

tu_mus raw channels, aperture 2.1.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-26

This is the result for all 90 green channel images:

Looks like the aperture indication has a bug.

tu_mus raw channels, aperture 2.1, report.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-26

The aperture has no bug but the HFD detection goes to a save default due to the very low background value under 8.

I can a better look if you share all the 90 raw images and master flat. master dark files.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

han.k - 2024-07-26

There is a bug in version 2024.07.25. After loading a new images in the phometry tab, the viewer screen stays black. Download version 2024.07.26.

Last edit: han.k 2024-07-26

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

<< < 1 2 (Page 2 of 2)

Log in to post a comment.