This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 11.29 23:48:19.40 +61:01:54.5
115.36322 -0.90907 galactic Cas Second-epoch detections are separated by 3.1" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | EM Cas | 23:48:13.91 +61:01:54.5 (Gaia DR3) | SRA (local) | 272.500000000000 (local) | Gaia3var=VARIABLE SpType: M6 1954ApJ...120..118N [NB54] 380
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:48:19.40 +61:01:54.5: 13.35 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:48:19.40 +61:01:54.5: 13.62 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.44 +/- 0.03
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 48 19.40 +61 01 54.5 11.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
EM Cas,2461180.8124,11.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
EM Cas 20260520.3124 11.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 14.17 23:53:15.41 +64:39:07.5
116.75381 2.48051 galactic Cas Second-epoch detections are separated by 3.1" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2017217564792125568 | 23:53:12.41 +64:39:44.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:53:15.41 +64:39:07.5: 15.43 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:53:15.41 +64:39:07.5: 15.94 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.43 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 53 15.41 +64 39 07.5 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2017217564792125568,2461180.8124,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2017217564792125568 20260520.3124 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 14.13 23:56:48.40 +62:27:18.8
116.66306 0.25027 galactic Cas Second-epoch detections are separated by 5.0" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:56:48.40 +62:27:18.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:56:48.40 +62:27:18.8: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:56:48.40 +62:27:18.8: 15.56 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 56 48.40 +62 27 18.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,14.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 14.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.93 23:47:07.44 +61:51:12.6
115.42494 -0.07726 galactic Cas Second-epoch detections are separated by 1.1" and 2.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:47:07.44 +61:51:12.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:47:07.44 +61:51:12.6: 16.01 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:47:07.44 +61:51:12.6: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 47 07.44 +61 51 12.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.91 00:00:54.63 +62:47:27.9
117.19306 0.48369 galactic Cas Second-epoch detections are separated by 6.0" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430048379509991936 | 00:00:59.48 +62:47:56.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:00:54.63 +62:47:27.9: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:00:54.63 +62:47:27.9: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 00 54.63 +62 47 27.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430048379509991936,2461180.8124,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430048379509991936 20260520.3124 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 14.00 23:47:49.72 +60:50:37.4
115.25924 -1.07692 galactic Cas Second-epoch detections are separated by 1.4" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:47:49.72 +60:50:37.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:47:49.72 +60:50:37.4: 15.52 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:47:49.72 +60:50:37.4: 15.94 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.52 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 47 49.72 +60 50 37.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.67 00:09:22.42 +63:07:57.8
118.20040 0.64805 galactic Cas Second-epoch detections are separated by 4.8" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:22.42 +63:07:57.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:09:22.42 +63:07:57.8: 14.96 +/- 0.16 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:09:22.42 +63:07:57.8: 15.50 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.09 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 09 22.42 +63 07 57.8 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.84 23:49:35.80 +65:55:38.5
116.67577 3.80960 galactic Cas Second-epoch detections are separated by 2.6" and 1.0 pix
The object was found in VSX23" Gaia DR3 2209737072952052480
Type: ROT
# Max. Min./Amp. JD0 Period
14.060 G 14.090 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:49:35.80 +65:55:38.5: 16.11 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:49:35.80 +65:55:38.5: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 49 35.80 +65 55 38.5 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2209737072952052480,2461180.8124,13.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2209737072952052480 20260520.3124 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.60 00:05:44.00 +63:49:37.1
117.91748 1.40109 galactic Cas Second-epoch detections are separated by 6.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:44.00 +63:49:37.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:05:44.00 +63:49:37.1: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:05:44.00 +63:49:37.1: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 05 44.00 +63 49 37.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.75 23:29:21.36 +57:22:37.4
112.01505 -3.74458 galactic Cas Second-epoch detections are separated by 3.2" and 2.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:21.36 +57:22:37.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:29:21.36 +57:22:37.4: 14.85 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:29:21.36 +57:22:37.4: 15.72 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 14.85 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 29 21.36 +57 22 37.4 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.68 23:24:17.20 +57:20:28.2
111.35498 -3.55857 galactic Cas Second-epoch detections are separated by 3.8" and 1.8 pix
The object was found in VSX24" Gaia DR3 2009364444729400320
Type: VAR
# Max. Min./Amp. JD0 Period
17.190 G 17.350 G 0.018612000000 K
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:24:17.20 +57:20:28.2: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:24:17.20 +57:20:28.2: 15.55 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 24 17.20 +57 20 28.2 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2009364444729400320,2461180.8124,13.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2009364444729400320 20260520.3124 13.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.61 00:04:51.74 +63:07:42.3
117.69741 0.73100 galactic Cas Second-epoch detections are separated by 1.7" and 1.2 pix
The object was found in VSX 2" ZTF J000451.57+630744.3
Type: EW
# Max. Min./Amp. JD0 Period
18.413 r Y 0.230 r 2458360.81730 0.270130600000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:04:51.74 +63:07:42.3: 16.04 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:04:51.74 +63:07:42.3: 15.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 04 51.74 +63 07 42.3 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J000451.57+630744.3,2461180.8124,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J000451.57+630744.3 20260520.3124 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.60 23:40:11.53 +61:31:48.3
114.54742 -0.17642 galactic Cas Second-epoch detections are separated by 0.8" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:40:11.53 +61:31:48.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:40:11.53 +61:31:48.3: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:40:11.53 +61:31:48.3: 15.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 40 11.53 +61 31 48.3 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.46 23:59:11.58 +64:51:27.1
117.41657 2.54672 galactic Cas Second-epoch detections are separated by 3.7" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:59:11.58 +64:51:27.1 (user input) | T | P | (position from user input) J-Ks=0.685+/-0.116 (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:59:11.58 +64:51:27.1: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:59:11.58 +64:51:27.1: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 59 11.58 +64 51 27.1 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.63 23:49:39.43 +60:53:29.3
115.48677 -1.08409 galactic Cas Second-epoch detections are separated by 3.0" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ZTF J234933.89+605349.5 | 23:49:33.90 +60:53:49.4 (Gaia DR3) | SR (local) | 2458457.21070 (local) | Gaia3var=NOT_AVAILABLE J-Ks=0.441+/-0.083 (G)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:49:39.43 +60:53:29.3: 14.65 +/- 0.13 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:49:39.43 +60:53:29.3: 14.69 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.66 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 49 39.43 +60 53 29.3 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J234933.89+605349.5,2461180.8124,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J234933.89+605349.5 20260520.3124 13.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.43 23:57:16.36 +62:35:51.7
116.74543 0.37834 galactic Cas Second-epoch detections are separated by 3.9" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:16.36 +62:35:51.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:57:16.36 +62:35:51.7: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:57:16.36 +62:35:51.7: 15.72 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 57 16.36 +62 35 51.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.46 00:04:26.37 +63:27:46.0
117.71103 1.06844 galactic Cas Second-epoch detections are separated by 3.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:04:26.37 +63:27:46.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:04:26.37 +63:27:46.0: 15.46 +/- 0.22 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:04:26.37 +63:27:46.0: 15.86 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.46 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 04 26.37 +63 27 46.0 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.29 23:23:23.46 +65:43:45.0
114.04335 4.38839 galactic Cep Second-epoch detections are separated by 1.2" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:23.46 +65:43:45.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:23:23.46 +65:43:45.0: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:23:23.46 +65:43:45.0: 15.59 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.22 00:19:24.50 +65:50:02.7
119.65773 3.16616 galactic Cas Second-epoch detections are separated by 2.0" and 1.2 pix
The object was found in VSX15" ZTF J001922.23+654956.2
Type: RS
# Max. Min./Amp. JD0 Period
16.483 r Y 0.086 r 2458281.96510 0.484081700000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:19:24.50 +65:50:02.7: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:19:24.50 +65:50:02.7: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 19 24.50 +65 50 02.7 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J001922.23+654956.2,2461180.8124,13.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J001922.23+654956.2 20260520.3124 13.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.95 00:26:19.99 +64:01:23.7
120.18666 1.28540 galactic Cas Second-epoch detections are separated by 4.1" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:26:19.99 +64:01:23.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:26:19.99 +64:01:23.7: 14.64 +/- 0.13 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:26:19.99 +64:01:23.7: 14.36 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.47 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 26 19.99 +64 01 23.7 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.69 00:25:56.61 +65:07:48.3
120.25366 2.39099 galactic Cas Second-epoch detections are separated by 2.9" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:25:56.61 +65:07:48.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:25:56.61 +65:07:48.3: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:25:56.61 +65:07:48.3: 15.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 25 56.61 +65 07 48.3 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 11.58 23:22:25.11 +61:51:09.3
112.63917 0.77283 galactic Cas Second-epoch detections are separated by 1.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2015731647852056832 | 23:22:20.90 +61:50:44.2 (Gaia DR3) | RS (local) | (local) | Gaia3var=NOT_AVAILABLE SpType: F3: 1935BSD...C01....0S BSD 19-1767
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:22:25.11 +61:51:09.3: 12.98 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:22:25.11 +61:51:09.3: 14.13 +/- 0.09 detection
Forced photometry reference-image weighted average: 13.07 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 22 25.11 +61 51 09.3 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015731647852056832,2461180.8124,11.58,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2015731647852056832 20260520.3124 11.58CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.07 23:24:28.44 +61:38:25.4
112.79778 0.49168 galactic Cas Second-epoch detections are separated by 2.3" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2015667085902288384 | 23:24:28.54 +61:38:02.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A2 1935BSD...C01....0S BSD 19-1813
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:24:28.44 +61:38:25.4: 13.45 +/- 0.11 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:24:28.44 +61:38:25.4: 14.06 +/- 0.22 detection
Forced photometry reference-image weighted average: 13.57 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 24 28.44 +61 38 25.4 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015667085902288384,2461180.8124,12.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2015667085902288384 20260520.3124 12.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.52 23:45:41.71 +63:53:33.0
115.77539 1.93800 galactic Cas Second-epoch detections are separated by 1.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:45:41.71 +63:53:33.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:45:41.71 +63:53:33.0: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:45:41.71 +63:53:33.0: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 45 41.71 +63 53 33.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.53 23:42:50.98 +61:24:48.0
114.82196 -0.37374 galactic Cas Second-epoch detections are separated by 0.8" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:50.98 +61:24:48.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:50.98 +61:24:48.0: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:42:50.98 +61:24:48.0: 15.65 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 42 50.98 +61 24 48.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.63 23:42:48.94 +61:39:26.4
114.88209 -0.13723 galactic Cas Second-epoch detections are separated by 2.0" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:48.94 +61:39:26.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:48.94 +61:39:26.4: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:42:48.94 +61:39:26.4: 15.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 42 48.94 +61 39 26.4 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.76 23:53:17.38 +61:56:48.6
116.15255 -0.15712 galactic Cas Second-epoch detections are separated by 6.4" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:53:17.38 +61:56:48.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:53:17.38 +61:56:48.6: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:53:17.38 +61:56:48.6: 15.53 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 53 17.38 +61 56 48.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.78 00:16:42.42 +65:59:32.9
119.40451 3.35887 galactic Cas Second-epoch detections are separated by 5.6" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:16:42.42 +65:59:32.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:16:42.42 +65:59:32.9: 16.16 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:16:42.42 +65:59:32.9: 15.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 16 42.42 +65 59 32.9 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.91 23:38:47.72 +61:19:09.3
114.32887 -0.33323 galactic Cas Second-epoch detections are separated by 1.9" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ASASSN-V J233841.62+611906.2 | 23:38:41.61 +61:19:05.8 (Gaia DR3) | L (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:38:47.72 +61:19:09.3: 15.04 +/- 0.16 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:38:47.72 +61:19:09.3: 14.82 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.93 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 38 47.72 +61 19 09.3 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J233841.62+611906.2,2461180.8124,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J233841.62+611906.2 20260520.3124 12.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.81 00:33:25.99 +63:45:32.6
120.94310 0.95685 galactic Cas Second-epoch detections are separated by 0.5" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ZTF J003327.29+634611.8 | 00:33:27.30 +63:46:11.8 (Gaia DR3) | SR (local) | 2458277.38890 (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:33:25.99 +63:45:32.6: 15.90 +/- 0.33 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:33:25.99 +63:45:32.6: 14.30 +/- 0.09 detection
Forced photometry reference-image weighted average: 14.41 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 33 25.99 +63 45 32.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J003327.29+634611.8,2461180.8124,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J003327.29+634611.8 20260520.3124 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.78 00:41:41.25 +65:49:31.4
121.93258 2.97256 galactic Cas Second-epoch detections are separated by 5.0" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:41:41.25 +65:49:31.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:41:41.25 +65:49:31.4: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:41:41.25 +65:49:31.4: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 41 41.25 +65 49 31.4 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.04 23:27:25.70 +65:38:08.3
114.40652 4.16402 galactic Cep Second-epoch detections are separated by 1.9" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:25.70 +65:38:08.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:27:25.70 +65:38:08.3: 15.03 +/- 0.20 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:27:25.70 +65:38:08.3: 14.92 +/- 0.22 detection
Forced photometry reference-image weighted average: 14.98 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.14 23:46:20.38 +61:59:27.9
115.36965 0.07891 galactic Cas Second-epoch detections are separated by 8.2" and 1.1 pix
The object was found in VSX16" ZTF J234618.05+615926.5
Type: RS
# Max. Min./Amp. JD0 Period
18.196 g Y 0.067 g 2458363.78450 0.468494700000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:46:20.38 +61:59:27.9: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:46:20.38 +61:59:27.9: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 46 20.38 +61 59 27.9 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J234618.05+615926.5,2461180.8124,13.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J234618.05+615926.5 20260520.3124 13.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.24 23:48:49.80 +61:16:40.8
115.48190 -0.68487 galactic Cas Second-epoch detections are separated by 0.7" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:49.80 +61:16:40.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:48:49.80 +61:16:40.8: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:48:49.80 +61:16:40.8: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 48 49.80 +61 16 40.8 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.32 00:05:50.93 +62:30:05.1
117.69684 0.09396 galactic Cas Second-epoch detections are separated by 3.5" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:50.93 +62:30:05.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:05:50.93 +62:30:05.1: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:05:50.93 +62:30:05.1: 15.60 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.60 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 05 50.93 +62 30 05.1 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.51 23:42:25.82 +61:28:21.0
114.78919 -0.30347 galactic Cas Second-epoch detections are separated by 4.3" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:25.82 +61:28:21.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:25.82 +61:28:21.0: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:42:25.82 +61:28:21.0: 15.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 42 25.82 +61 28 21.0 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.47 23:59:15.83 +63:47:47.8
117.21058 1.50594 galactic Cas Second-epoch detections are separated by 3.6" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:59:15.83 +63:47:47.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:59:15.83 +63:47:47.8: 15.61 +/- 0.28 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:59:15.83 +63:47:47.8: 15.75 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.61 +/- 0.28
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 59 15.83 +63 47 47.8 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.54 23:46:07.19 +61:58:41.5
115.34143 0.07288 galactic Cas Second-epoch detections are separated by 4.9" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:46:07.19 +61:58:41.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:46:07.19 +61:58:41.5: 15.07 +/- 0.18 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:46:07.19 +61:58:41.5: 15.62 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.19 +/- 0.16
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 46 07.19 +61 58 41.5 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.66 23:30:58.74 +62:16:23.2
113.72385 0.84847 galactic Cas Second-epoch detections are separated by 2.1" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:58.74 +62:16:23.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:30:58.74 +62:16:23.2: 15.41 +/- 0.23 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:30:58.74 +62:16:23.2: 15.60 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.41 +/- 0.23
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 30 58.74 +62 16 23.2 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.76 00:02:07.61 +63:18:06.5
117.42656 0.95836 galactic Cas Second-epoch detections are separated by 1.5" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:02:07.61 +63:18:06.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:02:07.61 +63:18:06.5: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:02:07.61 +63:18:06.5: 15.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 02 07.61 +63 18 06.5 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.85 00:05:20.61 +63:23:38.7
117.79816 0.98271 galactic Cas Second-epoch detections are separated by 0.3" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:20.61 +63:23:38.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:05:20.61 +63:23:38.7: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:05:20.61 +63:23:38.7: 15.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 05 20.61 +63 23 38.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.71 00:13:38.70 +63:26:08.0
118.72148 0.87318 galactic Cas Second-epoch detections are separated by 1.5" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Large-amplitude variable Gaia DR2 431444656196144896 | 00:13:38.70 +63:26:08.0 (user input) | 2021A&A...648A..44M | | (position from user input) (the VSX policy as of May 2022 seems to be NOT to regard variables from 2021A&A...648A..44M as 'known' for the lack of classification)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:13:38.70 +63:26:08.0: 15.91 +/- 0.33 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:13:38.70 +63:26:08.0: 15.52 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.69 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 13 38.70 +63 26 08.0 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Large-amplitude variable Gaia DR2 431444656196144896,2461180.8124,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Large-amplitude variable Gaia DR2 431444656196144896 20260520.3124 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.71 00:23:33.01 +65:19:35.9
120.02443 2.61244 galactic Cas Second-epoch detections are separated by 4.1" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:33.01 +65:19:35.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:23:33.01 +65:19:35.9: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:23:33.01 +65:19:35.9: 15.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 23 33.01 +65 19 35.9 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 14.05 23:58:57.71 +64:02:49.5
117.22855 1.75796 galactic Cas Second-epoch detections are separated by 1.8" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:58:57.71 +64:02:49.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:58:57.71 +64:02:49.5: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:58:57.71 +64:02:49.5: 15.52 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.52 +/- 0.28
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 58 57.71 +64 02 49.5 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.09 00:24:12.31 +57:57:08.5
119.31311 -4.72791 galactic Cas Second-epoch detections are separated by 1.6" and 1.6 pix
The object was found in VSX 2" NSVS J0024122+575706
Type: SR
# Max. Min./Amp. JD0 Period
12.979 r Y 0.517 r 2458470.85960 232.234431800000 M6.5
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:24:12.31 +57:57:08.5: 14.40 +/- 0.08 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:24:12.31 +57:57:08.5: 14.17 +/- 0.07 detection
Forced photometry reference-image weighted average: 14.27 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 24 12.31 +57 57 08.5 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0024122+575706,2461180.8124,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0024122+575706 20260520.3124 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.81 23:29:40.00 +64:59:20.5
114.42425 3.47670 galactic Cep Second-epoch detections are separated by 5.0" and 0.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:40.00 +64:59:20.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:29:40.00 +64:59:20.5: 16.08 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:29:40.00 +64:59:20.5: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 11.63 23:48:17.70 +61:01:53.9
115.35986 -0.90840 galactic Cas Second-epoch detections are separated by 2.6" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | EM Cas | 23:48:13.91 +61:01:54.5 (Gaia DR3) | SRA (local) | 272.500000000000 (local) | Gaia3var=VARIABLE SpType: M6 1954ApJ...120..118N [NB54] 380
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:48:17.70 +61:01:53.9: 13.34 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:48:17.70 +61:01:53.9: 13.65 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.43 +/- 0.03
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 23 48 17.70 +61 01 53.9 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
EM Cas,2461180.8124,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
EM Cas 20260520.3124 11.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 13.06 00:11:19.44 +64:18:31.8
118.60033 1.77497 galactic Cas Second-epoch detections are separated by 5.7" and 2.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:19.44 +64:18:31.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:11:19.44 +64:18:31.8: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:11:19.44 +64:18:31.8: 15.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 11 19.44 +64 18 31.8 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,13.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 13.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.43 00:34:24.54 +64:31:42.2
121.10159 1.71718 galactic Cas Second-epoch detections are separated by 5.7" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:34:24.54 +64:31:42.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:34:24.54 +64:31:42.2: 15.99 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:34:24.54 +64:31:42.2: 15.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 34 24.54 +64 31 42.2 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 05 20.3124 2461180.8124 12.38 00:07:42.54 +64:42:19.8
118.28056 2.22940 galactic Cas Second-epoch detections are separated by 3.3" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:42.54 +64:42:19.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:07:42.54 +64:42:19.8: 15.96 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 00:07:42.54 +64:42:19.8: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 05 20.3123* 00 07 42.54 +64 42 19.8 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461180.8124,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260520.3124 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461061.56554947 21.01.2026 01:34:13.474 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
First image: 2461061.56554947 21.01.2026 01:34:13.474 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Last image: 2461180.81262507 20.05.2026 07:30:00.806 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 5
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.66
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 6 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 10.0 # minimum number of pixels above threshold
DETECT_THRESH 10.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 10.0 # or , in mag.arcsec-2
SATUR_LEVEL 55000.0 # level (in ADUs) at which arises saturation
GAIN 0.37 # detector gain in e-/ADU
Total objects detected (at least 2 times): 22268
Objects passed selection criteria: 22153
Measurements per detected object (mean, median, min, max): 2.6 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.6 2.0 2 4
Average stars detected per image: 15884.2
Average stars matched: 14914 (93.8917 %)
Memory usage VmPeak: 126432 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue May 19 15:05:05 CDT 2026
VaST build number 1.0rc89-63-g0e0f9022
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-05-19)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed May 20 03:17:18 CDT 2026
Host name: tau
############################################################
## VaST run with SExtractor config file default.sex.telephoto_lens_vSTL ##
Images processed 4
Images used for photometry 4
Ref. image: 2461061.56554947 21.01.2026 01:34:13.474 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
First image: 2461061.56554947 21.01.2026 01:34:13.474 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Last image: 2461180.81262507 20.05.2026 07:30:00.806 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 337
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.32
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 74 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 2.0 # minimum number of pixels above threshold
DETECT_THRESH 3.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 3.0 # or , in mag.arcsec-2
SATUR_LEVEL 57000.0 # level (in ADUs) at which arises saturation
GAIN 0.83 # detector gain in e-/ADU
WEIGHT_TYPE BACKGROUND
Total objects detected (at least 2 times): 174513
Objects passed selection criteria: 173993
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 129697
Average stars matched: 120981 (93.2795 %)
Memory usage VmPeak: 2057416 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue May 19 15:05:05 CDT 2026
VaST build number 1.0rc89-63-g0e0f9022
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-05-19)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed May 20 03:53:39 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ2b1x1/TTUQ2_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
SExtractor catalog cache: saved Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_onlybrightstars_v1
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461180.81207843
Re-using ../tocp_transients_list.txt
'../tocp_transients_list.txt' -> 'tocp_transients_list.txt'
Re-using ../tns_transients_list.txt
'../tns_transients_list.txt' -> 'tns_transients_list.txt'
Plate-solving the images
'../asassn_transients_list.txt' -> 'asassn_transients_list.txt'
wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits'
wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits'
wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits'
wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits (1st reference image)
verification OK: wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Image size: 943.5'x628.6' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.91"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 23:59:58.597 +61:59:18.65 J2000 4789.000 3195.000
###################################
The image scale is 5.91"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits (1st new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Image size: 941.7'x627.3' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:07.913 +62:00:32.03 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 23:59:58.597 +61:59:18.65
Second-epoch image center 00:00:07.913 +62:00:32.03
Angular distance between the image centers 0.0273 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits (2nd new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Image size: 941.6'x627.2' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:06.652 +62:00:29.58 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 23:59:58.597 +61:59:18.65
Second-epoch image center 00:00:06.652 +62:00:29.58
Angular distance between the image centers 0.0252 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 00:00:07.913 +62:00:32.03
Second-epoch second image center 00:00:06.652 +62:00:29.58
Angular distance between the image centers 0.00256 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits &> /tmp/tmp.VaVERPK6ZF
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits &> /tmp/tmp.CYEBANmwA9
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits &> /tmp/tmp.gOK5CwvThQ
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits &> /tmp/tmp.vb8ULBtw3w
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits and wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits and wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat
Found non-empty wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits and wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat
The reference image (wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits) and catalog (wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat) found
'wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat' -> 'wcsmag.cat'
Read 30227 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0004 to 359.9985 deg, Dec +55.3299 to +67.4069 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0004 to 359.9985 deg, Dec 55.3299 to 67.4069 deg
Loaded 133369 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 1543 out of 1717 total matches.
Matched with Tycho-2 1717 out of 30227 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.924800
a=0.000000 b=1.000000 c=22.924800
From vast_summary.log: estimated ref. image limiting mag.: -7.66
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.26
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.26
Lightcurve magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 30227 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0004 to 359.9985 deg, Dec +55.3299 to +67.4069 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0004 to 359.9985 deg, Dec 55.3299 to 67.4069 deg
Loaded 133369 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 1543 out of 1717 total matches.
Matched with Tycho-2 1717 out of 30227 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits:
Forced-photometry filter: calibrated wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits -> calib.txt_param_ref_wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits (aperture=5.8)
Read 25266 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0007 to 359.9981 deg, Dec +55.2924 to +67.4366 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0007 to 359.9981 deg, Dec 55.2924 to 67.4366 deg
Loaded 134115 Tycho-2 stars within the image boundaries (VT and BT non-zero).
Relation between the catalog and instrumental magnitudes is written to calib.txt
Stars used for magnitude calibration (good matches): 14213 out of 15744 total matches.
Matched with Tycho-2 15744 out of 25266 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits:
Forced-photometry filter: calibrated wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits -> calib.txt_param_ref_wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits (aperture=6.0)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 5 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.1 pix Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
2.1 pix Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
2.1 pix wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
2.1 pix wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
Limiting magnitude estimates:
15.3 mag. Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
15.1 mag. Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
14.0 mag. fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
14.1 mag. fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
All-image limiting magnitude estimate: 14.0 (SNR ) 11.3 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.VaVERPK6ZF (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits' -> 'wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat
SExtractor catalog parsing summary: zero_flux=4, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3557, passed=30223
Got 30223 stars (including 26629 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat
util/solve_plate_with_UCAC5 got 30223 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 943.5'
Seting catalog search parameters based on the expected field of view 943.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013104 (47.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010483 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.1650 through 0 to 19.9057, gap 19.9057 to 341.1650
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 949 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 906 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.37"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 938 matched stars entering correct_measured_positions(), 27480 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.60"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.1693 through 0 to 19.9052, gap 19.9052 to 341.1693
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 27495 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.56"
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 28289 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.26"
Excluding outliers - 968 stars left (next iteration limit 1031)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits N_match=968 sigma_overall_arcsec=2.074 sigma_q1_arcsec=1.555 sigma_q2_arcsec=1.706 sigma_q3_arcsec=1.337 sigma_q4_arcsec=1.498 n_q1=165 n_q2=270 n_q3=234 n_q4=299 worst_quadrant_to_overall_ratio=0.822
The image catalog is written to wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits -region wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.CYEBANmwA9 (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits' -> 'wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat corresponding to the image wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2950, passed=25266
Got 25266 stars (including 22295 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat
util/solve_plate_with_UCAC5 got 25266 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.8'
Seting catalog search parameters based on the expected field of view 941.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013081 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010464 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.2805 through 0 to 20.0270, gap 20.0270 to 341.2805
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 980 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 979 matched stars entering correct_measured_positions(), 949 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.47"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 979 matched stars entering correct_measured_positions(), 24075 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.45"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.2799 through 0 to 20.0270, gap 20.0270 to 341.2799
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 980 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 979 matched stars entering correct_measured_positions(), 24070 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.45"
Accuracy estimation diagnostic: 979 matched stars entering correct_measured_positions(), 24070 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.47"
Excluding outliers - 979 stars left (next iteration limit 1076)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits N_match=979 sigma_overall_arcsec=0.476 sigma_q1_arcsec=0.578 sigma_q2_arcsec=0.429 sigma_q3_arcsec=0.450 sigma_q4_arcsec=0.387 n_q1=200 n_q2=260 n_q3=232 n_q4=287 worst_quadrant_to_overall_ratio=1.213
The image catalog is written to wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits -region wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.gOK5CwvThQ (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=916, passed=13132
Got 13132 stars (including 12201 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat
util/solve_plate_with_UCAC5 got 13132 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.7'
Seting catalog search parameters based on the expected field of view 941.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013079 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010463 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6701 through 0 to 18.9835, gap 18.9835 to 340.6701
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 561 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 452 matched stars entering correct_measured_positions(), 413 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.84"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 431 matched stars entering correct_measured_positions(), 6643 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.53"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6630 through 0 to 18.9951, gap 18.9951 to 340.6630
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 622 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 562 matched stars entering correct_measured_positions(), 6710 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.38"
Accuracy estimation diagnostic: 562 matched stars entering correct_measured_positions(), 8107 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.55"
Excluding outliers - 562 stars left (next iteration limit 474)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits N_match=562 sigma_overall_arcsec=5.462 sigma_q1_arcsec=7.281 sigma_q2_arcsec=3.006 sigma_q3_arcsec=26.808 sigma_q4_arcsec=9.168 n_q1=182 n_q2=251 n_q3=56 n_q4=73 worst_quadrant_to_overall_ratio=4.908
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits -region wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.vb8ULBtw3w (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=921, passed=13132
Got 13132 stars (including 12199 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat
util/solve_plate_with_UCAC5 got 13132 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.6'
Seting catalog search parameters based on the expected field of view 941.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013078 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010462 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6698 through 0 to 18.9834, gap 18.9834 to 340.6698
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 568 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 463 matched stars entering correct_measured_positions(), 418 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.06"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 443 matched stars entering correct_measured_positions(), 6580 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.43"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6652 through 0 to 18.9977, gap 18.9977 to 340.6652
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 628 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 568 matched stars entering correct_measured_positions(), 6635 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.31"
Accuracy estimation diagnostic: 566 matched stars entering correct_measured_positions(), 8099 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.81"
Excluding outliers - 566 stars left (next iteration limit 487)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits N_match=566 sigma_overall_arcsec=5.971 sigma_q1_arcsec=7.620 sigma_q2_arcsec=3.468 sigma_q3_arcsec=19.188 sigma_q4_arcsec=11.224 n_q1=185 n_q2=249 n_q3=68 n_q4=64 worst_quadrant_to_overall_ratio=3.214
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits -region wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
###################################
# Pre-local-correction WCS quality summary (see WCS_QUALITY_DIAG lines above)
ref1=Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits sigma_overall=2.074 worst_q_ratio=0.822
ref2=Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits sigma_overall=0.476 worst_q_ratio=1.213
new1=fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits sigma_overall=5.462 worst_q_ratio=4.908
new2=fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits sigma_overall=5.971 worst_q_ratio=3.214
reference average sigma_overall=1.275 worst_q_ratio=1.0175
warn-on-ratio threshold: 2.0x reference
###################################
WCS_QUALITY_RETRY: 1st new image (fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits) flagged: sigma=5.462 (ref avg 1.275), ratio=4.908 (ref avg 1.0175), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00003.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/lib/make_outxyls_for_astrometric_calibration found 12600 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Using the local copy of Astrometry.net code
IMAGE_SIZE= --width 9576 --height 6388 SCALE_LOW=544.5 SCALE_HIGH=3025.0
Using solve-field binary
/usr/local/astrometry/bin/solve-field
Reading input file 1 of 1: "out3138845.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3138845.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
log-odds ratio 20.2075 (5.97043e+08), 5 match, 0 conflict, 10 distractors, 198 index.
RA,Dec = (0.147418,62.014), pixel scale 5.9029 arcsec/pix.
log-odds ratio 114.352 (4.59528e+49), 44 match, 0 conflict, 142 distractors, 200 index.
RA,Dec = (359.96,62.017), pixel scale 5.93943 arcsec/pix.
Hit/miss: Hit/miss: ------+----++--++----+----+---++---++----+--------++----+---++----+----+---------+--------++---+++--
Field 1: solved with index index-4113.fits.
Field 1 solved: writing to file ./out3138845.solved to indicate this.
Field: out3138845.xyls
Field center: (RA,Dec) = (359.961696, 62.017874) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:50.807, +62:01:04.345).
Field size: 15.6128 x 10.476 degrees
Field rotation angle: up is -9.77168 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits' -> 'fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits'
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M May 20 03:29 fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
-rw-r--r-- 1 apache apache 8.5K May 20 03:29 out3138845.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits (fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits)
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration01' / astrometry.net run
Reading input file 1 of 1: "out3138845.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3138845.axy"...
Only searching for solutions within 15.5783 degrees of RA,Dec (359.963,62.0187)
log-odds ratio 25.2337 (9.09628e+10), 9 match, 0 conflict, 27 distractors, 28 index.
RA,Dec = (0.0295822,62.0072), pixel scale 5.95196 arcsec/pix.
Hit/miss: Hit/miss: -++--+-++---+----------+----------++(best)----------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3138845.solved to indicate this.
Field: out3138845.xyls
Field center: (RA,Dec) = (0.031276, 62.008043) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:07.506, +62:00:28.954).
Field size: 15.7176 x 10.5197 degrees
Field rotation angle: up is -4.32382 degrees E of N
Field parity: neg
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M May 20 03:29 fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
-rw-r--r-- 1 apache apache 8.5K May 20 03:29 out3138845.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits)... done!
done!
All done!
The WCS header appears to be added with no errors.
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration02' / astrometry.net run
The field of view is large: we'll try to run Astromety.net code on the image itself rather than a star list
Reading input file "wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 71872 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.axy"...
Verifying WCS using indices with quads of size [63.3686, 949.933] arcmin
Verifying WCS with index 39 of 61 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 40 of 61 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 41 of 61 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 42 of 61 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 43 of 61 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 2.19455
Verifying WCS with index 44 of 61 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 1.35306
Verifying WCS with index 45 of 61 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0.703142
Verifying WCS with index 46 of 61 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0.0289139
Verifying WCS using indices with quads of size [63.3686, 949.933] arcmin
Verifying WCS with index 39 of 61 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 40 of 61 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 41 of 61 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 42 of 61 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 43 of 61 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 2.19455
Verifying WCS with index 44 of 61 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 1.35306
Verifying WCS with index 45 of 61 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0.703142
Verifying WCS with index 46 of 61 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0.0289139
Got 0 solutions.
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4112.fits, field objects 21-30).
Field: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Generating wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat from image00003.cat
Catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits created.
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
Image size: 941.7'x627.3' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:07.913 +62:00:32.03 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 13132 stars ###
'wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/correct_sextractor_wcs_catalog_usingxy2sky3726470.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=916, passed=13132
Got 13132 stars (including 12201 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat
util/solve_plate_with_UCAC5 got 13132 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.7'
Seting catalog search parameters based on the expected field of view 941.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013079 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010463 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6701 through 0 to 18.9835, gap 18.9835 to 340.6701
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 561 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 452 matched stars entering correct_measured_positions(), 413 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.84"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 431 matched stars entering correct_measured_positions(), 6643 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.53"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6630 through 0 to 18.9951, gap 18.9951 to 340.6630
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 622 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 562 matched stars entering correct_measured_positions(), 6710 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.38"
Accuracy estimation diagnostic: 562 matched stars entering correct_measured_positions(), 8107 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.55"
Excluding outliers - 562 stars left (next iteration limit 474)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits N_match=562 sigma_overall_arcsec=5.462 sigma_q1_arcsec=7.281 sigma_q2_arcsec=3.006 sigma_q3_arcsec=26.808 sigma_q4_arcsec=9.168 n_q1=182 n_q2=251 n_q3=56 n_q4=73 worst_quadrant_to_overall_ratio=4.908
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits -region wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
WCS_QUALITY_RETRY: --tweak-order 2 did NOT improve 1st new image (fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits): sigma 5.462->5.462, ratio 4.908->4.908; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits) flagged: sigma=5.971 (ref avg 1.275), ratio=3.214 (ref avg 1.0175), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00004.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/lib/make_outxyls_for_astrometric_calibration found 12604 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Using the local copy of Astrometry.net code
IMAGE_SIZE= --width 9576 --height 6388 SCALE_LOW=544.5 SCALE_HIGH=3025.0
Using solve-field binary
/usr/local/astrometry/bin/solve-field
Reading input file 1 of 1: "out3789860.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3789860.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 24.941 (6.78796e+10), 6 match, 0 conflict, 7 distractors, 28 index.
RA,Dec = (0.0243269,62.0065), pixel scale 5.95188 arcsec/pix.
Hit/miss: Hit/miss: --++-+-++---+(best)----------+-------------+----+---------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3789860.solved to indicate this.
Field: out3789860.xyls
Field center: (RA,Dec) = (0.026021, 62.007363) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:06.245, +62:00:26.507).
Field size: 15.7174 x 10.5196 degrees
Field rotation angle: up is -4.31353 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits' -> 'fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits'
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M May 20 03:39 fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
-rw-r--r-- 1 apache apache 8.5K May 20 03:39 out3789860.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits (fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits)
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration01' / astrometry.net run
Reading input file 1 of 1: "out3789860.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3789860.axy"...
Only searching for solutions within 15.6933 degrees of RA,Dec (0.0277167,62.0082)
log-odds ratio 24.941 (6.78796e+10), 6 match, 0 conflict, 7 distractors, 28 index.
RA,Dec = (0.0243269,62.0065), pixel scale 5.95188 arcsec/pix.
Hit/miss: Hit/miss: --++-+-++---+(best)----------+-------------+----+---------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3789860.solved to indicate this.
Field: out3789860.xyls
Field center: (RA,Dec) = (0.026021, 62.007363) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:06.245, +62:00:26.507).
Field size: 15.7174 x 10.5196 degrees
Field rotation angle: up is -4.31353 degrees E of N
Field parity: neg
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M May 20 03:39 fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
-rw-r--r-- 1 apache apache 8.5K May 20 03:39 out3789860.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits)... done!
done!
All done!
The WCS header appears to be added with no errors.
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration02' / astrometry.net run
The field of view is large: we'll try to run Astromety.net code on the image itself rather than a star list
Reading input file "wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 72359 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.axy"...
Verifying WCS using indices with quads of size [63.3677, 949.92] arcmin
Verifying WCS with index 39 of 61 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 40 of 61 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 41 of 61 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 42 of 61 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 43 of 61 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 6.91363
Verifying WCS with index 44 of 61 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 5.61579
Verifying WCS with index 45 of 61 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 4.31252
Verifying WCS with index 46 of 61 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 2.95946
Verifying WCS using indices with quads of size [63.3677, 949.92] arcmin
Verifying WCS with index 39 of 61 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 40 of 61 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 41 of 61 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 42 of 61 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 43 of 61 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 6.91363
Verifying WCS with index 44 of 61 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 5.61579
Verifying WCS with index 45 of 61 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 4.31252
Verifying WCS with index 46 of 61 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 2.95946
Got 0 solutions.
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4112.fits, field objects 21-30).
Field: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Generating wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat from image00004.cat
Catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits created.
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
Image size: 941.6'x627.2' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:06.652 +62:00:29.58 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 13132 stars ###
'wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/correct_sextractor_wcs_catalog_usingxy2sky1178547.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=921, passed=13132
Got 13132 stars (including 12199 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat
util/solve_plate_with_UCAC5 got 13132 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.6'
Seting catalog search parameters based on the expected field of view 941.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013078 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010462 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6698 through 0 to 18.9834, gap 18.9834 to 340.6698
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 568 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 463 matched stars entering correct_measured_positions(), 418 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.06"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 443 matched stars entering correct_measured_positions(), 6580 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.43"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.6652 through 0 to 18.9977, gap 18.9977 to 340.6652
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 628 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 568 matched stars entering correct_measured_positions(), 6635 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.31"
Accuracy estimation diagnostic: 566 matched stars entering correct_measured_positions(), 8099 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.81"
Excluding outliers - 566 stars left (next iteration limit 487)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits N_match=566 sigma_overall_arcsec=5.971 sigma_q1_arcsec=7.620 sigma_q2_arcsec=3.468 sigma_q3_arcsec=19.188 sigma_q4_arcsec=11.224 n_q1=185 n_q2=249 n_q3=68 n_q4=64 worst_quadrant_to_overall_ratio=3.214
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits -region wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
WCS_QUALITY_RETRY: --tweak-order 2 did NOT improve 2nd new image (fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits): sigma 5.971->5.971, ratio 3.214->3.214; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=5.462 -- 4.28x the reference average (1.275); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=5.971 -- 4.68x the reference average (1.275); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=4.908 -- 4.82x the reference average (1.0175); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=3.214 -- 3.16x the reference average (1.0175); plate solution may be of low accuracy
Distribution of catalog-matched stars across the image:
plot_astrometric_residuals_xy: wrote wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015_astrometric_residuals.png (968 matched stars from wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.cat.astrometric_residuals, image 9576x6388)
plot_astrometric_residuals_xy: wrote wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009_astrometric_residuals.png (979 matched stars from wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits.cat.astrometric_residuals, image 9576x6388)
plot_astrometric_residuals_xy: wrote wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324_astrometric_residuals.png (562 matched stars from wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits.cat.astrometric_residuals, image 9576x6388)
plot_astrometric_residuals_xy: wrote wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325_astrometric_residuals.png (566 matched stars from wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits.cat.astrometric_residuals, image 9576x6388)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-29-13_20.00sec_4.90C_LIGHT_0324.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-05-20_CI_Cas-02-Q2b1x1_031113_TTUQ2b1x1_1432937_oAOcu9LH/wcs_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325.fits'
Preparing the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:48:19.40 +61:01:54.5: 13.35 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-02-10_20-23-50_20.00sec_-15.00C_LIGHT_0009.fits at 23:48:19.40 +61:01:54.5: 13.62 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.44 +/- 0.03
Forced photometry filter KEPT candidate at 23:48:19.40 +61:01:54.5: ref_mag=13.44 +/- 0.03 new_mean_mag=11.2891 delta=2.15 (need > 0.90)
Adding exclusion_list_local.txt__out15755.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 11s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 1s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50388_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 50388_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50981_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 50981_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:36:59.15 +63:07:58.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52809_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 52809_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:07:05.33 +61:48:55.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 53080_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 53080_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231618_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231618_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231620_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231620_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231623_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231623_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231625_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231625_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231635_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231635_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231647_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231647_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231653_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231653_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231657_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231657_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231663_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231663_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231665_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231665_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231676_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231676_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231677_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231677_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (24.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231679_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231679_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231681_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231681_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231685_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231685_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231689_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231689_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231690_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231690_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231694_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231694_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231695_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231695_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231702_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231702_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231705_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231705_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231706_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231706_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231707_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231707_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231709_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231709_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231710_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231710_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231713_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231713_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231718_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231718_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:29:00.96 +60:37:40.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231721_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231721_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231723_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231723_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231724_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231724_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231725_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231725_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231728_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231728_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231729_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231729_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231730_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231730_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231733_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231733_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231734_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231734_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231736_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231736_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231737_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231737_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231738_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231738_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231739_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231739_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:41:34.12 +59:35:30.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231742_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231742_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231744_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231744_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231746_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231746_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231747_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231747_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231751_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231751_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231752_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231752_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231759_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231759_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231760_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231760_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:58:35.24 +61:12:00.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231763_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231763_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231765_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231765_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231766_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231766_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231771_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231771_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231774_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231774_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231777_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231777_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231778_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231778_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231779_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231779_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231780_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231780_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231781_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231781_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231782_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231782_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231783_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231783_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:15:53.07 +59:25:17.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231785_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231785_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231786_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231786_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.3 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231787_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231787_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231788_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231788_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231790_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231790_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231791_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231791_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231792_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231792_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231794_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231794_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:09:29.36 +62:35:17.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231796_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231796_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231798_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231798_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231800_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231800_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:58:29.45 +61:13:05.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231802_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231802_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231805_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231805_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (29.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231810_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231810_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:26:36.56 +59:44:02.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231811_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231811_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:06:20.17 +58:23:25.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231812_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231812_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231815_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231815_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:30:12.81 +60:16:19.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231816_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231816_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:16:13.47 +60:59:35.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231817_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 231817_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 231818_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 231818_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (31.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 233901_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 233901_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:33:16.94 +62:54:24.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 234658_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 234658_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:21:25.90 +59:13:55.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 234831_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 234831_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 235743_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 235743_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 235871_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 235871_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:48:43.21 +62:14:41.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 236201_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 236201_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 236346_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 236346_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 236765_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 236765_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:04:20.73 +60:09:28.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 236864_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 236864_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 237096_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 237096_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 237558_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 237558_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 237684_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 237684_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:36:20.13 +60:18:17.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 237807_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 237807_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 237815_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 237815_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 238236_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 238236_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:57:31.94 +61:02:51.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 238288_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 238288_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 238292_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 238292_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 238475_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 238475_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 238777_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 238777_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:04:53.00 +61:20:34.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 238866_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 238866_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 239257_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 239257_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 239442_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 239442_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 239448_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 239448_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 239512_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 239512_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 239878_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 239878_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240086_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 240086_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240136_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 240136_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240263_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 240263_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (37.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240288_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 240288_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240585_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 240585_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240588_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 240588_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240707_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 240707_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240774_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 240774_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 240886_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 240886_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (32.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241212_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241212_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:09:19.68 +58:04:55.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241330_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 241330_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241409_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241409_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241469_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241469_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241472_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241472_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241481_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241481_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241495_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 241495_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241818_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241818_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 241912_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 241912_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242035_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242035_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242208_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242208_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242383_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242383_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242489_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242489_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242673_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242673_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:26:33.34 +62:14:18.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242714_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242714_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242906_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242906_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242942_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 242942_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243087_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243087_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243233_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243233_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243259_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243259_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:35:58.03 +62:41:13.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243308_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243308_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:01:59.88 +59:58:01.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243320_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243320_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:37:51.80 +57:31:04.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243345_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243345_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:58:56.15 +60:16:15.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243452_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243452_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243530_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243530_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:32:41.71 +57:53:38.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243599_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243599_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:18:22.18 +58:16:18.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243666_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243666_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:59:34.33 +60:17:49.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243796_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243796_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243798_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243798_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243854_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 243854_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243911_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 243911_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243959_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 243959_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244121_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244121_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244160_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244160_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:16:48.80 +62:33:34.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244302_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244302_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244390_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244390_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:27:10.56 +60:41:53.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244424_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244424_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:04:32.16 +62:17:25.9 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244428_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244428_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:57:26.13 +61:03:13.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244446_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244446_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:01:34.31 +61:11:27.4 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244571_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244571_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244679_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244679_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244687_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244687_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244779_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244779_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244816_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244816_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244837_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244837_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:05:14.27 +61:17:31.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244848_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244848_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244902_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 244902_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244969_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244969_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244979_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 244979_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245011_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245011_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245051_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245051_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245065_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245065_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:59:39.34 +60:16:58.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245282_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245282_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245512_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245512_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:23:19.76 +62:17:19.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245753_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245753_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:05:43.10 +58:17:43.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245808_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245808_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245929_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245929_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245959_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 245959_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246052_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246052_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246063_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246063_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246076_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246076_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246276_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246276_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:58:06.71 +61:01:35.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246295_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246295_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246371_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246371_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:25:00.07 +62:22:41.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246376_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246376_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246401_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246401_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246470_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246470_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246521_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246521_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:10:41.97 +59:41:31.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246641_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246641_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:29:53.09 +60:13:31.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246697_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246697_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246751_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246751_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246828_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 246828_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246883_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 246883_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247031_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247031_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247032_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247032_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247205_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247205_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247206_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 247206_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247403_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247403_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247423_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247423_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247673_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247673_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:23:53.44 +60:22:46.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247801_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247801_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247854_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247854_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:57:09.65 +60:59:55.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247933_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247933_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:17:16.26 +62:50:54.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247940_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 247940_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:35:29.14 +61:53:04.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248107_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248107_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248123_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248123_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248154_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248154_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:29:48.17 +58:31:42.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248200_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248200_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248276_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 248276_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248295_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248295_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248421_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248421_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248455_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248455_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:25:13.91 +62:31:45.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248551_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248551_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248584_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248584_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248632_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248632_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248751_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248751_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248905_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 248905_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249004_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249004_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249122_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249122_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249167_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249167_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249351_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 249351_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249377_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 249377_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249486_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249486_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249523_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249523_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249547_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249547_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249744_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249744_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249883_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 249883_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250062_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250062_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:19:04.74 +59:42:36.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250066_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250066_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250262_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 250262_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250484_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250484_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250652_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250652_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250722_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250722_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250735_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250735_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250829_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250829_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250865_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 250865_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (32.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251049_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251049_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251056_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251056_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251077_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251077_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:17:13.30 +62:51:11.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251108_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251108_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251194_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251194_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251300_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251300_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251829_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 251829_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252005_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252005_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:22:25.45 +59:41:04.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252012_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252012_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252089_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 252089_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252094_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252094_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252110_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252110_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252149_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 252149_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252230_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252230_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252253_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252253_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252381_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252381_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252485_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 252485_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252815_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252815_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252991_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 252991_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253059_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 253059_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253280_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 253280_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253576_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 253576_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (35.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253740_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 253740_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253883_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 253883_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254004_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254004_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254125_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254125_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.3 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254131_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254131_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254256_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 254256_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254333_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254333_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254489_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254489_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254497_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254497_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254500_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254500_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254518_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254518_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254519_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254519_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.2 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254558_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254558_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.3 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254614_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254614_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254625_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254625_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254685_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 254685_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.2 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187990_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 187990_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 28638_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 28638_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 131202_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 131202_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:04:40.66 +60:22:02.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 48441_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 48441_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:36:59.00 +63:08:02.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 120176_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 120176_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35779_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 35779_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 23869_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 23869_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187975_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 187975_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 23:58:36.40 +58:25:43.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 29649_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
Preparing report for the candidate 29649_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 95534_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 95534_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (28.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 106367_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 106367_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
**** FOUND 00:29:27.22 +60:49:51.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31624_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 31624_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 94160_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 94160_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate due to large distance (30.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 14438_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325
The candidate 14438_fd_Cas-02-Q2b1x1_2026-05-20_02-30-00_20.00sec_5.00C_LIGHT_0325 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
make_report_in_HTML.sh Phase 2 (HTML assembly): 3s
make_report_in_HTML.sh TOTAL: 118s
Prepared the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
23:48:19.40 +61:01:54.5
23:48:17.70 +61:01:53.9
00:24:12.31 +57:57:08.5
23:53:15.41 +64:39:07.5
23:56:48.40 +62:27:18.8
23:47:07.44 +61:51:12.6
00:00:54.63 +62:47:27.9
23:47:49.72 +60:50:37.4
00:09:22.42 +63:07:57.8
23:49:35.80 +65:55:38.5
00:05:44.00 +63:49:37.1
23:29:21.36 +57:22:37.4
23:24:17.20 +57:20:28.2
00:04:51.74 +63:07:42.3
23:40:11.53 +61:31:48.3
23:59:11.58 +64:51:27.1
23:49:39.43 +60:53:29.3
23:57:16.36 +62:35:51.7
00:04:26.37 +63:27:46.0
23:23:23.46 +65:43:45.0
00:19:24.50 +65:50:02.7
00:26:19.99 +64:01:23.7
00:25:56.61 +65:07:48.3
23:22:25.11 +61:51:09.3
23:24:28.44 +61:38:25.4
23:45:41.71 +63:53:33.0
23:42:50.98 +61:24:48.0
00:34:24.54 +64:31:42.2
23:42:48.94 +61:39:26.4
23:53:17.38 +61:56:48.6
00:16:42.42 +65:59:32.9
23:38:47.72 +61:19:09.3
00:33:25.99 +63:45:32.6
00:41:41.25 +65:49:31.4
23:27:25.70 +65:38:08.3
23:46:20.38 +61:59:27.9
23:48:49.80 +61:16:40.8
00:05:50.93 +62:30:05.1
23:42:25.82 +61:28:21.0
23:59:15.83 +63:47:47.8
23:46:07.19 +61:58:41.5
23:30:58.74 +62:16:23.2
00:02:07.61 +63:18:06.5
00:05:20.61 +63:23:38.7
00:13:38.70 +63:26:08.0
00:23:33.01 +65:19:35.9
23:58:57.71 +64:02:49.5
23:29:40.00 +64:59:20.5
00:07:42.54 +64:42:19.8
00:11:19.44 +64:18:31.8
########### Completed Cas-02-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
23:48:19.40 +61:01:54.5
23:53:15.41 +64:39:07.5
23:56:48.40 +62:27:18.8
23:47:07.44 +61:51:12.6
00:00:54.63 +62:47:27.9
23:47:49.72 +60:50:37.4
00:09:22.42 +63:07:57.8
23:49:35.80 +65:55:38.5
00:05:44.00 +63:49:37.1
23:29:21.36 +57:22:37.4
23:24:17.20 +57:20:28.2
00:04:51.74 +63:07:42.3
23:40:11.53 +61:31:48.3
23:59:11.58 +64:51:27.1
23:49:39.43 +60:53:29.3
23:57:16.36 +62:35:51.7
00:04:26.37 +63:27:46.0
23:23:23.46 +65:43:45.0
00:19:24.50 +65:50:02.7
00:26:19.99 +64:01:23.7
00:25:56.61 +65:07:48.3
23:22:25.11 +61:51:09.3
23:24:28.44 +61:38:25.4
23:45:41.71 +63:53:33.0
23:42:50.98 +61:24:48.0
23:42:48.94 +61:39:26.4
23:53:17.38 +61:56:48.6
00:16:42.42 +65:59:32.9
23:38:47.72 +61:19:09.3
00:33:25.99 +63:45:32.6
00:41:41.25 +65:49:31.4
23:27:25.70 +65:38:08.3
23:46:20.38 +61:59:27.9
23:48:49.80 +61:16:40.8
00:05:50.93 +62:30:05.1
23:42:25.82 +61:28:21.0
23:59:15.83 +63:47:47.8
23:46:07.19 +61:58:41.5
23:30:58.74 +62:16:23.2
00:02:07.61 +63:18:06.5
00:05:20.61 +63:23:38.7
00:13:38.70 +63:26:08.0
00:23:33.01 +65:19:35.9
23:58:57.71 +64:02:49.5
00:24:12.31 +57:57:08.5
23:29:40.00 +64:59:20.5
23:48:17.70 +61:01:53.9
00:11:19.44 +64:18:31.8
00:34:24.54 +64:31:42.2
00:07:42.54 +64:42:19.8
###################################################################################
23:48:19.40 +61:01:54.5 -- not an asteroid (will add it to exclusion list)
23:53:15.41 +64:39:07.5 -- not an asteroid (will add it to exclusion list)
23:56:48.40 +62:27:18.8 -- not an asteroid (will add it to exclusion list)
23:47:07.44 +61:51:12.6 -- not an asteroid (will add it to exclusion list)
00:00:54.63 +62:47:27.9 -- not an asteroid (will add it to exclusion list)
23:47:49.72 +60:50:37.4 -- not an asteroid (will add it to exclusion list)
00:09:22.42 +63:07:57.8 -- not an asteroid (will add it to exclusion list)
23:49:35.80 +65:55:38.5 -- not an asteroid (will add it to exclusion list)
00:05:44.00 +63:49:37.1 -- not an asteroid (will add it to exclusion list)
23:29:21.36 +57:22:37.4 -- not an asteroid (will add it to exclusion list)
23:24:17.20 +57:20:28.2 -- not an asteroid (will add it to exclusion list)
00:04:51.74 +63:07:42.3 -- not an asteroid (will add it to exclusion list)
23:40:11.53 +61:31:48.3 -- not an asteroid (will add it to exclusion list)
23:59:11.58 +64:51:27.1 -- not an asteroid (will add it to exclusion list)
23:49:39.43 +60:53:29.3 -- not an asteroid (will add it to exclusion list)
23:57:16.36 +62:35:51.7 -- not an asteroid (will add it to exclusion list)
00:04:26.37 +63:27:46.0 -- not an asteroid (will add it to exclusion list)
23:23:23.46 +65:43:45.0 -- not an asteroid (will add it to exclusion list)
00:19:24.50 +65:50:02.7 -- not an asteroid (will add it to exclusion list)
00:26:19.99 +64:01:23.7 -- not an asteroid (will add it to exclusion list)
00:25:56.61 +65:07:48.3 -- not an asteroid (will add it to exclusion list)
23:22:25.11 +61:51:09.3 -- not an asteroid (will add it to exclusion list)
23:24:28.44 +61:38:25.4 -- not an asteroid (will add it to exclusion list)
23:45:41.71 +63:53:33.0 -- not an asteroid (will add it to exclusion list)
23:42:50.98 +61:24:48.0 -- not an asteroid (will add it to exclusion list)
23:42:48.94 +61:39:26.4 -- not an asteroid (will add it to exclusion list)
23:53:17.38 +61:56:48.6 -- not an asteroid (will add it to exclusion list)
00:16:42.42 +65:59:32.9 -- not an asteroid (will add it to exclusion list)
23:38:47.72 +61:19:09.3 -- not an asteroid (will add it to exclusion list)
00:33:25.99 +63:45:32.6 -- not an asteroid (will add it to exclusion list)
00:41:41.25 +65:49:31.4 -- not an asteroid (will add it to exclusion list)
23:27:25.70 +65:38:08.3 -- not an asteroid (will add it to exclusion list)
23:46:20.38 +61:59:27.9 -- not an asteroid (will add it to exclusion list)
23:48:49.80 +61:16:40.8 -- not an asteroid (will add it to exclusion list)
00:05:50.93 +62:30:05.1 -- not an asteroid (will add it to exclusion list)
23:42:25.82 +61:28:21.0 -- not an asteroid (will add it to exclusion list)
23:59:15.83 +63:47:47.8 -- not an asteroid (will add it to exclusion list)
23:46:07.19 +61:58:41.5 -- not an asteroid (will add it to exclusion list)
23:30:58.74 +62:16:23.2 -- not an asteroid (will add it to exclusion list)
00:02:07.61 +63:18:06.5 -- not an asteroid (will add it to exclusion list)
00:05:20.61 +63:23:38.7 -- not an asteroid (will add it to exclusion list)
00:13:38.70 +63:26:08.0 -- not an asteroid (will add it to exclusion list)
00:23:33.01 +65:19:35.9 -- not an asteroid (will add it to exclusion list)
23:58:57.71 +64:02:49.5 -- not an asteroid (will add it to exclusion list)
00:24:12.31 +57:57:08.5 -- not an asteroid (will add it to exclusion list)
23:29:40.00 +64:59:20.5 -- not an asteroid (will add it to exclusion list)
23:48:17.70 +61:01:53.9 -- not an asteroid (will add it to exclusion list)
00:11:19.44 +64:18:31.8 -- not an asteroid (will add it to exclusion list)
00:34:24.54 +64:31:42.2 -- not an asteroid (will add it to exclusion list)
00:07:42.54 +64:42:19.8 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:54.63 +62:47:27.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:07.61 +63:18:06.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:26.37 +63:27:46.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:51.74 +63:07:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:20.61 +63:23:38.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:44.00 +63:49:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:50.93 +62:30:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:42.54 +64:42:19.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:22.42 +63:07:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:19.44 +64:18:31.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:38.70 +63:26:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:42.42 +65:59:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:24.50 +65:50:02.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:33.01 +65:19:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:12.31 +57:57:08.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:56.61 +65:07:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:19.99 +64:01:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:25.99 +63:45:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:24.54 +64:31:42.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:41.25 +65:49:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:25.11 +61:51:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:23.46 +65:43:45.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:17.20 +57:20:28.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:28.44 +61:38:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:25.70 +65:38:08.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:21.36 +57:22:37.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:40.00 +64:59:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:58.74 +62:16:23.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:47.72 +61:19:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:11.53 +61:31:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:25.82 +61:28:21.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:48.94 +61:39:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:50.98 +61:24:48.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:41.71 +63:53:33.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:07.19 +61:58:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:20.38 +61:59:27.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:07.44 +61:51:12.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:49.72 +60:50:37.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:17.70 +61:01:53.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:19.40 +61:01:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:49.80 +61:16:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:35.80 +65:55:38.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:39.43 +60:53:29.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:15.41 +64:39:07.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:17.38 +61:56:48.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:48.40 +62:27:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:16.36 +62:35:51.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:57.71 +64:02:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:11.58 +64:51:27.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:15.83 +63:47:47.8 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:00:54.63 +62:47:27.9 -- not a known variable star
00:02:07.61 +63:18:06.5 -- not a known variable star
00:04:26.37 +63:27:46.0 -- not a known variable star
00:04:51.74 +63:07:42.3 -- a known variable star
00:05:20.61 +63:23:38.7 -- not a known variable star
00:05:44.00 +63:49:37.1 -- not a known variable star
00:05:50.93 +62:30:05.1 -- not a known variable star
00:07:42.54 +64:42:19.8 -- not a known variable star
00:09:22.42 +63:07:57.8 -- not a known variable star
00:11:19.44 +64:18:31.8 -- not a known variable star
00:13:38.70 +63:26:08.0 -- not a known variable star
00:16:42.42 +65:59:32.9 -- not a known variable star
00:19:24.50 +65:50:02.7 -- a known variable star
00:23:33.01 +65:19:35.9 -- not a known variable star
00:24:12.31 +57:57:08.5 -- a known variable star
00:25:56.61 +65:07:48.3 -- not a known variable star
00:26:19.99 +64:01:23.7 -- not a known variable star
00:33:25.99 +63:45:32.6 -- not a known variable star
00:34:24.54 +64:31:42.2 -- not a known variable star
00:41:41.25 +65:49:31.4 -- not a known variable star
23:22:25.11 +61:51:09.3 -- not a known variable star
23:23:23.46 +65:43:45.0 -- not a known variable star
23:24:17.20 +57:20:28.2 -- a known variable star
23:24:28.44 +61:38:25.4 -- not a known variable star
23:27:25.70 +65:38:08.3 -- not a known variable star
23:29:21.36 +57:22:37.4 -- not a known variable star
23:29:40.00 +64:59:20.5 -- not a known variable star
23:30:58.74 +62:16:23.2 -- not a known variable star
23:38:47.72 +61:19:09.3 -- not a known variable star
23:40:11.53 +61:31:48.3 -- not a known variable star
23:42:25.82 +61:28:21.0 -- not a known variable star
23:42:48.94 +61:39:26.4 -- not a known variable star
23:42:50.98 +61:24:48.0 -- not a known variable star
23:45:41.71 +63:53:33.0 -- not a known variable star
23:46:07.19 +61:58:41.5 -- not a known variable star
23:46:20.38 +61:59:27.9 -- a known variable star
23:47:07.44 +61:51:12.6 -- not a known variable star
23:47:49.72 +60:50:37.4 -- not a known variable star
23:48:17.70 +61:01:53.9 -- not a known variable star
23:48:19.40 +61:01:54.5 -- not a known variable star
23:48:49.80 +61:16:40.8 -- not a known variable star
23:49:35.80 +65:55:38.5 -- a known variable star
23:49:39.43 +60:53:29.3 -- not a known variable star
23:53:15.41 +64:39:07.5 -- not a known variable star
23:53:17.38 +61:56:48.6 -- not a known variable star
23:56:48.40 +62:27:18.8 -- not a known variable star
23:57:16.36 +62:35:51.7 -- not a known variable star
23:58:57.71 +64:02:49.5 -- not a known variable star
23:59:11.58 +64:51:27.1 -- not a known variable star
23:59:15.83 +63:47:47.8 -- not a known variable star
Found 44 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
50 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 50 (excluding asteroids and hot pixels, 44 new), not updating the exclusion list!
###################################################################################
Not allowed to update the exclusion list IS_THIS_TEST_RUN=NO ALLOW_EXCLUSION_LIST_UPDATE= NO
The observatory MPC code is V36
############################################################
Positions of planets computed with util/planet_finder/main.py for JD(UT)2461180.81207843 -observatory V36
04:15:04.73 +22:22:03.7 Mercury (-1.7mag)
06:05:02.57 +25:04:04.6 Venus (-3.9mag)
01:55:14.40 +11:00:52.2 Mars (1.3mag)
07:33:32.88 +22:06:15.6 Jupiter (-1.9mag)
00:43:14.43 +02:13:59.8 Saturn (0.9mag)
03:55:38.41 +20:12:03.8 Uranus (5.8mag)
00:14:43.37 +00:08:33.8 Neptune (7.8mag)
20:34:06.26 -22:58:19.5 Pluto (14.5mag)
07:17:35.30 +25:05:17.2 Moon (-9.3mag)
-rw-r--r-- 1 apache apache 362 May 20 03:17 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461180.81207843:
07:33:39.77 +22:05:56.8 Io (5.9mag)
07:33:23.48 +22:06:39.9 Europa (6.1mag)
07:33:44.83 +22:05:49.3 Ganymede (5.5mag)
07:34:04.92 +22:04:51.8 Callisto (6.7mag)
07:34:59.64 +21:43:14.1 Himalia (15.5mag)
07:33:37.50 +22:06:02.7 Thebe (16.4mag)
07:35:23.70 +22:06:57.1 Elara (17.5mag)
07:34:39.85 +22:28:10.1 Pasiphae (17.6mag)
07:40:53.07 +22:06:43.8 Carme (18.8mag)
00:43:06.70 +02:14:25.7 Titan (8.7mag)
00:43:16.50 +02:14:12.8 Rhea (10.0mag)
00:43:24.35 +02:13:04.7 Iapetus (11.4mag)
00:43:20.25 +02:13:35.0 Hyperion (14.7mag)
00:44:18.63 +02:18:35.0 Phoebe (16.7mag)
-rw-r--r-- 1 apache apache 569 May 20 03:17 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461180.81207843:
17:10:58.34 -32:00:30.4 JWST
07:04:07.17 -09:10:26.5 Chandra
08:48:47.91 -49:45:54.0 XMM-Newton
-rw-r--r-- 1 apache apache 96 May 20 03:17 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461180.81207843 -observatory V36
13:26:18.13 -27:39:18.4 14.5mag D/1884 O1 (Barnard)
06:27:13.43 +30:48:25.9 15.8mag D/1886 K1 (Brooks)
15:31:42.90 +01:03:22.0 14.7mag D/1895 Q1 (Swift)
05:18:45.99 +24:25:18.0 17.1mag D/1918 W1 (Schorr)
08:48:58.03 +19:38:41.3 17.8mag P/2009 WX51 (Catalina)
18:53:21.19 -31:11:39.3 13.7mag P/2010 H2 (Vales)
05:35:22.78 -68:24:05.1 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:42:19.00 +31:44:32.7 17.4mag C/2017 K2 (PANSTARRS)
17:22:02.14 +14:05:35.6 17.7mag C/2021 G2 (ATLAS)
23:14:49.27 +30:46:44.1 17.2mag C/2022 E2 (ATLAS)
05:10:45.45 +26:46:43.6 16.3mag C/2022 N2 (PANSTARRS)
09:17:25.62 +31:38:51.5 16.5mag C/2022 QE78 (ATLAS)
08:41:23.34 +02:50:14.6 17.6mag C/2022 R6 (PANSTARRS)
18:39:44.44 +20:56:05.8 17.7mag C/2023 A3 (Tsuchinshan-ATLAS)
15:26:55.59 -11:04:45.2 17.5mag P/2023 B1 (PANSTARRS)
08:59:40.94 -07:16:50.9 18.0mag C/2023 F3 (ATLAS)
22:15:27.77 +65:14:37.7 17.7mag C/2023 H5 (Lemmon)
18:29:36.32 -05:06:15.9 13.8mag C/2023 R1 (PANSTARRS)
14:09:46.30 +86:55:04.8 17.9mag C/2023 X2 (Lemmon)
06:46:30.84 +63:47:39.0 17.5mag C/2024 A1 (ATLAS)
06:17:15.54 +25:43:48.6 12.9mag C/2024 E1 (Wierzchos)
15:52:48.18 +11:30:17.3 17.3mag C/2024 G6 (ATLAS)
20:21:42.02 +25:21:47.9 14.2mag C/2024 J3 (ATLAS)
03:59:07.91 -17:50:23.0 16.1mag C/2024 T5 (ATLAS)
05:48:05.96 +37:54:38.3 17.9mag C/2025 J1 (Borisov)
11:54:02.29 +53:25:36.4 16.7mag C/2025 L1 (ATLAS)
06:11:11.98 -09:39:11.7 11.8mag C/2025 R3 (PANSTARRS)
12:42:05.60 +04:30:24.2 17.2mag C/2025 Y1 (ATLAS)
01:24:14.58 +41:50:20.7 15.6mag C/2026 B2 (Sun-Gao)
11:11:21.89 -11:48:44.8 16.2mag A/2026 E1
19:48:41.51 -08:10:00.1 9.8mag 10P/Tempel
14:21:56.74 -01:37:40.6 17.1mag 24P/Schaumasse
10:59:11.80 -00:52:19.7 15.9mag 29P/Schwassmann-Wachmann
10:47:39.31 -02:35:17.6 17.6mag 43P/Wolf-Harrington
02:42:16.45 +22:58:38.5 17.5mag 47P/Ashbrook-Jackson
08:19:48.29 +28:54:52.8 16.9mag 63P/Wild
00:08:56.68 -07:49:23.1 15.7mag 65P/Gunn
05:43:10.36 +30:37:15.2 16.4mag 76P/West-Kohoutek-Ikemura
02:24:03.73 +14:28:09.7 14.0mag 78P/Gehrels
00:36:57.24 +00:20:00.8 15.2mag 88P/Howell
03:54:03.43 +28:05:36.5 15.1mag 93P/Lovas
06:06:34.70 +33:20:23.1 15.8mag 123P/West-Hartley
09:18:14.24 +22:50:48.3 16.4mag 124P/Mrkos
03:27:59.30 +17:47:59.8 16.4mag 128P/Shoemaker-Holt
03:55:48.71 +17:55:41.8 17.7mag 131P/Mueller
04:29:33.63 +19:40:43.3 12.3mag 141P/Machholz
04:32:39.37 +15:22:32.1 12.3mag 141P-A/Machholz
03:15:14.20 +12:12:18.9 10.5mag 141P-D/Machholz
02:43:47.02 -27:37:46.5 17.5mag 161P/Hartley-IRAS
02:41:48.15 +15:31:12.4 14.8mag 162P/SidingSpring
19:32:21.52 -03:02:58.6 17.8mag 169P/NEAT
17:06:41.28 -09:54:00.7 16.2mag 235P/LINEAR
06:51:35.79 +35:55:08.0 17.3mag 240P/NEAT
23:43:29.95 -10:00:23.5 16.9mag 260P/McNaught
03:15:18.04 +28:39:37.5 17.7mag 295P/LINEAR
21:03:30.84 -33:55:53.6 17.9mag 320P/McNaught
15:24:58.76 +08:21:23.4 17.4mag 391P/Kowalski
07:53:03.94 +21:08:27.7 17.8mag 450P/LONEOS
06:29:14.17 +42:58:07.4 17.7mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K May 20 03:17 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
01:13:11.60 -33:25:16.10 ASASSN-26dg 2026-05-13.41 16.8
16:44:31.77 -27:15:18.40 AT2026mhn 2026-05-12.33 15.8
21:23:11.57 -19:09:45.00 AT2026kwu 2026-05-12.26 16.9
14:20:14.30 -30:20:51.90 AT2026ktm 2026-05-12.06 17.21
14:41:39.01 -37:13:46.40 AT2026lkm 2026-05-11.18 16.89
12:59:50.45 -10:58:38.80 SN2026kep 2026-05-9.06 17.5
13:37:29.61 -29:50:30.90 AT2026lkd 2026-05-9.09 17.23
09:46:42.01 -14:52:03.60 SN2026kmo 2026-05-8.99 17.51
15:03:05.28 +22:02:03.80 AT2026lxf 2026-05-8.34 13.72
10:23:49.41 -20:57:25.30 ASASSN-26df 2026-05-8.21 16.52
22:14:40.56 +05:04:51.60 2026lda 2026-05-7.56 16.2
21:35:33.81 -14:05:16.30 ASASSN-26de 2026-05-6.29 14.51
16:21:49.13 -61:36:14.60 ASASSN-26dd 2026-05-5.15 15.93
14:26:40.22 -24:48:37.50 AT2026lig 2026-05-4.27 14.63
13:17:51.04 +30:25:13.50 SN2026kcp 2026-05-4.46 16.43
11:27:55.57 -13:38:56.90 SN2026kza 2026-05-1.08 15.59
22:28:27.10 +30:17:54.30 SN 2026fov 2026-04-29.6 14.36
21:00:10.71 -32:17:03.90 AT2026kis 2026-04-27.36 16.15
14:32:57.37 -58:13:26.40 ASASSN-26dc 2026-04-27.27 13.42
15:32:05.35 -43:54:34.60 ASASSN-26db 2026-04-27.37 16.06
16:34:34.94 -54:34:58.20 ASASSN-26da 2026-04-25.14 15.99
10:06:55.04 -01:13:49.70 SN2026jsg 2026-04-24.99 16.28
15:15:57.17 +56:18:32.80 SN2026kid 2026-04-24.52 -3.65
07:58:28.45 +57:03:42.40 AT2026kcf 2026-04-24.2 16.89
11:38:21.80 -50:43:06.50 SN2026jkb 2026-04-24.24 15.38
10:06:11.41 -39:41:04.20 AT2026dil 2026-04-24.2 16.85
14:21:40.08 +13:13:46.30 SN2026jlm 2026-04-22.16 15.12
10:53:55.42 -16:06:08.10 ASASSN-26cz 2026-04-22.12 16.24
01:13:11.60 -33:25:16.10 2026-05-13.41 16.8
13:45:02.03 +15:17:14.50 ASASSN-26cy 2026-04-21.27 15.78
13:20:52.22 -35:57:03.60 AT2026jcm 2026-04-19.01 16.65
13:36:15.66 -36:53:48.40 SN 2026iqy 2026-04-18.92 17.31
06:34:01.33 -40:07:34.00 ASASSN-26cx 2026-04-19.07 16.16
23:33:57.97 -45:12:11.90 SN 2026idu 2026-04-19.41 15.9
12:10:50.92 +66:55:31.20 SN 2026icv 2026-04-17.14 16.03
21:36:59.06 -60:43:35.90 ASASSN-26cv 2026-04-17.35 -1.18
08:13:26.26 -27:07:30.50 ASASSN-26cw 2026-04-17.07 -1.01
14:49:14.01 -27:29:20.10 ASASSN-26cu 2026-04-16.29 -2.7
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
01:13:11.60 -33:25:16.10 2026-05-13.41 16.8
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:35.90 ASASSN-26co 2026-04-7.15 14.93
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.80 -63:44:05.50 ASASSN-26ch 2026-03-27.86 13.02
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.88 -53:16:33.80 ASASSN-26cc 2026-03-20.04 15.48
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.96 -45:55:38.40 ASASSN-26bt 2026-03-18.8 16.32
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
-rw-r--r-- 1 apache apache 5.8K May 20 03:17 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
00:43:35.02 +41:46:28.0 PNV J00433502+4146280 2026-04-23.056 15.9mag
00:42:55.64 +41:14:12.2 PNV J00425564+4114122 2026-04-24.042 16.2mag
21:14:03.38 +56:46:44.1 TCP J21140338+5646441 2026-05-05.3534 16.7mag
15:03:05.19 +22:02:04.1 TCP J15030519+2202041 2026-05-08.3260 13.9mag
07:15:18.25 +47:53:16.7 TCP J07151825+4753167 2026-05-09.1599 14.4mag
16:00:18.44 -22:30:10.6 TCP J16001844-2230106 2026-05-09.6135 13.3mag
00:42:47.45 +41:16:58.5 PNV J00424745+4116585 2026-05-10.030 16.8mag
09:55:02.89 +69:02:13.8 PNV J09550289+6902138 2026-05-18.925 20.7mag
-rw-r--r-- 1 apache apache 188K May 20 03:17 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
14:50:45.748 +66:34:54.91 AT 2026mlk 2026-05-11.30 20.4091
18:57:13.399 -48:39:14.45 AT 2026mlj 2026-05-13.22 19.233
07:10:35.982 -68:41:17.89 AT 2026mli 2026-05-12.97 19.219
17:52:46.431 +47:52:46.86 AT 2026mlh 2026-05-08.38 20.1882
14:13:17.140 -79:34:21.34 SN 2026mlg 2026-05-13.16 19.098
13:01:56.482 -31:45:10.71 SN 2026mlf 2026-05-12.13 19.007
07:54:45.643 -77:42:34.01 AT 2026mle 2026-05-13.07 19.016
20:30:20.180 -54:23:56.77 AT 2026mld 2026-05-13.27 18.409
22:04:13.307 -62:36:12.13 AT 2026mlc 2026-05-13.37 18.826
05:26:12.032 -40:06:08.32 AT 2026mlb 2026-05-13.00 18.67
19:42:54.081 +00:48:22.14 AT 2026mla 2026-05-13.45 19.82
19:30:52.401 +01:28:25.46 AT 2026mkz 2026-05-10.43 18.98
19:16:53.816 +07:01:58.07 AT 2026mky 2026-05-13.38 19.79
18:26:55.952 +08:19:11.34 AT 2026mkx 2026-05-09.34 18.11
18:46:00.564 +05:06:38.95 AT 2026mkw 2026-05-08.40 19.71
14:09:28.410 +14:24:05.48 AT 2026mkv 2026-05-13.26 20.45
10:19:49.459 +35:57:58.03 AT 2026mku 2026-05-08.16 20.5914
08:06:09.530 +34:06:49.84 AT 2026mkt 2026-05-09.16 19.864
10:53:32.277 +43:02:13.19 AT 2026mks 2026-05-08.20 19.7954
18:01:16.824 +61:44:43.86 AT 2026mkr 2026-05-11.93 20.08
-rw-r--r-- 1 apache apache 30K May 20 03:17 tns_transients_list.txt
