Wed, 04/14/2021 - 14:28
When I use the Upload Wizard, it goes through all the stages as I would expect it to (first-time user) and gives me the final Summary screen. Then when I check the processing status, there is nothing there. I did see someone else's photos being processed so I know it's working for someone out there. Then I tried again with another fits file and the same thing. Then I tried Quick Upload and you can see the loading bar working for half a second, but then nothing else happens. There is no "next" button or anything like that, and nothing in the processing queue. I would upload a fits here if someone would be so kind as to try it on their end, but the "Choose Files" link below is greyed out?
Thanks, Noah
Noah,
I'll need more information to track the problem:
- names of some of the files.
- exact time when you saw the failures.
You can send this direct to VPhot@gasilvis.net
George
I am back to my original problem.
Tried uploading a images of X LEO and it said everything was fine. Both quick upload and wizard. The files show as being processed in the Q, but do not in the view processed files.
I did upload a previous file of T CRB that uploaded a couple of weeks ago, and it uploaded fine again.
Vladimir
Vladimir:
In the VPhot daily log I receive, it looks like your OBSERVER fits header now contains "Vladimir Stebina (SVD)". A few days ago I think it was "unknown". Have you changed it recently?
In my own VPhot telescope setup, I use my observer code (MZK) as my OBSERVER fits header in my images and also as "owned by" in the VPhot telescope setup. It is just simpler/easier to remember. What do you have in your "owned by" field?
Ken
PS: Could you send a screenshot of your current telescope settings from VPhot to kenmenstar@gmail.com and to gasilvis@gmail.com?
Vladimir
#USERNAME=SVD
This needs to be your obscode
#SYS_NAME=8newtonian f4 with ST-8XE camera
This needs to be the SystemName of the telescope profile you want to have applied.
This will help VPhot sort out where your image is supposed to go.
Some of this is should be done automatically and why it is not happening is a puzzle to me.
Be that as it may, set the above fits keywords and you should be good-to-go
After that new issues await. I see that X Leo is not being properly identified on the image. That is an issue you may need to take to CHET team.
George
Good day.
I'm also stuck with this problem wherein I don't see my images uploaded in VPhot
I noticed in this forum that it can be solved by evaluating the FITS header but I have no idea what's causing the problem.
Here is the FITS header of my NGC7790 image data which I've been uploading:
Image #1
SIMPLE = T
BITPIX = 16 /8 unsigned int, 16 & 32 int, -32 & -64 real
NAXIS = 2 /number of axes
NAXIS1 = 1725 /fastest changing axis
NAXIS2 = 1287 /next to fastest changing axis
BSCALE = 1.0000000000000000 /physical = BZERO + BSCALE*array_value
BZERO = 32768.000000000000 /physical = BZERO + BSCALE*array_value
DATE-OBS= '2021-12-06T16:20:26.11' /YYYY-MM-DDThh:mm:ss observation, UT
EXPTIME = 60.000000000000000 /Exposure time in seconds
EXPOSURE= 60.000000000000000 /Exposure time in seconds
SET-TEMP= -25.000000000000000 /CCD temperature setpoint in C
CCD-TEMP= -24.968750000000000 /CCD temperature at start of exposure in C
XPIXSZ = 10.800000000000001 /Pixel Width in microns (after binning)
YPIXSZ = 10.800000000000001 /Pixel Height in microns (after binning)
XBINNING= 2 /Binning factor in width
YBINNING= 2 /Binning factor in height
XORGSUBF= 0 /Subframe X position in binned pixels
YORGSUBF= 0 /Subframe Y position in binned pixels
READOUTM= 'Raw ' / Readout mode of image
FILTER = 'Green ' / Filter used when taking image
IMAGETYP= 'Light Frame' / Type of image
FOCALLEN= 3251.0000000000000 /Focal length of telescope in mm
APTDIA = 406.00000000000000 /Aperture diameter of telescope in mm
APTAREA = 129461.89526438713 /Aperture area of telescope in mm^2
EGAIN = 0.37999999523162842 /Electronic gain in e-/ADU
SBSTDVER= 'SBFITSEXT Version 1.0' /Version of SBFITSEXT standard in effect
SWCREATE= 'MaxIm DL Version 6.26 210113 12WM9' /Name of software
SWSERIAL= '297US-VF0TP-P02RY-EXV3T-2CKMJ-5M' /Software serial number
OBJECT = 'ngc7790 '
OBJCTRA = '23 57 00' / Nominal Right Ascension of center of image
OBJCTDEC= '+61 04 49' / Nominal Declination of center of image
OBJCTALT= ' 51.3464' / Nominal altitude of center of image
OBJCTAZ = '347.5828' / Nominal azimuth of center of image
OBJCTHA = ' 1.0793' / Nominal hour angle of center of image
PIERSIDE= 'EAST ' / Side of pier telescope is on
SITELAT = '24 10 35' / Latitude of the imaging location
SITELONG= '54 41 07' / Longitude of the imaging location
JD = 2459555.1808577548 /Julian Date at time of exposure
JD-HELIO= 2459555.1838185648 /Heliocentric Julian Date at time of exposure
AIRMASS = 1.2784192440320554 /Relative optical path length through atmosphere
TELESCOP= ' ' / telescope used to acquire this image
INSTRUME= 'SBIG STT-8300 3 CCD Camera'
OBSERVER= ' '
NOTES = ' '
ROWORDER= 'TOP-DOWN' / Image write order, BOTTOM-UP or TOP-DOWN
FLIPSTAT= ' '
SWOWNER = 'Thabet Al Qaissieh' /Licensed owner of software
INPUTFMT= 'FITS ' / Format of file from which image was read
SWMODIFY= 'MaxIm DL Version 6.26 230115 297US' /Name of software
HISTORY Dark Subtraction (Dark 1, 1725 x 1287, Bin2 x 2, Temp -25C,
HISTORY Exp Time 60s)
CALSTAT = 'DF '
HISTORY Flat Field (Flat 1, green, 1725 x 1287, Bin2 x 2, Temp -25C,
HISTORY Exp Time 260ms)
PEDESTAL= -100 /Correction to add for zero-based ADU
CSTRETCH= 'Medium ' / Initial display stretch mode
CBLACK = 1759 /Initial display black level in ADUs
CWHITE = 2907 /Initial display white level in ADUs
HISTORY Align Images
CTYPE1 = 'RA---TAN' / first parameter RA , projection TANgential
CTYPE2 = 'DEC--TAN' / second parameter DEC, projection TANgential
CUNIT1 = 'deg ' / Unit of coordinates
CRPIX1 = 8.630000000000E+002 / X of reference pixel
CRPIX2 = 6.440000000000E+002 / Y of reference pixel
CRVAL1 = 3.596117734980E+002 / RA of reference pixel (deg)
CRVAL2 = 6.119592946355E+001 / DEC of reference pixel (deg)
CDELT1 = 1.898109463348E-004 / X pixel size (deg)
CDELT2 = 1.897623213519E-004 / Y pixel size (deg)
CROTA1 = 9.148006777970E+001 / Image twist of X axis (deg)
CROTA2 = 9.145992825998E+001 / Image twist of Y axis (deg)
CD1_1 = -4.835964915462E-006 / CD matrix to convert (x,y) to (Ra, Dec)
CD1_2 = 1.896990111378E-004 / CD matrix to convert (x,y) to (Ra, Dec)
CD2_1 = -1.897493314662E-004 / CD matrix to convert (x,y) to (Ra, Dec)
CD2_2 = -4.901405738033E-006 / CD matrix to convert (x,y) to (Ra, Dec)
PLTSOLVD= T / ASTAP internal solver
COMMENT 7 Solved in 0.3 sec. Offset was 12.6'. Mount offset RA=5202.7', DEC=-6.
Thanks in advance for your help. Clear skies!
This is similar to problem discussed elsewhere in this thread. See SGO 10/30/2021.
Possible solution is to add the following entry into the FITS header:
EQUINOX = 2000.
Aldrin:
Did you try both quick upload and upload wizard?
Headers for TELESCOP and OBSERVER are not filled in.
Do you have a telescope setup in VPhot under admin?
Have you ever successfully uploaded any of your own images?
If you have Maxim, why do you plate-solve with ASTAP? Are these someone else's images?
What is your complete process for collecting and reducing your images before uploading? What software for each step?
Ken
I am having similar issues. I have tried everything listed in this thread. Filename is
UMA (ST UMA), 2022-05-02, 5x20L, ASCOM Telescope Driver for TheSky, (B), ASI Camera (2)_stacked.fits
Most recent attempt was at 19:25 UTC May 5.
FITS header passes the Wizard test but image does not appear in the image list nor does the file appear in the list of processed images. I have had this problem before and solved by changing the OBSERVER keyword to the aavso observer code and adding the EQUINOX keyword but now it isn't working again. I also tried eliminating the plateslove information (
CD1_1 = 2.683785784820E-004 / CD matrix to convert (x,y) to (Ra, Dec)
CD1_2 = -2.445692543731E-006 / CD matrix to convert (x,y) to (Ra, Dec)
CD2_1 = 2.351312844303E-006 / CD matrix to convert (x,y) to (Ra, Dec)
CD2_2 = 2.680841776644E-004 / CD matrix to convert (x,y) to (Ra, Dec)
) but that didn't help either.
Here is the is the FITS header
SIMPLE = T / file does conform to FITS standard
BITPIX = -32 / number of bits per data pixel
NAXIS = 2 / number of data axes
NAXIS1 = 2072 / length of data axis 1
NAXIS2 = 1411 / length of data axis 2
BZERO = 0 / offset and data range to that of unsigned short
BSCALE = 1 / default scaling factor
CRPIX1 = 1.036500000000E+003 / reference spectrum pixel coordinate for axis 1
CRPIX2 = 7.060000000000E+002 / reference spectrum pixel coordinate for axis 2
CTYPE1 = 'RA---TAN' / first parameter RA , projection TANgential
CTYPE2 = 'DEC--TAN' / second parameter DEC, projection TANgential
OBJECT = 'ST UMa' / Object name
DATE-LOC= '2022-05-01T21:16:51.6635267' / Local observation date
DATE-OBS= '2022-05-02T04:18:27'
IMAGETYP= 'LIGHT ' / Type of frame
CREATOR = 'Sequence Generator Pro v4.1.0.765' / Capture software
INSTRUME= 'ASI Camera (2)' / Instrument name
ROWORDER= 'TOP-DOWN' / Image row order
OBSERVER= 'DPAC ' / Observer name
USERNAME= 'DPAC '
SYS_NAME= 'CI '
SITENAME= 'CI ' / Observatory name
SITEELEV= 680 / Elevation of the imaging site in meters
SITELAT = '32 17 35.000' / Latitude of the imaging site in degrees
SITELONG= '-111 14 1.000' / Longitude of the imaging site in degrees
FOCUSER = 'ZWO Focuser (1)' / Focuser name
FOCPOS = 6893 / Absolute focuser position
FOCTEMP = 31.8400001525879 / Focuser temperature
FWHEEL = 'ZWO FilterWheel (1)' / Filter Wheel name
FILTER = 'B ' / Filter name
XBINNING= 4 / Camera X Bin
CCDXBIN = 4 / Camera X Bin
YBINNING= 4 / Camera Y Bin
CCDYBIN = 4 / Camera Y Bin
XPIXSZ = 9.26 / Pixel Width in microns (with binning)
YPIXSZ = 9.26 / Pixel Height in microns (with binning)
GAIN = '129 ' / Camera Gain
TELESCOP= 'CI' / Telescope name
RA = 171.958223664832 / Object Right Ascension in degrees
DEC = 45.1852705056224 / Object Declination in degrees
CRVAL1 = 1.719381854343E+002 / RA at image center in degrees
CRVAL2 = 4.520835038908E+001 / DEC at image center in degrees
OBJCTRA = '11 27 49.974' / Object Right Ascension in hms
OBJCTDEC= '+45 11 06.974' / Object Declination in degrees
PIERSIDE= 'East ' / Side of Pier the objective is on
AIRMASS = 1.02543684281201 / Average airmass
OBJCTALT= 77.2095588528463 / Altitude of the object
CENTALT = 77.2095588528463 / Altitude of the object
ANGLE = 0 / Image angle
SCALE = 0.96 / Image scale (arcsec / pixel)
PIXSCALE= 0.96 / Image scale (arcsec / pixel)
AOCCLOUD= 0 / Cloud Cover in %
AOCDEW = -6.6 / Dew Point in degrees C
AOCHUM = 11 / Humidity in %
AOCBAROM= 929.3 / Pressure in hPa
AOCRAIN = 0 / Rain Rate in mm/hr
AOCAMBT = 26.2 / Ambient Temperature in degrees C
AOCWINDD= 260 / Wind Direction in degrees (0-359)
AOCWIND = 4.6 / Wind Speed in m/s
EGAIN = 0.903593122959137 / Electrons Per ADU
CUNIT1 = 'deg ' / Unit of coordinates
CDELT1 = 2.683888784211E-004 / X pixel size (deg)
CDELT2 = 2.680953332791E-004 / Y pixel size (deg)
CROTA1 = -5.226864737386E-001 / Image twist of X axis (deg)
CROTA2 = -5.019657539314E-001 / Image twist of Y axis (deg)
CD1_1 = 2.683785784820E-004 / CD matrix to convert (x,y) to (Ra, Dec)
CD1_2 = -2.445692543731E-006 / CD matrix to convert (x,y) to (Ra, Dec)
CD2_1 = 2.351312844303E-006 / CD matrix to convert (x,y) to (Ra, Dec)
CD2_2 = 2.680841776644E-004 / CD matrix to convert (x,y) to (Ra, Dec)
PLTSOLVD= T / ASTAP internal solver
COMMENT 7 Solved in 0.1 sec. Offset was 1.6'. Mount offset RA=0.8', DEC=-1.4'
COMMENT 1 Written by ASTAP. www.hnsky.org
CALSTAT = 'DFBS'
JD-AVG = 2.459701679041E+006 / Julian Day of the observation mid-point.
DATE-AVG= '2022-05-02T04:17:49'
EQUINOX = '2000.0'
COMMENT UT midpoint in decimal notation: 20220502.1790
COMMENT D=master_dark_10x20s_at_0C_2022-02-26.fit
COMMENT F=master_flat_corrected_with_flat_darks_B_26xF_25xFD_2022-01-27.fit
HISTORY 1 Stacking method SIGMA CLIP AVERAGE
HISTORY 2 Processed as gray scale images.
EXPTIME = 100 / Total luminance exposure time in seconds.
LUM_EXP = 20 / Average luminance exposure time.
LUM_CNT = 5 / Luminance images combined.
LUM_DARK= 10 / Darks used for luminance.
LUM_FLAT= 26 / Flats used for luminance.
LUM_BIAS= 25 / Flat-darks used for luminance.
LUM_TEMP= 0 / Set temperature used for luminance.
DATAMIN = 0 / Minimum data value
DATAMAX = 63612 / Maximum data value
CBLACK = 16 / Indicates the black point used when displaying
CWHITE = 51 / indicates the white point used when displaying
END
Any help will be appreciated
Patric:
You indicated that you have successfully upload images before. Is that correct? Nothing has changed recently in the vphot upload procedure.
What is different about the system or software you are using for these new images? Have you been changing your procedures for imaging or reduction of your images? Are you working with new software with the intent of improving your photometry?
Are you able to re-upload one of the images that have worked successfully in the recent past?
I am willing to skype/zoom and discuss the procedures you are using? Email me at kenmenstar@gmail.com to set up this communication.
Ken
My workflow has been in a state of flux this winter.
A friend offered to automate my variable star imaging and I took him up on it. We tried various programs with the last being SG Pro.
We did use his copy of SG Pro to test using it for variables. It worked fairly well, and I used it for a couple of imaging sessions. Then I purchased my own copy of SG Pro.
We did have a few issues with sequences and those changed between his copy and my copy of SG Pro. I suspect we might have changed some naming conventions as well. I believe the first issue arose after my initial use of SG Pro, but then went away.
However, to do my calibration I go back to CCD Soft.
That is the last step before I upload the observations to VPHOT.
Thanks for the tips. I will go back and look at the FITS headers and VPHOT settings at each stage of the workflow.
I guess it might be appropriate that X LEO would have issues. That was the variable that led me to switch from visual to CCD.
Vladimir
Hello!
I'm stumped.
Vladimir sent me an image of X Leo. The only thing I noticed was that the telescop field in the FITS header did not match the VPHOT field, but he said this change gave him a PinPoint error.
I uploaded the image to Astrometry.Net and it solved fine. Plate scale and image angle were as in the FITS header. I uploaded it to the program I use, MPO Canopus, and it plate solved fine, which is interesting since I did not change the parameters of my setup to match that of the X LEO image. I uploaded the image to PinPoint in my setup and it plate solved fine.
I am not sure where the breakdown is, but his image plate solves fine in 3 other plate solving engines, which is especially puzzling since VPHOT uses PinPoint to plate solve and PinPoint solved it fine for me. Best regards.
Mike
On 10/25/2021 and 10/26/2021:
When uploading image with Upload Wizard, image fails to appear in image list:
My observer id is FPIA
The name of the file is: testNGC7790 B CandPS.fit
There were no errors in the Upload Wizard; I can send screenshots and actual file directly,
File size is 30.8M
Object name : "Autosave Image"
Approx RA: 23:58:46.82
Approx Dec: 61:11:54.36
Filter: B
Wizard stated: "You are good to go! Press 'Next' to proceed!"
Is there a log somewhere that can give me a clue what happened?
Thanks;
Pierre "Pete" Fleurant
The following is a copy of the fits header:
Image #1
SIMPLE = T / file does conform to FITS standard
BITPIX = 16 / number of bits per data pixel
NAXIS = 2 / number of data axes
NAXIS1 = 4800 / length of data axis 1
NAXIS2 = 3211 / length of data axis 2
EXTEND = T / FITS dataset may contain extensions
COMMENT FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
BZERO = 32768 / offset data range to that of unsigned short
BSCALE = 1 / default scaling factor
PROGRAM = 'PixInsight 1.8.8-9' / Software that created this HDU
COMMENT PixInsight Class Library: PCL 2.4.10
COMMENT FITS module version 1.1.9
COLORSPC= 'Grayscale' / PCL: Color space
RESOLUTN= 72. / PCL: Resolution in pixels per resolution unit
RESOUNIT= 'inch ' / PCL: Resolution unit
ROWORDER= 'TOP-DOWN' / Order of pixel rows stored in the image array
DATE-OBS= '2021-10-07T00:20:15.509' / Start date/time of observation (UTC)
EXPTIME = 60. / [sec] Duration of exposure
EXPOSURE= 60. / [sec] Duration of exposure
SET-TEMP= -20. / CCD temperature setpoint in C
CCD-TEMP= -20. / CCD temperature at start of exposure in C
XPIXSZ = 7.52 / Pixel size including binning, X-axis (um)
YPIXSZ = 7.52 / Pixel size including binning, Y-axis (um)
XBINNING= 2. / Binning level along the X-axis
YBINNING= 2. / Binning level along the Y-axis
XORGSUBF= 0. / Subframe X position in binned pixels
YORGSUBF= 0. / Subframe Y position in binned pixels
READOUTM= 'Fast ' / Readout mode of image
FILTER = 'B ' / Filter name
IMAGETYP= 'Light Frame' / Type of image
FOCALLEN= 1905.5696 / Focal length (mm)
APTDIA = 431.799987792969 / Aperture diameter of telescope in mm
APTAREA = 124165.167906122 / Aperture area of telescope in mm^2
EGAIN = 1. / Electronic gain in e-/ADU
SBSTDVER= 'SBFITSEXT Version 1.0' / Version of SBFITSEXT standard in effect
GAIN = 0.
SWSERIAL= '1TPWM-7392S-WMYXM-UYHJ3-9S9Q7-2J' / Software serial number
JD = 2459494.5140684 / Julian Date at time of exposure
JD-HELIO= 2459494.52002517 / Heliocentric Julian Date at time of exposure
OBJECT = 'Autosave Image' / Target object name
TELESCOP= 'ATMoB CDK17' / Telescope name
INSTRUME= 'QHYCCD-Cameras-Capture' / Detector instrument name
OBSERVER= 'Alan Sliski' / Observer name
NOTES = ' '
EXP = 0.
OBJ-DATE= ' '
OBJRA = ' '
OBJCTDEC= '+61 11 53.95' / Declination (deg) (compatibility)
OBJCTDRA= ' '
OBJHA = ' '
CCD = ' '
SIPLE = 'T '
FLIPSTAT= ' '
SWOWNER = 'Dave Heidenreich' / Licensed owner of
INPUTFMT= 'FITS ' / Format of file from which image was read
HISTORY File was processed by PinPoint 5.1.8 at 2021-10-14T15:34:14
DATE = '07/10/21' / [old format] UTC date of exposure start
UT = '00:20:15' / [old format] UTC time of exposure start
TIMESYS = 'UTC ' / Time scale: Universal Time, Coordinated
RADECSYS= 'FK5 ' / Equatorial coordinate system
CLRBAND = 'R ' / [J-C std] Std. color band of image or C=Color
ZMAG = 21.0881113436 / Mag zero point for 1 sec exposure
PA = 359.875587478 / [deg, 0-360 CCW] Position angle of plate
TR1_0 = 2400.00009275 / [private] X-axis distortion coefficients
TR1_1 = 4799.99999121
TR1_2 = 0.297830477309
TR1_3 = 0.905126305326
TR1_4 = -0.63435848273
TR1_5 = 0.0107192230595
TR1_6 = 4.9727155403
TR1_7 = 0.593965097612
TR1_8 = 0.342730485227
TR1_9 = 0.0312425017639
TR1_10 = -7.23287092656
TR1_11 = -0.0359257918461
TR1_12 = -3.20661655161
TR1_13 = 4.02157225761
TR1_14 = -2.03171660376
TR2_0 = 1605.49999939 / [private] Y-axis distortion coefficients
TR2_1 = -0.00363529369647
TR2_2 = 3210.99999932
TR2_3 = -0.682732591526
TR2_4 = 0.411860496669
TR2_5 = -1.44769538238
TR2_6 = -1.22474275486
TR2_7 = 1.535727647
TR2_8 = 0.0349051782545
TR2_9 = 0.466093676188
TR2_10 = 0.44806401687
TR2_11 = -0.21029005305
TR2_12 = 8.522815532
TR2_13 = -1.94358565399
TR2_14 = 2.01256803948
HISTORY WCS added by PinPoint 5.1.8 at 2021-10-14T15:34:15
HISTORY Matched 352 stars from the Gray GSC-ACT Catalog
HISTORY Average residual was 0.23 arc-seconds
PLTSOLVD= T / Plate has been solved by PinPoint
CSTRETCH= 'Medium ' / Initial display stretch mode
CBLACK = 333. / Initial display black level in ADUs
CWHITE = 1262. / Initial display white level in ADUs
PEDESTAL= -100. / Correction to add for zero-based ADU
SWMODIFY= 'MaxIm DL Version 5.15' / Name of software that modified the image
HISTORY Bias Subtraction (Bias 1, 4800 x 3211, Bin2 x 2, Temp -5C,
HISTORY Exp Time 0ms)
CALSTAT = 'BDF '
HISTORY Dark Subtraction (Dark 1, 4800 x 3211, Bin2 x 2, Temp -5C,
HISTORY Exp Time 60s)
HISTORY Flat Field (Flat B 1, B, 4800 x 3211, Bin2 x 2, Temp -5C,
SNAPSHOT= 10. / Number of images combined
MIDPOINT= '2021-10-07T00:44:03.040' / UT of midpoint of exposure
COMMENT Astrometric solution by PixInsight 1.8.8-9
DATE-END= '2021-10-07T00:21:15.509' / End date/time of observation (UTC)
RA = 359.694848048616 / Right ascension of the center of the image (deg
OBJCTRA = '23 58 46.764' / Right ascension (hours) (compatibility)
DEC = 61.1983200159032 / Declination of the center of the image (deg)
RADESYS = 'ICRS ' / Coordinates referred to ICRS / J2000.0
CTYPE1 = 'RA---TAN' / Axis1 projection: Gnomonic
CTYPE2 = 'DEC--TAN' / Axis2 projection: Gnomonic
CRPIX1 = 2400. / Axis1 reference pixel
CRPIX2 = 1605.5 / Axis2 reference pixel
CRVAL1 = 359.695082213 / Axis1 reference value
CRVAL2 = 61.1984333079 / Axis2 reference value
PV1_1 = 0. / Native longitude of the reference point (deg)
PV1_2 = 0. / Native latitude of the reference point (deg)
CD1_1 = -0.000226122077632 / Scale matrix (1,1)
CD1_2 = 4.90940051365E-07 / Scale matrix (1,2)
CD2_1 = -4.91004091293E-07 / Scale matrix (2,1)
CD2_2 = -0.000226092585329 / Scale matrix (2,2)
CDELT1 = -0.000226122610717349 / Axis1 scale
CDELT2 = -0.000226093118344821 / Axis2 scale
CROTA1 = 0.12441252191889 / Axis1 rotation angle (deg)
CROTA2 = 0.12441252191889 / Axis2 rotation angle (deg)
Pete,
I'm seeing:
- username= FPIA telescope= ATMoB MAO
- Updating header ... 1.3124549 s
The property has not been set.: TargetRightAscension
- Write header to database ... issue with StorePlateInDB
- Moving image to C:\V_E\images\637709364586626682.fts ... 0.1562149 s
- Failed to solve the image. message: Column 'ObsDateTime' cannot be null
OBJCTDRA= ' '
George
After uploading image without any error indication using either Quick Upload or Upload Wizard, image fails to appear in image without any indication of error.
This error can be reproduced if there is existing astrometric metadata in the FITS image and the same image is opened and saved in PixInsight.
I received the following reply from a Staff member:
<em>By default, PixInsight loads existing astrometric metadata in XISF and FITS images, then it regenerates the astrometric solution and replaces the corresponding header keywords with updated values. This behavior can be disabled with EDIT > Global Preferences > Miscellaneous Image Window Settings > Load astrometric solutions, although disabling this feature is strongly discouraged (you will miss important new features that will be implemented in future versions if you do so).
Juan Conejero
PixInsight Development Team
Pleiades Astrophoto S.L.
https://pixinsight.com/</em>
Apparently one or more of the following entries is causing the problem.
Here is an example of the entries, when removed, does not cause a failure:<em>
RADESYS = 'ICRS ' / Coordinates referred to ICRS / J2000.0
CTYPE1 = 'RA---TAN' / Axis1 projection: Gnomonic
CTYPE2 = 'DEC--TAN' / Axis2 projection: Gnomonic
CRPIX1 = 2400. / Axis1 reference pixel
CRPIX2 = 1605.5 / Axis2 reference pixel
CRVAL1 = 359.695082213 / Axis1 reference value
CRVAL2 = 61.1984333079 / Axis2 reference value
PV1_1 = 0. / Native longitude of the reference point (deg)
PV1_2 = 0. / Native latitude of the reference point (deg)
CD1_1 = -0.000226122077632 / Scale matrix (1,1)
CD1_2 = 4.90940051365E-07 / Scale matrix (1,2)
CD2_1 = -4.91004091293E-07 / Scale matrix (2,1)
CD2_2 = -0.000226092585329 / Scale matrix (2,2)
CDELT1 = -0.000226122610717349 / Axis1 scale
CDELT2 = -0.000226093118344821 / Axis2 scale
CROTA1 = 0.12441252191889 / Axis1 rotation angle (deg)
CROTA2 = 0.12441252191889 / Axis2 rotation angle (deg)</em>
Is there a list of reserved keywords that VPhot uses?
Thanks!
Peter,
You describe a repeatable experiment above where a file uploads successfully if certain fits header keys are removed.
Can you give me the filenames and exact time you did this experiment so I can look for it in the logs.
George
File name is "Test_Autosave Image -0007B.fit" with common telescope "ATMoB 17PW".
Uploaded at 01:37PM Eastern, today on 10/29/2021
Pete
I see in the log:
10/29/2021 5:37:14 PM - Found Test_Autosave Image -0007B.fit.
- Size 30839040 queued 0 s ... 0 s
- Moving/extracting to temp folder ... 0.0468865 s
- Waiting for write to complete ... 0.0156186 s
- PinPoint error: Failed to get CTYPE1 keyword.
- Error: No FITS image file is attached.
- Cleaning up. 0.2031233 s
The file got purged during a cleanup, so I can't examine it.
If you are willing to try that upload again, I'll take a look.
George
FITS image not getting loaded to image list
File name is "Test_Autosave Image -0007B.fit" with common telescope "ATMoB 17PW".
Uploaded at 01:47PM Eastern, today on 10/30/2021
At the time the queue was large.
Pete
Got the file.
VPhot still shows the error - PinPoint error: Failed to get CTYPE1 keyword.
I tried to process the file with standalone PinPoint and got the error:
D:\Temp\Test_Autosave Image -0007B.fit:
The WCS info in the image is not for equinox J2000.0. Cannot process the file.
I think PinPoint wants to see:
EQUINOX = 2000.0 / Equatorial coordinates are J2000
EPOCH = 2000.0 / (incorrect but needed by old programs)
George
Interesting.
If I remove the last 17 entries from the FITS Header, it will load into my image list.
RADESYS = 'ICRS ' / Coordinates referred to ICRS / J2000.0
CTYPE1 = 'RA---TAN' / Axis1 projection: Gnomonic
CTYPE2 = 'DEC--TAN' / Axis2 projection: Gnomonic
CRPIX1 = 2400. / Axis1 reference pixel
CRPIX2 = 1605.5 / Axis2 reference pixel
CRVAL1 = 359.695082213 / Axis1 reference value
CRVAL2 = 61.1984333079 / Axis2 reference value
PV1_1 = 0. / Native longitude of the reference point (deg)
PV1_2 = 0. / Native latitude of the reference point (deg)
CD1_1 = -0.000226122077632 / Scale matrix (1,1)
CD1_2 = 4.90940051365E-07 / Scale matrix (1,2)
CD2_1 = -4.91004091293E-07 / Scale matrix (2,1)
CD2_2 = -0.000226092585329 / Scale matrix (2,2)
CDELT1 = -0.000226122610717349 / Axis1 scale
CDELT2 = -0.000226093118344821 / Axis2 scale
CROTA1 = 0.12441252191889 / Axis1 rotation angle (deg)
CROTA2 = 0.12441252191889 / Axis2 rotation angle (deg)
So I know to remove these before ever uploading.
But the question I have is why didin't the user (me) get an indication of error. Does PinPoint signal VPhot there was an error, or do things just end?
Thanks!
-Pete
Its a shame that the pixinsight plate solution is not being used.
VPhot looks for CD1_1= in the header as confirmation that the solution is done.
Your file has that. But VPhot is using pinpoint to access the header and pinpoint barfs when it doesn't see the EQUINOX. I think.
Can you just insert EQUINOX= 2000.0 ? That might work.
George
Hi George,
Sorry for the delay. I was out of town, etc., etc..
YES, that worked!
After using ImageSolver script in PixInsight I added "EQUINOX= 2000.0" to the FITS Header and uploaded to VPhot.
It came back with a green WCS.
Thanks!
-Pierre "Pete" Fleurant
It seems like the upload wizard should be flagging anything required and not say things are OK if they are missing. I've also been having a problem with images not uploading. Even though the wizard says they are fine, the never appear in the queue. My observer code is TBOB.
Bill:
I suspect the reason your images are not getting to your vphot account is not related to missing headers needed to process the images BUT related to information needed to deliver the images to your account. Flagging every error is certainly useful but often not easy to program?
Have you ever succeeded in uploading images to your account? If so, is something different with the images in this recent attempt?
Ken
No, I’ve never been…
Ken,
No, I’ve never been able to upload an image. Several people have told me I should use VPhot rather than ASTAP and I’d like to give it a try but it just doesn’t work for me. Without any sort of error reporting I’m just shooting in the dark. I’d be happy to send an image to someone and they can see if they can upload it. But I really suspect there is a problem in the headers somewhere.
Bill
Following Pete's advice above, I added the EQUINOX key to the header and now it seems to be working. Thanks Pete.