Refresh astrometric solutions fails ... (was Batch Solve Images)

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

Brought to you by: han59

Refresh astrometric solutions fails ... (was Batch Solve Images)

Forum: General discussions ASTAP

Creator: Pat Browne

Created: 2022-09-16

Updated: 2022-11-02

1 2 > >> (Page 1 of 2)

Pat Browne - 2022-09-16

Hi Han,
This is in response to our last exchange, where I added to the existing thread on Batch solve:

1) Based on your first comment below, I realized that the RA and DEC entries in the fits header were uninitialized. So I removed them from the fits header
2) Then I was able to set the apporximate RA and Dec position in ASTAP
3) I also ensured that FOV was auto AND search Radius 180
4) However it solved half of the images.
5) The remaining images had to be reloaded and solved manually, resetting each time the FOV to auto.
6) Unfortunately solving the images manually does not force a check mark in the photometry tab for the set of images.

Bottom line - during the process of Refresh Astrometric solution the FOV field gets changed from auto resulting in a failure to batch process certain images which can be solved when FOV=auto

Would you be able to suggest a way to ensure FOV=auto during a batch process ?
thanks
Pat

===
You replied:

You can do two things:

1) Prior to batch solving enter the RA, DEC position in the ASTAP viewer. It will use this position if no other position is in the FITS header.
2) Enter a search radius of 180 degrees. The first image of the series will take some minutes to solve but once the first image is solved, ASTAP will remember the position (and put it in the viewer as 1) ) and solve the other images of the series very quickly.

You could also combine 1) and 2) for next time.

Note if required you can also set the Field of view in "Auto" but that will most likely slow down the batch. Any setting change will be remembered after a solve of "save settings"

===

Capture d’écran de 2022-09-16 11-47-56.png

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

han.k - 2022-09-16

Hi Pat,

Normally the images have all the same FOV so the idea once the first is solved the other images can be solved using the information from the first.

Why is the FOV different for the images? 5% difference is no problem. But more then 20% difference gets problematic.

Han

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

Pat Browne - 2022-09-16

Hi Han,
That's a mystery. Here's the batch of files

(There are only 10 of them - 26mB so I zipped them up and attached them to this message.)

Pat

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

han.k - 2022-09-16

The scale of the images is 1.35 x 1.02 degrees. But the information in the image header tells ASTAP it is 0.31 x0.25 degrees. So the first image solves on FOV=auto overriding the is 0.31 x0.25 degrees but for the next image ASTAP will take the 0.31x0.25 degrees and solving will fail.

There is conflicting information in the header:
FOCALLEN= 200 / [mm] Telescope focal length
PIXSIZE1= 3.76 / [um] Pixel Size X, binned

but this one spoils it:
SCALE = 8.618756E-01 / arcsecs per pixel

Easiest way to fix this to remove this keyword SCALE. Load all images in the tab lights. Select all and select in the mouse popup menu "Change keyword in selected files" type for key word "scale" and then type as value "DELETE". The file data changes but you can recover them in the batch menu.

Han

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

han.k - 2022-09-16

The screenshot:

Untitled.png

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

Pat Browne - 2022-09-17

Hi Han,
I was able to delete the scale keyword.
I used the V17 database this time because the data is photometric.
It didn't solve 3 images. Do we know why ? I can solve them manually.
Would you like to see the log ?
I'm attaching 3 files
1. My settings (alignement tab)
2. Photometry tab with 3 unsolved
3. Manual (main window solution) of one of the files not solved during refresh astrometric solutions

Capture d’écran de 2022-09-17 11-30-23.png

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

Pat Browne - 2022-09-17

Hi again,
Attached are the two screenshots that didn't get posted
1. Batch astrometric solve (3 unchecked)
2. Manual main window solve of one of the ones unchecked

Capture d’écran de 2022-09-17 11-32-47.png

Capture d’écran de 2022-09-17 11-34-10.png

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

Pat Browne - 2022-09-17

Hi Han,
Since we have astrometric solutions for most of the images, I tried generating a report.
The graph scale is problematique. The magnitude for Bet Lyra is not correct
There is no data in the text file.

I have attached these two files.

Is this data set ok to generate a report ?

Merci beaucoup!
Pat

BETLYRvite_1s_20220911_034217_cal_graph.png

BETLYRvite_1s_20220911_034217_cal_report.txt

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

han.k - 2022-09-18

The 10 images you send earlier all solve. Check if the images which failed if they are of reasonable quality.

I checked the photometry. Bet_Lyr is saturated. So the center is near 65535. So ASTAP will refuse to report a magnitude value. You have to exposure shorter to and avoid the saturation range. Sometimes it helps to a little defocus for very bright stars.

Han

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

Pat Browne - 2022-09-21

Bonjour Han,
This time RRLyra : definitely not satured:

I decided to fix the saturation problem by selecting RR Lyra: Mag range 7.17 - 8.14
Everything worked beautifully: calibration only, astrometric refresh, analyse - using V17. I was able to identify two check stars from the AAVSO VSP 2 degree chart.

However the AAVSO report does not compute values for RR Lyrae and again the graph shows mag limits of over 100.

The mystery to solve is why the magnitude is not shown -

RR Lyr 2459842.64061 ? na CV NO STD ENSEMBLE na 193207.9+422524 ? 1.220 na 193207.9+422524 Ensemble of Gaia eDR3 stars, photometry transformed to Johnson-V. 2/SNR used for MERR.

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

Pat Browne - 2022-09-21

Attached is the sample which includes the report and the graph - for RR Lyrae

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

han.k - 2022-09-21

You have to click at least of RR_Lyr and also on a Check star with a similar magnitude. Then it will work. See attached screenshot.

I will add a warning if no star is selected. Note clicking on a star rotates the three position of VAR, Check and 3. It is like a "musical chair"

Last edit: han.k 2022-09-21

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

han.k - 2022-09-21

The missing attachment:

Untitled.png

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

han.k - 2022-09-21

This (Windows) version has a warning:

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

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

Pat Browne - 2022-09-21

Hi Han,
I did select the 3 stars. The report even notes its coordinates However ...
Still no joy.
NOTE I am running ubuntu linux.
Have you a new version for linux that I can try. ?

Pat

rrlyr_4s_20220920_032734_cal_report.txt

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

han.k - 2022-09-21

I have tested it now in Linux. It works. Did you instruct the program to scroll through the images to fill the magnitude values? You have press the >| button to scroll once thorugh the images and measure the stars. Then the magnitude values are added. See red markings attached screenshot.

Untitled.png

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

han.k - 2022-09-21

This is the new instruction just in case:

Untitled.png

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

Pat Browne - 2022-09-24

Hi Han,
I updated my version - see the about page
Same problem - I put on continuous scroll after I selected Var Check and 3 but there is never any estimate of magnitude written into the photometry page. Hence the report fails.

Is there a linux update that I can try ?

Capture d’écran de 2022-09-23 20-35-24.png

Capture d’écran de 2022-09-23 20-39-25.png

Capture d’écran de 2022-09-23 20-40-29.png

Capture d’écran de 2022-09-23 20-42-19.png

Capture d’écran de 2022-09-23 20-43-19.png

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

Pat Browne - 2022-09-24

Hi Han,
I tried processing the three stars again and this time it WORKS!
Two things were different:
1) I clicked analyse
2) I chose another Star 3.

Here's the report -
MERCI beaucoup

Last edit: Pat Browne 2022-09-24

rrlyr_4s_20220920_041947_cal_report.txt

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

han.k - 2022-09-24

Hi Pat,

Good it is starts working. The magnitude of the check star is maybe a little unstable.

Star 3 should not be relevant. It is just an extra you can use for testing. Note the ASTAP list of data you can also select all and copy with cntrl+C to a spreadsheet.

If you find any other problem please report. Feedback helps.

Cheers, Han

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

Pat Browne - 2022-09-24

Hi Han,
There seems to be a persistant bug that may have to do with star 3
I think I have found a repro case: If I select star 3 as shown - no magnitudes are generated.
As soon as I pick another star 3 - I get magnitudes.
So somehow my data is sensitive to star 3.
Attached are the 2 images showing star 3 (11 mag) and the bug

Capture d’écran de 2022-09-24 13-24-45.png

Capture d’écran de 2022-09-24 13-25-57.png

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

han.k - 2022-09-25

Hello Pat,

Yes your correct. I looked in the code and it uses all three magnitudes to calculate the graph scale. So you have to select three stars of similar magnitude. This is required to keep all three stars within the graph.

If you don't select a Check or 3 star it will display in the list a question mark (?) for the magnitude and ignore the values.

What I don't understand is that in your screenshot of the graph the magnitude is around -4. I can't reproduce that. What are the stars magnitude in the list/table. Can you repeat what your doing and is it reproducible and make a screenshot of the list/table?

Han

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

Pat Browne - 2022-09-29

Hi Han,
Sorry for the delay.
Yes, I can reproduce this if I assign 3 to the 11mag star
There is no list produced. I'll just send you the report and the graph

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

Pat Browne - 2022-09-29

No change --- i.e. this is what happens with the 3 star as shown

rrlyr_4s_20220920_032734_cal_graph.png

rrlyr_4s_20220920_032734_cal_report.txt

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

han.k - 2022-09-29

Hi Pat,

Looking to your graph, the Var marker is not placed on RR_Lyr. I have marked it with orange arrows:

Red dot: Var (? Refresh plotting)
Green dot: Check (193207.9....)
Blue dot: 3

The red dot description be should RR_Lyr. So marker "Var" should be placed RR_Lyr but it seems placed at empty space generating "? Refresh plotting"

Use the >| button to scroll trough the images.

1) Check if Var, Check and 3 markers stay on the stars. If not correct it.
2) Check if columns in table are filled correctly. There should be no "?" After a marker correction scroll again to collect the photometry data.
3) Only If columns are filled correctly generate the AAVSO report.

Attached your report and my quick report

Han

cal_graph.png

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

1 2 > >> (Page 1 of 2)

Log in to post a comment.