This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df
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 07 09.3433 2461230.8433 11.11 23:32:12.26 +52:55:03.9
111.02081 -8.11184 galactic Cas Second-epoch detections are separated by 3.3" and 5.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:32:12.26 +52:55:03.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:32:12.26 +52:55:03.9: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:32:12.26 +52:55:03.9: 15.58 +/- 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 07 09.3433* 23 32 12.26 +52 55 03.9 11.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,2461230.8433,11.11,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 20260709.3433 11.11CV 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 07 09.3433 2461230.8433 11.17 00:20:44.11 +50:11:43.0
117.90984 -12.37685 galactic Cas Second-epoch detections are separated by 4.9" and 6.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:20:44.11 +50:11:43.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:44.11 +50:11:43.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:44.11 +50:11:43.0: 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 07 09.3433* 00 20 44.11 +50 11 43.0 11.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,2461230.8433,11.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
target 20260709.3433 11.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 07 09.3433 2461230.8433 11.70 00:02:19.07 +54:08:11.0
115.70241 -8.04443 galactic Cas Second-epoch detections are separated by 8.0" and 6.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 | Gaia DR3 420317392359633792 | 00:02:21.60 +54:07:41.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:19.07 +54:08:11.0: 14.83 +/- 0.15 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:19.07 +54:08:11.0: 15.07 +/- 0.19 detection
Forced photometry reference-image weighted average: 14.93 +/- 0.12
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 07 09.3433* 00 02 19.07 +54 08 11.0 11.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 420317392359633792,2461230.8433,11.70,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 420317392359633792 20260709.3433 11.70CV 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 07 09.3433 2461230.8433 11.97 00:13:33.15 +53:52:03.8
117.30040 -8.58926 galactic Cas Second-epoch detections are separated by 8.8" and 6.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 | 00:13:33.15 +53:52:03.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:13:33.15 +53:52:03.8: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:13:33.15 +53:52:03.8: 15.73 +/- 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 07 09.3433* 00 13 33.15 +53 52 03.8 12.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,2461230.8433,11.97,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 20260709.3433 11.97CV 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 07 09.3433 2461230.8433 11.22 00:11:08.37 +52:33:49.5
116.73658 -9.82257 galactic Cas Second-epoch detections are separated by 4.1" and 5.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 395919813453369600 | 00:11:11.92 +52:33:26.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:11:08.37 +52:33:49.5: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:11:08.37 +52:33:49.5: 15.61 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.61 +/- 0.33
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 07 09.3433* 00 11 08.37 +52 33 49.5 11.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 395919813453369600,2461230.8433,11.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
Gaia DR3 395919813453369600 20260709.3433 11.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 07 09.3433 2461230.8433 10.64 23:38:16.61 +56:01:35.0
112.78613 -5.39745 galactic Cas Second-epoch detections are separated by 3.8" and 5.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:38:16.61 +56:01:35.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:38:16.61 +56:01:35.0: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:38:16.61 +56:01:35.0: 15.58 +/- 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 07 09.3433* 23 38 16.61 +56 01 35.0 10.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,2461230.8433,10.64,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 20260709.3433 10.64CV 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 07 09.3433 2461230.8433 7.33 23:58:27.04 +51:26:22.6
114.57717 -10.57054 galactic Cas Second-epoch detections are separated by 4.4" and 6.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:58:27.04 +51:26:22.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:27.04 +51:26:22.6: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:27.04 +51:26:22.6: 15.47 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.47 +/- 0.34
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 07 09.3433* 23 58 27.04 +51 26 22.6 7.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,2461230.8433,7.33,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 20260709.3433 7.33CV 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 07 09.3433 2461230.8433 14.20 23:44:45.09 +58:01:07.3
114.17360 -3.71458 galactic Cas Second-epoch detections are separated by 2.9" and 6.4 pix
The object was found in VSX16" ZTF J234444.44+580122.9
Type: EA
# Max. Min./Amp. JD0 Period
14.423 r Y 0.143 r 2458657.92850 2.154041200000
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:44:45.09 +58:01:07.3: 14.92 +/- 0.17 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:44:45.09 +58:01:07.3: 15.64 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.08 +/- 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!
TCP 2026 07 09.3433* 23 44 45.09 +58 01 07.3 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
ZTF J234444.44+580122.9,2461230.8433,14.20,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 J234444.44+580122.9 20260709.3433 14.20CV 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 07 09.3433 2461230.8433 14.32 23:46:04.57 +54:20:47.4
113.41520 -7.31308 galactic Cas Second-epoch detections are separated by 6.2" and 5.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:46:04.57 +54:20:47.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:46:04.57 +54:20:47.4: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:46:04.57 +54:20:47.4: 15.92 +/- 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 07 09.3433* 23 46 04.57 +54 20 47.4 14.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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.21 23:47:18.24 +54:24:27.4
113.60514 -7.29863 galactic Cas Second-epoch detections are separated by 7.0" and 6.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:47:18.24 +54:24:27.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:47:18.24 +54:24:27.4: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:47:18.24 +54:24:27.4: 15.83 +/- 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 07 09.3433* 23 47 18.24 +54 24 27.4 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
target,2461230.8433,14.21,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 20260709.3433 14.21CV 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 07 09.3433 2461230.8433 14.39 00:05:48.00 +55:40:11.5
116.48323 -6.62942 galactic Cas Second-epoch detections are separated by 8.6" and 5.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:05:48.00 +55:40:11.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:48.00 +55:40:11.5: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:05:48.00 +55:40:11.5: 15.63 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.63 +/- 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 07 09.3433* 00 05 48.00 +55 40 11.5 14.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,2461230.8433,14.39,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 20260709.3433 14.39CV 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 07 09.3433 2461230.8433 14.05 23:32:49.97 +51:33:20.2
110.69454 -9.43876 galactic Cas Second-epoch detections are separated by 3.5" and 6.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:32:49.97 +51:33:20.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:32:49.97 +51:33:20.2: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:32:49.97 +51:33:20.2: 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 07 09.3433* 23 32 49.97 +51 33 20.2 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 14.04 00:20:45.15 +54:18:08.9
118.41708 -8.30006 galactic Cas Second-epoch detections are separated by 7.8" and 6.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:20:45.15 +54:18:08.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:45.15 +54:18:08.9: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:45.15 +54:18:08.9: 15.88 +/- 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 07 09.3433* 00 20 45.15 +54 18 08.9 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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.00 23:50:46.61 +52:51:41.2
113.73215 -8.92335 galactic Cas Second-epoch detections are separated by 1.4" and 5.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:50:46.61 +52:51:41.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:50:46.61 +52:51:41.2: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:50:46.61 +52:51:41.2: 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 07 09.3433* 23 50 46.61 +52 51 41.2 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.90 23:48:32.96 +55:00:38.1
113.92988 -6.75822 galactic Cas Second-epoch detections are separated by 1.6" and 5.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:48:32.96 +55:00:38.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:48:32.96 +55:00:38.1: 15.50 +/- 0.24 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:48:32.96 +55:00:38.1: 14.94 +/- 0.14 detection
Forced photometry reference-image weighted average: 15.08 +/- 0.12
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 07 09.3433* 23 48 32.96 +55 00 38.1 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,2461230.8433,13.90,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 20260709.3433 13.90CV 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 07 09.3433 2461230.8433 13.84 23:37:48.55 +55:18:46.0
112.52060 -6.06362 galactic Cas Second-epoch detections are separated by 7.5" and 5.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:37:48.55 +55:18:46.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:37:48.55 +55:18:46.0: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:37:48.55 +55:18:46.0: 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 07 09.3433* 23 37 48.55 +55 18 46.0 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,2461230.8433,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
target 20260709.3433 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 07 09.3433 2461230.8433 13.81 00:03:44.46 +50:50:07.8
115.28423 -11.32663 galactic Cas Second-epoch detections are separated by 4.1" and 5.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 | ATO J000.9201+50.8319 | 00:03:44.46 +50:50:07.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:03:44.46 +50:50:07.8: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:03:44.46 +50:50:07.8: 15.98 +/- 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 07 09.3433* 00 03 44.46 +50 50 07.8 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
ATO J000.9201+50.8319,2461230.8433,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
ATO J000.9201+50.8319 20260709.3433 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 07 09.3433 2461230.8433 13.88 23:52:26.35 +53:22:23.6
114.09789 -8.48355 galactic Cas Second-epoch detections are separated by 2.9" and 5.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:52:26.35 +53:22:23.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:52:26.35 +53:22:23.6: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:26.35 +53:22:23.6: 15.55 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.55 +/- 0.24
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 07 09.3433* 23 52 26.35 +53 22 23.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,2461230.8433,13.88,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 20260709.3433 13.88CV 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 07 09.3433 2461230.8433 13.74 00:15:30.46 +52:00:00.6
117.32196 -10.47978 galactic Cas Second-epoch detections are separated by 8.7" and 6.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:15:30.46 +52:00:00.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:15:30.46 +52:00:00.6: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:15:30.46 +52:00:00.6: 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 07 09.3433* 00 15 30.46 +52 00 00.6 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,2461230.8433,13.74,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 20260709.3433 13.74CV 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 07 09.3433 2461230.8433 13.87 23:50:42.90 +52:47:03.3
113.70453 -8.99617 galactic Cas Second-epoch detections are separated by 1.1" and 5.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 | 23:50:42.90 +52:47:03.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:50:42.90 +52:47:03.3: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:50:42.90 +52:47:03.3: 15.95 +/- 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 07 09.3433* 23 50 42.90 +52 47 03.3 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,2461230.8433,13.87,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 20260709.3433 13.87CV 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 07 09.3433 2461230.8433 13.82 00:23:06.17 +56:38:59.2
119.02301 -6.00676 galactic Cas Second-epoch detections are separated by 8.2" and 5.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 421556438884382720 | 00:23:02.65 +56:39:11.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:23:06.17 +56:38:59.2: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:06.17 +56:38:59.2: 15.49 +/- 0.27 detection
Forced photometry reference-image weighted average: 15.49 +/- 0.27
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 07 09.3433* 00 23 06.17 +56 38 59.2 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 421556438884382720,2461230.8433,13.82,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 421556438884382720 20260709.3433 13.82CV 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 07 09.3433 2461230.8433 13.79 23:48:25.43 +53:27:14.5
113.52963 -8.26346 galactic Cas Second-epoch detections are separated by 5.0" and 5.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:25.43 +53:27:14.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:48:25.43 +53:27:14.5: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:48:25.43 +53:27:14.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 07 09.3433* 23 48 25.43 +53 27 14.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,2461230.8433,13.79,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 20260709.3433 13.79CV 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 07 09.3433 2461230.8433 13.81 23:45:17.16 +56:33:48.8
113.87131 -5.13999 galactic Cas Second-epoch detections are separated by 7.8" and 5.7 pix
The object was found in VSX16" Gaia DR3 1997987832279829376
Type: VAR
# Max. Min./Amp. JD0 Period
17.310 G 17.370 G 0.405377000000 K
ATTENTION: measured mag 13.81 is 3.5 mag brighter than the VSX record maximum brightness 17.31 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:45:17.16 +56:33:48.8: 14.78 +/- 0.15 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:45:17.16 +56:33:48.8: 14.77 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.77 +/- 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 07 09.3433* 23 45 17.16 +56 33 48.8 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 1997987832279829376,2461230.8433,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
Gaia DR3 1997987832279829376 20260709.3433 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 07 09.3433 2461230.8433 13.72 23:40:15.18 +55:54:40.3
113.02098 -5.58471 galactic Cas Second-epoch detections are separated by 4.4" and 5.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 | 23:40:15.18 +55:54:40.3 (user input) | T | P | (position from user input) J-Ks=0.540+/-0.078 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:40:15.18 +55:54:40.3: 15.49 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:40:15.18 +55:54:40.3: 15.66 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.49 +/- 0.29
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 07 09.3433* 23 40 15.18 +55 54 40.3 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,2461230.8433,13.72,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 20260709.3433 13.72CV 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 07 09.3433 2461230.8433 13.75 23:51:14.96 +52:36:43.8
113.74326 -9.18246 galactic Cas Second-epoch detections are separated by 4.9" and 5.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 | ATO J357.8061+52.6226 | 23:51:14.96 +52:36:43.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:51:14.96 +52:36:43.8: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:14.96 +52:36:43.8: 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 07 09.3433* 23 51 14.96 +52 36 43.8 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
ATO J357.8061+52.6226,2461230.8433,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
ATO J357.8061+52.6226 20260709.3433 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 07 09.3433 2461230.8433 13.65 23:34:44.95 +50:14:51.3
110.58806 -10.77712 galactic And Second-epoch detections are separated by 2.6" and 6.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:34:44.95 +50:14:51.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:34:44.95 +50:14:51.3: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:34:44.95 +50:14:51.3: 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 07 09.3433* 23 34 44.95 +50 14 51.3 13.7 U And 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,2461230.8433,13.65,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 20260709.3433 13.65CV 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 07 09.3433 2461230.8433 13.67 00:04:32.90 +52:54:20.2
115.79877 -9.31550 galactic Cas Second-epoch detections are separated by 3.7" and 6.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 | ATO J001.1222+52.9025 | 00:04:32.90 +52:54:20.2 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:32.90 +52:54:20.2: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:32.90 +52:54:20.2: 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 07 09.3433* 00 04 32.90 +52 54 20.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
ATO J001.1222+52.9025,2461230.8433,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
ATO J001.1222+52.9025 20260709.3433 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 07 09.3433 2461230.8433 13.67 00:18:03.21 +50:32:31.8
117.52093 -11.97851 galactic Cas Second-epoch detections are separated by 7.3" and 6.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 | Gaia DR3 394544217025761280 | 00:18:00.53 +50:32:34.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:18:03.21 +50:32:31.8: 15.32 +/- 0.22 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:18:03.21 +50:32:31.8: 15.29 +/- 0.22 detection
Forced photometry reference-image weighted average: 15.31 +/- 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!
TCP 2026 07 09.3433* 00 18 03.21 +50 32 31.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
Gaia DR3 394544217025761280,2461230.8433,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
Gaia DR3 394544217025761280 20260709.3433 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 07 09.3433 2461230.8433 13.52 23:35:22.67 +56:30:55.7
112.53928 -4.81377 galactic Cas Second-epoch detections are separated by 8.5" and 5.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:35:22.67 +56:30:55.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:35:22.67 +56:30:55.7: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:35:22.67 +56:30:55.7: 15.84 +/- 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 07 09.3433* 23 35 22.67 +56 30 55.7 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,2461230.8433,13.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 20260709.3433 13.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 07 09.3433 2461230.8433 13.55 00:22:04.53 +54:21:13.0
118.61672 -8.27194 galactic Cas Second-epoch detections are separated by 6.3" and 6.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 419726301779641216 | 00:22:07.02 +54:21:09.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:04.53 +54:21:13.0: 14.73 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:04.53 +54:21:13.0: 14.64 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.68 +/- 0.08
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 07 09.3433* 00 22 04.53 +54 21 13.0 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
Gaia DR3 419726301779641216,2461230.8433,13.55,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 419726301779641216 20260709.3433 13.55CV 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 07 09.3433 2461230.8433 13.51 23:51:37.10 +52:54:02.5
113.86639 -8.91491 galactic Cas Second-epoch detections are separated by 6.9" and 5.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 | ATO J357.9012+52.8883 | 23:51:37.10 +52:54:02.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:51:37.10 +52:54:02.5: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:37.10 +52:54:02.5: 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 07 09.3433* 23 51 37.10 +52 54 02.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
ATO J357.9012+52.8883,2461230.8433,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
ATO J357.9012+52.8883 20260709.3433 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 07 09.3433 2461230.8433 13.34 23:55:25.10 +51:47:33.2
114.18613 -10.12539 galactic Cas Second-epoch detections are separated by 7.0" and 6.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 | ATO J358.8546+51.8043 | 23:55:25.10 +51:47:33.2 (user input) | CBH (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:25.10 +51:47:33.2: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:55:25.10 +51:47:33.2: 15.98 +/- 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 07 09.3433* 23 55 25.10 +51 47 33.2 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
ATO J358.8546+51.8043,2461230.8433,13.34,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
ATO J358.8546+51.8043 20260709.3433 13.34CV 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 07 09.3433 2461230.8433 13.13 23:29:43.59 +54:42:05.1
111.22488 -6.30236 galactic Cas Second-epoch detections are separated by 8.0" and 5.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:43.59 +54:42:05.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:29:43.59 +54:42:05.1: 15.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:29:43.59 +54:42:05.1: 15.67 +/- 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 07 09.3433* 23 29 43.59 +54 42 05.1 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,2461230.8433,13.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 20260709.3433 13.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 07 09.3433 2461230.8433 13.12 23:36:42.47 +50:50:13.4
111.06670 -10.30501 galactic Cas Second-epoch detections are separated by 6.8" and 5.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:36:42.47 +50:50:13.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:36:42.47 +50:50:13.4: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:36:42.47 +50:50:13.4: 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 07 09.3433* 23 36 42.47 +50 50 13.4 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,2461230.8433,13.12,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 20260709.3433 13.12CV 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 07 09.3433 2461230.8433 12.83 23:45:29.28 +53:49:18.7
113.19678 -7.79867 galactic Cas Second-epoch detections are separated by 8.4" and 5.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 | 23:45:29.28 +53:49:18.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:45:29.28 +53:49:18.7: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:45:29.28 +53:49:18.7: 15.76 +/- 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 07 09.3433* 23 45 29.28 +53 49 18.7 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,2461230.8433,12.83,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 20260709.3433 12.83CV 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 07 09.3433 2461230.8433 12.74 23:33:43.42 +56:50:45.6
112.41892 -4.43107 galactic Cas Second-epoch detections are separated by 7.5" and 5.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:33:43.42 +56:50:45.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:43.42 +56:50:45.6: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:33:43.42 +56:50:45.6: 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 07 09.3433* 23 33 43.42 +56 50 45.6 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,2461230.8433,12.74,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 20260709.3433 12.74CV 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 07 09.3433 2461230.8433 12.59 23:29:17.32 +55:18:42.5
111.35713 -5.70302 galactic Cas Second-epoch detections are separated by 6.0" and 5.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 1997633755177085440 | 23:29:16.09 +55:18:13.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:29:17.32 +55:18:42.5: 14.92 +/- 0.19 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:29:17.32 +55:18:42.5: 14.73 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.81 +/- 0.12
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 07 09.3433* 23 29 17.32 +55 18 42.5 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
Gaia DR3 1997633755177085440,2461230.8433,12.59,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 1997633755177085440 20260709.3433 12.59CV 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 07 09.3433 2461230.8433 12.38 23:43:00.44 +52:41:51.6
112.53947 -8.78779 galactic Cas Second-epoch detections are separated by 7.5" and 5.8 pix
The object was found in VSX22" Gaia DR3 1993026732733577216
Type: ROT
# Max. Min./Amp. JD0 Period
12.440 G 12.460 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:00.44 +52:41:51.6: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:00.44 +52:41:51.6: 15.57 +/- 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 07 09.3433* 23 43 00.44 +52 41 51.6 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
Gaia DR3 1993026732733577216,2461230.8433,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
Gaia DR3 1993026732733577216 20260709.3433 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
Mean magnitude and position on the discovery images:
2026 07 09.3433 2461230.8433 12.11 23:43:36.10 +53:16:07.0
112.77892 -8.26062 galactic Cas Second-epoch detections are separated by 5.1" and 5.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 | 23:43:36.10 +53:16:07.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:36.10 +53:16:07.0: 15.83 +/- 0.36 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:36.10 +53:16:07.0: 15.85 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.83 +/- 0.36
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 07 09.3433* 23 43 36.10 +53 16 07.0 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
target,2461230.8433,12.11,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 20260709.3433 12.11CV 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 07 09.3433 2461230.8433 12.02 00:14:53.89 +53:15:42.4
117.41116 -9.21784 galactic Cas Second-epoch detections are separated by 3.8" and 6.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 | Gaia DR3 419245673457567232 | 00:14:52.39 +53:15:02.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F5 1927AnHar.100...33C HD 232145
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:14:53.89 +53:15:42.4: 13.47 +/- 0.05 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:53.89 +53:15:42.4: 13.48 +/- 0.05 detection
Forced photometry reference-image weighted average: 13.47 +/- 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 07 09.3433* 00 14 53.89 +53 15 42.4 12.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
Gaia DR3 419245673457567232,2461230.8433,12.02,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 419245673457567232 20260709.3433 12.02CV 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 07 09.3433 2461230.8433 12.31 23:33:26.69 +52:54:43.2
111.19912 -8.17386 galactic Cas Second-epoch detections are separated by 4.2" and 5.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 | ASASSN-V J233324.40+525459.8 | 23:33:24.39 +52:54:59.8 (Gaia DR3) | L (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:26.69 +52:54:43.2: 13.43 +/- 0.05 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:33:26.69 +52:54:43.2: 13.38 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.40 +/- 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 07 09.3433* 23 33 26.69 +52 54 43.2 12.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
ASASSN-V J233324.40+525459.8,2461230.8433,12.31,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 J233324.40+525459.8 20260709.3433 12.31CV 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 07 09.3433 2461230.8433 12.64 23:32:10.90 +52:54:26.7
111.01434 -8.12064 galactic Cas Second-epoch detections are separated by 5.4" and 5.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:32:10.90 +52:54:26.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:32:10.90 +52:54:26.7: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:32:10.90 +52:54:26.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 07 09.3433* 23 32 10.90 +52 54 26.7 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,2461230.8433,12.64,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 20260709.3433 12.64CV 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 07 09.3433 2461230.8433 12.79 00:31:48.37 +56:53:27.1
120.23916 -5.87821 galactic Cas Second-epoch detections are separated by 5.1" and 6.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 | 00:31:48.37 +56:53:27.1 (user input) | T | P | (position from user input) SpType: F9 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:31:48.37 +56:53:27.1: 13.86 +/- 0.07 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:31:48.37 +56:53:27.1: 14.03 +/- 0.09 detection
Forced photometry reference-image weighted average: 13.93 +/- 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 07 09.3433* 00 31 48.37 +56 53 27.1 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,2461230.8433,12.79,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 20260709.3433 12.79CV 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 07 09.3433 2461230.8433 12.97 00:22:44.23 +52:22:58.0
118.48857 -10.24118 galactic Cas Second-epoch detections are separated by 6.2" and 6.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 | ATO J005.6923+52.3782 | 00:22:46.35 +52:22:32.8 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:44.23 +52:22:58.0: 14.97 +/- 0.19 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:44.23 +52:22:58.0: 14.72 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.82 +/- 0.12
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 07 09.3433* 00 22 44.23 +52 22 58.0 13.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
ATO J005.6923+52.3782,2461230.8433,12.97,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
ATO J005.6923+52.3782 20260709.3433 12.97CV 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 07 09.3433 2461230.8433 13.06 00:23:22.97 +55:49:13.9
118.97021 -6.83527 galactic Cas Second-epoch detections are separated by 3.4" and 6.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 | ATO J005.8518+55.8256 | 00:23:22.97 +55:49:13.9 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:23:22.97 +55:49:13.9: 14.41 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:22.97 +55:49:13.9: 14.48 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.45 +/- 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 07 09.3433* 00 23 22.97 +55 49 13.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
ATO J005.8518+55.8256,2461230.8433,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
ATO J005.8518+55.8256 20260709.3433 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 07 09.3433 2461230.8433 12.98 00:24:38.31 +56:58:50.9
119.26875 -5.70021 galactic Cas Second-epoch detections are separated by 7.1" and 6.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 | 00:24:38.31 +56:58:50.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:24:38.31 +56:58:50.9: 14.68 +/- 0.18 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:24:38.31 +56:58:50.9: 14.38 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.49 +/- 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 07 09.3433* 00 24 38.31 +56 58 50.9 13.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,2461230.8433,12.98,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 20260709.3433 12.98CV 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 07 09.3433 2461230.8433 13.08 00:27:10.97 +50:01:18.1
118.94308 -12.66211 galactic Cas Second-epoch detections are separated by 8.4" and 6.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 | ATO J006.8007+50.0230 | 00:27:10.97 +50:01:18.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:27:10.97 +50:01:18.1: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:27:10.97 +50:01:18.1: 15.69 +/- 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 07 09.3433* 00 27 10.97 +50 01 18.1 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
ATO J006.8007+50.0230,2461230.8433,13.08,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
ATO J006.8007+50.0230 20260709.3433 13.08CV 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 07 09.3433 2461230.8433 13.10 23:53:29.10 +53:32:26.0
114.28956 -8.35594 galactic Cas Second-epoch detections are separated by 2.5" and 5.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 | ATO J358.3905+53.5461 | 23:53:29.10 +53:32:26.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:53:29.10 +53:32:26.0: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:53:29.10 +53:32:26.0: 15.43 +/- 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 07 09.3433* 23 53 29.10 +53 32 26.0 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
ATO J358.3905+53.5461,2461230.8433,13.10,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
ATO J358.3905+53.5461 20260709.3433 13.10CV 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 07 09.3433 2461230.8433 13.13 00:13:38.09 +52:03:06.5
117.03973 -10.38693 galactic Cas Second-epoch detections are separated by 8.6" and 5.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 | 00:13:38.09 +52:03:06.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:13:38.09 +52:03:06.5: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:13:38.09 +52:03:06.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!
TCP 2026 07 09.3433* 00 13 38.09 +52 03 06.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
target,2461230.8433,13.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 20260709.3433 13.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 07 09.3433 2461230.8433 13.15 00:24:51.20 +53:02:33.5
118.88484 -9.62008 galactic Cas Second-epoch detections are separated by 6.6" and 6.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:24:51.20 +53:02:33.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:24:51.20 +53:02:33.5: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:24:51.20 +53:02:33.5: 15.67 +/- 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 07 09.3433* 00 24 51.20 +53 02 33.5 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,2461230.8433,13.15,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 20260709.3433 13.15CV 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 07 09.3433 2461230.8433 13.23 23:53:49.14 +53:08:16.8
114.24729 -8.75941 galactic Cas Second-epoch detections are separated by 3.5" and 5.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 | Gaia DR3 1945434200126827520 | 23:53:52.16 +53:07:42.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F0 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:53:49.14 +53:08:16.8: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:53:49.14 +53:08:16.8: 15.97 +/- 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 07 09.3433* 23 53 49.14 +53 08 16.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
Gaia DR3 1945434200126827520,2461230.8433,13.23,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 1945434200126827520 20260709.3433 13.23CV 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 07 09.3433 2461230.8433 13.19 00:02:56.34 +56:52:15.6
116.31100 -5.37599 galactic Cas Second-epoch detections are separated by 6.9" and 6.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 | Gaia DR3 421058153960538368 | 00:02:54.10 +56:52:56.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:56.34 +56:52:15.6: 14.10 +/- 0.07 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:56.34 +56:52:15.6: 14.32 +/- 0.08 detection
Forced photometry reference-image weighted average: 14.19 +/- 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 07 09.3433* 00 02 56.34 +56 52 15.6 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
Gaia DR3 421058153960538368,2461230.8433,13.19,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 421058153960538368 20260709.3433 13.19CV 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 07 09.3433 2461230.8433 13.16 00:20:04.73 +50:09:06.4
117.79758 -12.40709 galactic Cas Second-epoch detections are separated by 8.9" and 6.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 | ATO J005.0247+50.1555 | 00:20:04.73 +50:09:06.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:04.73 +50:09:06.4: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:04.73 +50:09:06.4: 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 07 09.3433* 00 20 04.73 +50 09 06.4 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
ATO J005.0247+50.1555,2461230.8433,13.16,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
ATO J005.0247+50.1555 20260709.3433 13.16CV 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 07 09.3433 2461230.8433 13.24 00:07:37.86 +53:34:09.5
116.37746 -8.74402 galactic Cas Second-epoch detections are separated by 7.0" and 5.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:07:37.86 +53:34:09.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:07:37.86 +53:34:09.5: 14.52 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:07:37.86 +53:34:09.5: 14.60 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.56 +/- 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 07 09.3433* 00 07 37.86 +53 34 09.5 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.26 00:12:56.74 +50:00:20.0
116.61643 -12.39359 galactic Cas Second-epoch detections are separated by 3.1" and 6.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 | ATO J003.2462+49.9966 | 00:12:56.74 +50:00:20.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:12:56.74 +50:00:20.0: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:12:56.74 +50:00:20.0: 15.90 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.90 +/- 0.34
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 07 09.3433* 00 12 56.74 +50 00 20.0 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
ATO J003.2462+49.9966,2461230.8433,13.26,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
ATO J003.2462+49.9966 20260709.3433 13.26CV 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 07 09.3433 2461230.8433 13.37 23:41:52.68 +53:03:28.6
112.47064 -8.39511 galactic Cas Second-epoch detections are separated by 8.3" and 5.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:41:52.68 +53:03:28.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:41:52.68 +53:03:28.6: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:41:52.68 +53:03:28.6: 15.83 +/- 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 07 09.3433* 23 41 52.68 +53 03 28.6 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,2461230.8433,13.37,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 20260709.3433 13.37CV 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 07 09.3433 2461230.8433 13.43 23:58:59.53 +53:17:26.1
115.04577 -8.77623 galactic Cas Second-epoch detections are separated by 7.6" and 6.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:58:59.53 +53:17:26.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:59.53 +53:17:26.1: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:59.53 +53:17:26.1: 15.84 +/- 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 07 09.3433* 23 58 59.53 +53 17 26.1 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.49 00:26:27.14 +51:06:31.0
118.93349 -11.56906 galactic Cas Second-epoch detections are separated by 7.8" and 6.1 pix
The object was found in VSX15" Gaia DR3 394810745517846528
Type: ROT
# Max. Min./Amp. JD0 Period
15.320 G 15.380 G 6.382400000000 K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:26:27.14 +51:06:31.0: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:26:27.14 +51:06:31.0: 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 07 09.3433* 00 26 27.14 +51 06 31.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
Gaia DR3 394810745517846528,2461230.8433,13.49,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 394810745517846528 20260709.3433 13.49CV 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 07 09.3433 2461230.8433 13.63 00:29:32.20 +53:56:40.1
119.67424 -8.78869 galactic Cas Second-epoch detections are separated by 7.0" and 6.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 | ATO J007.3904+53.9505 | 00:29:32.20 +53:56:40.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:29:32.20 +53:56:40.1: 15.79 +/- 0.35 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:29:32.20 +53:56:40.1: 15.83 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.79 +/- 0.35
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 07 09.3433* 00 29 32.20 +53 56 40.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
ATO J007.3904+53.9505,2461230.8433,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
ATO J007.3904+53.9505 20260709.3433 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 07 09.3433 2461230.8433 13.59 00:31:11.75 +56:46:20.1
120.14621 -5.98997 galactic Cas Second-epoch detections are separated by 7.9" and 6.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:31:11.75 +56:46:20.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:31:11.75 +56:46:20.1: 15.01 +/- 0.22 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:31:11.75 +56:46:20.1: 15.06 +/- 0.21 detection
Forced photometry reference-image weighted average: 15.04 +/- 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!
TCP 2026 07 09.3433* 00 31 11.75 +56 46 20.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,2461230.8433,13.59,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 20260709.3433 13.59CV 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 07 09.3433 2461230.8433 13.57 00:25:44.55 +54:58:05.4
119.21590 -7.71808 galactic Cas Second-epoch detections are separated by 8.6" and 5.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 | 00:25:44.55 +54:58:05.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:25:44.55 +54:58:05.4: 15.39 +/- 0.35 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:25:44.55 +54:58:05.4: 15.22 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.29 +/- 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 07 09.3433* 00 25 44.55 +54 58 05.4 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,2461230.8433,13.57,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 20260709.3433 13.57CV 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 07 09.3433 2461230.8433 13.68 00:20:03.71 +51:55:20.5
118.01884 -10.64983 galactic Cas Second-epoch detections are separated by 8.3" and 5.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 | ATO J005.0070+51.9244 | 00:20:03.71 +51:55:20.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:03.71 +51:55:20.5: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:03.71 +51:55:20.5: 15.68 +/- 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 07 09.3433* 00 20 03.71 +51 55 20.5 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
ATO J005.0070+51.9244,2461230.8433,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
ATO J005.0070+51.9244 20260709.3433 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 07 09.3433 2461230.8433 13.61 00:22:23.70 +53:06:02.8
118.51907 -9.52195 galactic Cas Second-epoch detections are separated by 6.6" and 6.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:22:23.70 +53:06:02.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:23.70 +53:06:02.8: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:23.70 +53:06:02.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 07 09.3433* 00 22 23.70 +53 06 02.8 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,2461230.8433,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
target 20260709.3433 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 07 09.3433 2461230.8433 13.61 23:54:23.41 +55:37:41.3
114.88747 -6.35005 galactic Cas Second-epoch detections are separated by 5.1" and 6.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:54:23.41 +55:37:41.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:54:23.41 +55:37:41.3: 14.60 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:54:23.41 +55:37:41.3: 15.00 +/- 0.18 detection
Forced photometry reference-image weighted average: 14.73 +/- 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 07 09.3433* 23 54 23.41 +55 37 41.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,2461230.8433,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
target 20260709.3433 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 07 09.3433 2461230.8433 13.78 00:22:36.64 +51:54:06.2
118.41353 -10.71694 galactic Cas Second-epoch detections are separated by 6.7" and 6.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:22:36.64 +51:54:06.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:36.64 +51:54:06.2: 15.72 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:36.64 +51:54:06.2: 15.85 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.72 +/- 0.31
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 07 09.3433* 00 22 36.64 +51 54 06.2 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,2461230.8433,13.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 20260709.3433 13.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 07 09.3433 2461230.8433 13.69 00:25:02.62 +52:51:24.1
118.89413 -9.80800 galactic Cas Second-epoch detections are separated by 8.7" and 5.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 | ATO J006.2531+52.8645 | 00:25:01.05 +52:52:03.8 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:25:02.62 +52:51:24.1: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:25:02.62 +52:51:24.1: 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 07 09.3433* 00 25 02.62 +52 51 24.1 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
ATO J006.2531+52.8645,2461230.8433,13.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
ATO J006.2531+52.8645 20260709.3433 13.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 07 09.3433 2461230.8433 13.66 00:14:16.81 +56:52:39.6
117.84697 -5.62677 galactic Cas Second-epoch detections are separated by 6.7" and 5.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 | 00:14:16.81 +56:52:39.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:14:16.81 +56:52:39.6: 14.81 +/- 0.17 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:16.81 +56:52:39.6: 14.85 +/- 0.18 detection
Forced photometry reference-image weighted average: 14.83 +/- 0.13
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 07 09.3433* 00 14 16.81 +56 52 39.6 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.71 00:27:16.87 +54:05:35.9
119.35406 -8.61054 galactic Cas Second-epoch detections are separated by 8.9" and 6.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 | 00:27:16.87 +54:05:35.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:27:16.87 +54:05:35.9: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:27:16.87 +54:05:35.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 07 09.3433* 00 27 16.87 +54 05 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.66 00:11:48.29 +52:52:36.7
116.88728 -9.52911 galactic Cas Second-epoch detections are separated by 6.7" and 6.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:11:48.29 +52:52:36.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:11:48.29 +52:52:36.7: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:11:48.29 +52:52:36.7: 15.90 +/- 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 07 09.3433* 00 11 48.29 +52 52 36.7 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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.71 00:22:18.53 +54:16:24.8
118.64162 -8.35536 galactic Cas Second-epoch detections are separated by 7.2" and 6.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:22:18.53 +54:16:24.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:18.53 +54:16:24.8: 15.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:18.53 +54:16:24.8: 15.68 +/- 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 07 09.3433* 00 22 18.53 +54 16 24.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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.70 23:35:46.63 +49:52:31.1
110.63642 -11.18154 galactic And Second-epoch detections are separated by 3.1" and 5.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 | ATO J353.9546+49.8661 | 23:35:49.11 +49:51:58.1 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:35:46.63 +49:52:31.1: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:35:46.63 +49:52:31.1: 15.76 +/- 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 07 09.3433* 23 35 46.63 +49 52 31.1 13.7 U And 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
ATO J353.9546+49.8661,2461230.8433,13.70,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
ATO J353.9546+49.8661 20260709.3433 13.70CV 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 07 09.3433 2461230.8433 13.79 23:43:03.88 +54:27:17.2
113.01658 -7.09538 galactic Cas Second-epoch detections are separated by 7.7" and 6.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:43:03.88 +54:27:17.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:03.88 +54:27:17.2: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:03.88 +54:27:17.2: 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 07 09.3433* 23 43 03.88 +54 27 17.2 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,2461230.8433,13.79,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 20260709.3433 13.79CV 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 07 09.3433 2461230.8433 13.79 00:18:10.07 +54:09:39.8
118.02047 -8.39312 galactic Cas Second-epoch detections are separated by 7.0" and 6.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:18:10.07 +54:09:39.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:18:10.07 +54:09:39.8: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:18:10.07 +54:09:39.8: 15.86 +/- 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 07 09.3433* 00 18 10.07 +54 09 39.8 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,2461230.8433,13.79,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 20260709.3433 13.79CV 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 07 09.3433 2461230.8433 13.84 00:19:46.94 +51:04:47.8
117.86815 -11.48030 galactic Cas Second-epoch detections are separated by 8.0" and 6.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:19:46.94 +51:04:47.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:19:46.94 +51:04:47.8: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:19:46.94 +51:04:47.8: 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 07 09.3433* 00 19 46.94 +51 04 47.8 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,2461230.8433,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
target 20260709.3433 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 07 09.3433 2461230.8433 13.80 00:30:03.91 +55:50:24.4
119.91275 -6.90630 galactic Cas Second-epoch detections are separated by 7.8" and 5.6 pix
The object was found in VSX17" Gaia DR3 421275925980620032
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.210 G 14.250 G A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:30:03.91 +55:50:24.4: 15.31 +/- 0.24 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:30:03.91 +55:50:24.4: 15.47 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.37 +/- 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 07 09.3433* 00 30 03.91 +55 50 24.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
Gaia DR3 421275925980620032,2461230.8433,13.80,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 421275925980620032 20260709.3433 13.80CV 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 07 09.3433 2461230.8433 13.71 00:05:12.48 +52:08:44.2
115.75840 -10.08106 galactic Cas Second-epoch detections are separated by 5.2" and 5.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 | 00:05:12.48 +52:08:44.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:12.48 +52:08:44.2: 15.78 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:05:12.48 +52:08:44.2: 15.39 +/- 0.23 detection
Forced photometry reference-image weighted average: 15.53 +/- 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 07 09.3433* 00 05 12.48 +52 08 44.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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 13.82 23:57:06.40 +52:12:18.3
114.53401 -9.77854 galactic Cas Second-epoch detections are separated by 8.2" and 6.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:57:06.40 +52:12:18.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:57:06.40 +52:12:18.3: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:57:06.40 +52:12:18.3: 15.95 +/- 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 07 09.3433* 23 57 06.40 +52 12 18.3 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,2461230.8433,13.82,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 20260709.3433 13.82CV 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 07 09.3433 2461230.8433 13.98 23:41:15.33 +54:56:13.8
112.89251 -6.56074 galactic Cas Second-epoch detections are separated by 4.9" and 5.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 | ATO J355.2998+54.9350 | 23:41:11.25 +54:56:17.5 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:41:15.33 +54:56:13.8: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:41:15.33 +54:56:13.8: 15.67 +/- 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 07 09.3433* 23 41 15.33 +54 56 13.8 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
ATO J355.2998+54.9350,2461230.8433,13.98,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
ATO J355.2998+54.9350 20260709.3433 13.98CV 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 07 09.3433 2461230.8433 13.91 00:00:55.88 +53:17:46.2
115.33417 -8.82888 galactic Cas Second-epoch detections are separated by 5.4" and 5.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 | 00:00:55.88 +53:17:46.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:00:55.88 +53:17:46.2: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:00:55.88 +53:17:46.2: 15.88 +/- 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 07 09.3433* 00 00 55.88 +53 17 46.2 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,2461230.8433,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
target 20260709.3433 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 07 09.3433 2461230.8433 13.86 23:33:31.54 +56:43:43.0
112.35795 -4.53509 galactic Cas Second-epoch detections are separated by 8.3" and 5.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:33:31.54 +56:43:43.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:31.54 +56:43:43.0: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:33:31.54 +56:43:43.0: 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 07 09.3433* 23 33 31.54 +56 43 43.0 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,2461230.8433,13.86,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 20260709.3433 13.86CV 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 07 09.3433 2461230.8433 13.92 23:30:29.06 +55:42:25.8
111.64247 -5.38006 galactic Cas Second-epoch detections are separated by 4.0" and 6.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 | 23:30:29.06 +55:42:25.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:30:29.06 +55:42:25.8: 15.18 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:30:29.06 +55:42:25.8: 15.18 +/- 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 07 09.3433* 23 30 29.06 +55 42 25.8 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,2461230.8433,13.92,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 20260709.3433 13.92CV 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 07 09.3433 2461230.8433 14.02 23:57:15.32 +56:43:46.6
115.51692 -5.36006 galactic Cas Second-epoch detections are separated by 6.7" and 5.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 | ATO J359.3120+56.7301 | 23:57:15.32 +56:43:46.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:57:15.32 +56:43:46.6: 14.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:57:15.32 +56:43:46.6: 14.60 +/- 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 07 09.3433* 23 57 15.32 +56 43 46.6 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
ATO J359.3120+56.7301,2461230.8433,14.02,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
ATO J359.3120+56.7301 20260709.3433 14.02CV 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 07 09.3433 2461230.8433 13.92 23:33:30.72 +49:44:37.1
110.24082 -11.19818 galactic And Second-epoch detections are separated by 2.3" and 5.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:33:30.72 +49:44:37.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:30.72 +49:44:37.1: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:33:30.72 +49:44:37.1: 15.67 +/- 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 07 09.3433* 23 33 30.72 +49 44 37.1 13.9 U And 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,2461230.8433,13.92,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 20260709.3433 13.92CV 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 07 09.3433 2461230.8433 14.05 23:41:21.68 +55:49:16.9
113.14687 -5.71335 galactic Cas Second-epoch detections are separated by 4.3" and 5.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 | Gaia DR3 1997541804212061568 | 23:41:16.50 +55:49:20.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:41:21.68 +55:49:16.9: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:41:21.68 +55:49:16.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 07 09.3433* 23 41 21.68 +55 49 16.9 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
Gaia DR3 1997541804212061568,2461230.8433,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
Gaia DR3 1997541804212061568 20260709.3433 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 07 09.3433 2461230.8433 13.91 23:51:18.77 +53:33:31.6
113.97640 -8.26427 galactic Cas Second-epoch detections are separated by 7.4" and 6.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:51:18.77 +53:33:31.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:51:18.77 +53:33:31.6: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:18.77 +53:33:31.6: 15.82 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.82 +/- 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 07 09.3433* 23 51 18.77 +53 33 31.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,2461230.8433,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
target 20260709.3433 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 07 09.3433 2461230.8433 14.04 00:06:22.15 +52:40:48.3
116.03217 -9.58684 galactic Cas Second-epoch detections are separated by 3.6" and 5.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:06:22.15 +52:40:48.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:06:22.15 +52:40:48.3: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:06:22.15 +52:40:48.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 07 09.3433* 00 06 22.15 +52 40 48.3 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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.10 00:16:56.10 +51:18:54.7
117.44844 -11.18883 galactic Cas Second-epoch detections are separated by 7.2" and 6.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:16:56.10 +51:18:54.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:16:56.10 +51:18:54.7: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:16:56.10 +51:18:54.7: 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 07 09.3433* 00 16 56.10 +51 18 54.7 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,2461230.8433,14.10,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 20260709.3433 14.10CV 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 07 09.3433 2461230.8433 14.05 00:04:13.83 +51:49:57.8
115.54986 -10.36111 galactic Cas Second-epoch detections are separated by 2.9" and 6.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 | 00:04:13.83 +51:49:57.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:13.83 +51:49:57.8: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:13.83 +51:49:57.8: 15.60 +/- 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 07 09.3433* 00 04 13.83 +51 49 57.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,2461230.8433,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 20260709.3433 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 07 09.3433 2461230.8433 14.20 23:48:20.02 +54:53:08.0
113.86899 -6.87195 galactic Cas Second-epoch detections are separated by 0.9" and 5.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 | Large-amplitude variable Gaia DR2 1994560963771739264 | 23:48:20.58 +54:53:51.1 (Gaia DR3) | 2021A&A...648A..44M | | Gaia3var=NOT_AVAILABLE (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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:48:20.02 +54:53:08.0: 14.99 +/- 0.20 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:48:20.02 +54:53:08.0: 15.28 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.11 +/- 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 07 09.3433* 23 48 20.02 +54 53 08.0 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
Large-amplitude variable Gaia DR2 1994560963771739264,2461230.8433,14.20,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 1994560963771739264 20260709.3433 14.20CV 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 07 09.3433 2461230.8433 14.20 23:35:32.57 +53:11:46.4
111.58827 -7.99576 galactic Cas Second-epoch detections are separated by 7.4" and 5.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 | ATO J353.8811+53.2033 | 23:35:32.57 +53:11:46.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:35:32.57 +53:11:46.4: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:35:32.57 +53:11:46.4: 15.85 +/- 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 07 09.3433* 23 35 32.57 +53 11 46.4 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
ATO J353.8811+53.2033,2461230.8433,14.20,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
ATO J353.8811+53.2033 20260709.3433 14.20CV 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 07 09.3433 2461230.8433 14.12 00:07:44.94 +50:07:04.6
115.79294 -12.14724 galactic Cas Second-epoch detections are separated by 8.4" and 6.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:07:44.94 +50:07:04.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:07:44.94 +50:07:04.6: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:07:44.94 +50:07:04.6: 15.90 +/- 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 07 09.3433* 00 07 44.94 +50 07 04.6 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,2461230.8433,14.12,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 20260709.3433 14.12CV 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 07 09.3433 2461230.8433 14.21 23:56:55.55 +56:39:43.0
115.45822 -5.41672 galactic Cas Second-epoch detections are separated by 6.9" and 5.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:55.55 +56:39:43.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:56:55.55 +56:39:43.0: 15.08 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:56:55.55 +56:39:43.0: 15.08 +/- 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 07 09.3433* 23 56 55.55 +56 39 43.0 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
target,2461230.8433,14.21,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 20260709.3433 14.21CV 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 07 09.3433 2461230.8433 14.32 23:52:08.08 +55:52:15.5
114.63133 -6.04209 galactic Cas Second-epoch detections are separated by 7.5" and 5.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 | ATO J358.0392+55.8789 | 23:52:10.18 +55:52:51.8 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:52:08.08 +55:52:15.5: 15.76 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:08.08 +55:52:15.5: 15.71 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.74 +/- 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 07 09.3433* 23 52 08.08 +55 52 15.5 14.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
ATO J358.0392+55.8789,2461230.8433,14.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
ATO J358.0392+55.8789 20260709.3433 14.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 07 09.3433 2461230.8433 14.53 23:48:54.10 +52:52:59.3
113.45933 -8.83460 galactic Cas Second-epoch detections are separated by 4.7" and 6.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 | 23:48:54.10 +52:52:59.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:48:54.10 +52:52:59.3: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:48:54.10 +52:52:59.3: 15.92 +/- 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 07 09.3433* 23 48 54.10 +52 52 59.3 14.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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.51 23:34:01.28 +52:35:02.4
111.18408 -8.51294 galactic Cas Second-epoch detections are separated by 3.4" and 6.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:34:01.28 +52:35:02.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:34:01.28 +52:35:02.4: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:34:01.28 +52:35:02.4: 15.84 +/- 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 07 09.3433* 23 34 01.28 +52 35 02.4 14.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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.51 23:32:25.48 +52:35:05.5
110.95052 -8.43908 galactic Cas Second-epoch detections are separated by 3.2" and 5.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 | 23:32:25.48 +52:35:05.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:32:25.48 +52:35:05.5: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:32:25.48 +52:35:05.5: 15.73 +/- 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 07 09.3433* 23 32 25.48 +52 35 05.5 14.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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.58 23:51:52.62 +53:48:17.4
114.11618 -8.04432 galactic Cas Second-epoch detections are separated by 8.5" and 6.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 | Gaia DR3 1993474233966468096 | 23:51:47.69 +53:48:09.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:51:52.62 +53:48:17.4: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:52.62 +53:48:17.4: 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 07 09.3433* 23 51 52.62 +53 48 17.4 14.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 1993474233966468096,2461230.8433,14.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 1993474233966468096 20260709.3433 14.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 07 09.3433 2461230.8433 14.62 23:42:44.51 +53:52:54.1
112.81786 -7.63559 galactic Cas Second-epoch detections are separated by 4.8" and 5.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:42:44.51 +53:52:54.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:42:44.51 +53:52:54.1: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:42:44.51 +53:52:54.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 07 09.3433* 23 42 44.51 +53 52 54.1 14.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,2461230.8433,14.62,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 20260709.3433 14.62CV 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 07 09.3433 2461230.8433 14.59 00:14:38.20 +54:13:58.9
117.51343 -8.25109 galactic Cas Second-epoch detections are separated by 8.8" and 6.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:14:38.20 +54:13:58.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:14:38.20 +54:13:58.9: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:38.20 +54:13:58.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 07 09.3433* 00 14 38.20 +54 13 58.9 14.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,2461230.8433,14.59,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 20260709.3433 14.59CV 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 07 09.3433 2461230.8433 14.73 00:02:24.25 +54:59:50.0
115.88053 -7.20180 galactic Cas Second-epoch detections are separated by 4.6" and 5.9 pix
The object was found in VSX20" Gaia DR3 420461119146211968
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.780 G 14.820 G A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:24.25 +54:59:50.0: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:24.25 +54:59:50.0: 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 07 09.3433* 00 02 24.25 +54 59 50.0 14.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 420461119146211968,2461230.8433,14.73,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 420461119146211968 20260709.3433 14.73CV 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 07 09.3433 2461230.8433 14.60 00:02:03.49 +55:39:54.1
115.96035 -6.53689 galactic Cas Second-epoch detections are separated by 8.3" and 5.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:02:03.49 +55:39:54.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:03.49 +55:39:54.1: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:03.49 +55:39:54.1: 15.84 +/- 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 07 09.3433* 00 02 03.49 +55 39 54.1 14.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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 14.60 23:46:55.28 +58:01:13.4
114.45267 -3.78528 galactic Cas Second-epoch detections are separated by 6.4" and 6.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:46:55.28 +58:01:13.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:46:55.28 +58:01:13.4: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:46:55.28 +58:01:13.4: 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 07 09.3433* 23 46 55.28 +58 01 13.4 14.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,2461230.8433,14.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 20260709.3433 14.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 07 09.3433 2461230.8433 11.41 00:20:45.27 +50:11:53.4
117.91334 -12.37436 galactic Cas Second-epoch detections are separated by 6.1" and 6.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:20:45.27 +50:11:53.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:45.27 +50:11:53.4: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:45.27 +50:11:53.4: 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 07 09.3433* 00 20 45.27 +50 11 53.4 11.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,2461230.8433,11.41,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 20260709.3433 11.41CV 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 07 09.3433 2461230.8433 13.39 00:26:00.35 +53:55:15.5
119.14846 -8.76385 galactic Cas Second-epoch detections are separated by 6.3" and 6.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:26:00.35 +53:55:15.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:26:00.35 +53:55:15.5: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:26:00.35 +53:55:15.5: 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 07 09.3433* 00 26 00.35 +53 55 15.5 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,2461230.8433,13.39,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 20260709.3433 13.39CV 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 07 09.3433 2461230.8433 12.82 23:59:54.83 +56:58:33.0
115.92469 -5.19328 galactic Cas Second-epoch detections are separated by 6.6" and 5.8 pix
The object was found in VSX14" V0533 Cas
Type: M
# Max. Min./Amp. JD0 Period
15.361 g Y 2.943 g 2458396.91440 296.168262100000 C(N)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:59:54.83 +56:58:33.0: 14.65 +/- 0.11 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:59:54.83 +56:58:33.0: 14.50 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.57 +/- 0.08
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 07 09.3433* 23 59 54.83 +56 58 33.0 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
V0533 Cas,2461230.8433,12.82,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
V0533 Cas 20260709.3433 12.82CV 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 07 09.3433 2461230.8433 10.71 23:38:16.57 +56:01:50.6
112.78726 -5.39327 galactic Cas Second-epoch detections are separated by 1.4" and 5.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:38:16.57 +56:01:50.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:38:16.57 +56:01:50.6: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:38:16.57 +56:01:50.6: 15.76 +/- 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 07 09.3433* 23 38 16.57 +56 01 50.6 10.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,2461230.8433,10.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 20260709.3433 10.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 07 09.3433 2461230.8433 11.47 23:50:45.88 +53:34:28.0
113.90016 -8.22997 galactic Cas Second-epoch detections are separated by 6.2" and 5.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:50:45.88 +53:34:28.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:50:45.88 +53:34:28.0: 15.60 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:50:45.88 +53:34:28.0: 15.64 +/- 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 07 09.3433* 23 50 45.88 +53 34 28.0 11.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,2461230.8433,11.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 20260709.3433 11.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 07 09.3433 2461230.8433 7.75 23:58:25.46 +51:26:27.8
114.57339 -10.56828 galactic Cas Second-epoch detections are separated by 5.7" and 6.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:58:25.46 +51:26:27.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:25.46 +51:26:27.8: 15.60 +/- 0.34 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:25.46 +51:26:27.8: 15.53 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.56 +/- 0.24
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 07 09.3433* 23 58 25.46 +51 26 27.8 7.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,2461230.8433,7.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 20260709.3433 7.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 07 09.3433 2461230.8433 7.96 00:23:10.19 +55:47:39.9
118.93737 -6.85793 galactic Cas Second-epoch detections are separated by 8.3" and 6.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 | T Cas | 00:23:14.31 +55:47:33.1 (Gaia DR3) | M (local) | 443.500000000000 (local) | Gaia3var=VARIABLE SpType: M8e 1923ApJ....58..215M T Cas
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:23:10.19 +55:47:39.9: 10.25 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:10.19 +55:47:39.9: 10.27 +/- 0.01 detection
Forced photometry reference-image weighted average: 10.26 +/- 0.01
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 07 09.3433* 00 23 10.19 +55 47 39.9 8.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
T Cas,2461230.8433,7.96,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
T Cas 20260709.3433 7.96CV 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: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
First image: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Last image: 2461230.84357469 09.07.2026 08:14:34.853 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 16
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.78
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: 14 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): 24036
Objects passed selection criteria: 23942
Measurements per detected object (mean, median, min, max): 2.9 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.9 2.0 2 4
Average stars detected per image: 18065.8
Average stars matched: 16592.8 (91.8464 %)
Memory usage VmPeak: 126844 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Jul 8 15:05:08 CDT 2026
VaST build number 1.0rc89-141-gc31ee76a
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-07-08)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Jul 9 05:02:19 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: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
First image: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Last image: 2461230.84357469 09.07.2026 08:14:34.853 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 369
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.39
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: 138 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): 193262
Objects passed selection criteria: 192701
Measurements per detected object (mean, median, min, max): 2.9 3.0 2 4
Measurements per selected object (mean, median, min, max): 2.9 3.0 2 4
Average stars detected per image: 150478
Average stars matched: 136699 (90.8436 %)
Memory usage VmPeak: 2116320 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Jul 8 15:05:08 CDT 2026
VaST build number 1.0rc89-141-gc31ee76a
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-07-08)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Thu Jul 9 05:37:03 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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.cat to cache
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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: 2461230.84306233
Re-using ../asassn_transients_list.txt
'../asassn_transients_list.txt' -> 'asassn_transients_list.txt'
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
wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits exists and is non-empty
Saving wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits'
wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits exists and is non-empty
Saving wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits'
wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits'
wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits (1st reference image)
verification OK: wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Image size: 941.8'x627.0' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 23:59:52.581 +53:59:29.78 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/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-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
Image size: 926.7'x616.2' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:58.434 +54:00:51.21 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:52.581 +53:59:29.78
Second-epoch image center 23:59:58.434 +54:00:51.21
Angular distance between the image centers 0.0268 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
Image size: 926.7'x616.3' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 00:00:01.067 +54:01:17.35 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:52.581 +53:59:29.78
Second-epoch image center 00:00:01.067 +54:01:17.35
Angular distance between the image centers 0.0364 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 23:59:58.434 +54:00:51.21
Second-epoch second image center 00:00:01.067 +54:01:17.35
Angular distance between the image centers 0.00971 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for a parallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits &> /tmp/tmp.ff5hq5hkLu
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits &> /tmp/tmp.bLMDaC7E5c
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits &> /tmp/tmp.9XHzQOApNA
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits &> /tmp/tmp.BDf87du3Lz
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
wait (drain background util/solve_plate_with_UCAC5 jobs before Tycho-2 calibration -- avoids wcs_.fits write race)
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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
Found non-empty wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
The reference image (wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits) and catalog (wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat) found
'wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat' -> 'wcsmag.cat'
Read 29225 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0002 to 359.9995 deg, Dec +47.7049 to +59.3705 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.0002 to 359.9995 deg, Dec 47.7049 to 59.3705 deg
Loaded 162590 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): 14935 out of 16561 total matches.
Matched with Tycho-2 16561 out of 29225 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.842700
a=0.000000 b=1.000000 c=22.842700
From vast_summary.log: estimated ref. image limiting mag.: -7.78
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.06
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.06
Lightcurve magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 29225 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0002 to 359.9995 deg, Dec +47.7049 to +59.3705 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.0002 to 359.9995 deg, Dec 47.7049 to 59.3705 deg
Loaded 162590 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): 14935 out of 16561 total matches.
Matched with Tycho-2 16561 out of 29225 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits:
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits (aperture=6.0)
Read 29065 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0009 to 359.9998 deg, Dec +47.6373 to +59.3623 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.0009 to 359.9998 deg, Dec 47.6373 to 59.3623 deg
Loaded 163448 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): 14807 out of 16429 total matches.
Matched with Tycho-2 16429 out of 29065 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits:
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits (aperture=6.0)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 15 candidate transients before the final filtering. (Hard limit: 10000)
Median FWHM seeing for isolated stars:
2.1 pix Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
2.1 pix Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
2.3 pix fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
2.3 pix fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
2.1 pix wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
2.1 pix wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
Limiting magnitude estimates:
15.1 mag. Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
15.1 mag. Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
14.5 mag. fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
14.5 mag. fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
All-image limiting magnitude estimate: 14.5 (SNR ) 11.6 (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.5 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.ff5hq5hkLu (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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits' -> 'wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3209, bad_region=7497, passed=29225
Got 29225 stars (including 19224 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
util/solve_plate_with_UCAC5 got 29225 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 345.4494 through 0 to 15.3164, gap 15.3164 to 345.4494
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 968 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.56"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 22315 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
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 345.4506 through 0 to 15.3182, gap 15.3182 to 345.4506
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 22314 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 22315 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.46"
Excluding outliers - 973 stars left (next iteration limit 1070)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits N_match=973 sigma_overall_arcsec=0.484 sigma_q1_arcsec=0.551 sigma_q2_arcsec=0.430 sigma_q3_arcsec=0.487 sigma_q4_arcsec=0.426 n_q1=280 n_q2=198 n_q3=285 n_q4=210 worst_quadrant_to_overall_ratio=1.137
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits -region wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.bLMDaC7E5c (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-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.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-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.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-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits' -> 'wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3195, bad_region=7496, passed=29065
Got 29065 stars (including 19086 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat
util/solve_plate_with_UCAC5 got 29065 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 345.4479 through 0 to 15.3165, gap 15.3165 to 345.4479
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.6 to 59.4)
Done reading UCAC5 zone files...
Matched 974 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 964 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.55"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 22203 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.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 345.4487 through 0 to 15.3181, gap 15.3181 to 345.4487
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.6 to 59.4)
Done reading UCAC5 zone files...
Matched 974 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 22202 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 22202 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.48"
Excluding outliers - 972 stars left (next iteration limit 1069)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits N_match=972 sigma_overall_arcsec=0.506 sigma_q1_arcsec=0.539 sigma_q2_arcsec=0.430 sigma_q3_arcsec=0.560 sigma_q4_arcsec=0.425 n_q1=282 n_q2=199 n_q3=280 n_q4=211 worst_quadrant_to_overall_ratio=1.107
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits -region wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.9XHzQOApNA (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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1412, bad_region=4379, passed=19082
Got 19082 stars (including 13515 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat
util/solve_plate_with_UCAC5 got 19082 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 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 345.0823 through 0 to 14.8806, gap 14.8806 to 345.0823
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 322 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 238 matched stars entering correct_measured_positions(), 172 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.41"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 229 matched stars entering correct_measured_positions(), 4230 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.94"
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 345.0703 through 0 to 14.9054, gap 14.9054 to 345.0703
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 389 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 328 matched stars entering correct_measured_positions(), 4283 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.88"
Accuracy estimation diagnostic: 318 matched stars entering correct_measured_positions(), 5461 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.39"
Excluding outliers - 318 stars left (next iteration limit 251)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits N_match=318 sigma_overall_arcsec=9.718 sigma_q1_arcsec=26.403 sigma_q2_arcsec=24.845 sigma_q3_arcsec=7.006 sigma_q4_arcsec=9.725 n_q1=34 n_q2=22 n_q3=114 n_q4=148 worst_quadrant_to_overall_ratio=2.717
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits -region wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.BDf87du3Lz (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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1441, bad_region=4361, passed=19021
Got 19021 stars (including 13456 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat
util/solve_plate_with_UCAC5 got 19021 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 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 345.0818 through 0 to 14.8804, gap 14.8804 to 345.0818
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 324 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 242 matched stars entering correct_measured_positions(), 170 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.34"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 233 matched stars entering correct_measured_positions(), 4152 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.81"
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 345.0703 through 0 to 14.9047, gap 14.9047 to 345.0703
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 394 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 331 matched stars entering correct_measured_positions(), 4202 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.75"
Accuracy estimation diagnostic: 325 matched stars entering correct_measured_positions(), 5324 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.28"
Excluding outliers - 325 stars left (next iteration limit 256)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits N_match=325 sigma_overall_arcsec=9.557 sigma_q1_arcsec=27.720 sigma_q2_arcsec=26.031 sigma_q3_arcsec=7.112 sigma_q4_arcsec=9.520 n_q1=32 n_q2=24 n_q3=118 n_q4=151 worst_quadrant_to_overall_ratio=2.901
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits -region wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits sigma_overall=0.484 worst_q_ratio=1.137
ref2=Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits sigma_overall=0.506 worst_q_ratio=1.107
new1=fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits sigma_overall=9.718 worst_q_ratio=2.717
new2=fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits sigma_overall=9.557 worst_q_ratio=2.901
reference average sigma_overall=0.495 worst_q_ratio=1.122
warn-on-ratio threshold: 2.0x reference
###################################
WCS_QUALITY_RETRY: 1st new image (fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits) flagged: sigma=9.718 (ref avg 0.495), ratio=2.717 (ref avg 1.122), 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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/lib/make_outxyls_for_astrometric_calibration found 18315 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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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: "out477709.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out477709.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 28.4354 (2.23523e+12), 7 match, 0 conflict, 16 distractors, 24 index.
RA,Dec = (359.991,54.0126), pixel scale 5.93111 arcsec/pix.
Hit/miss: Hit/miss: ---++---+------++-+---+(best)-------+---------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out477709.solved to indicate this.
Field: out477709.xyls
Field center: (RA,Dec) = (359.992092, 54.013401) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:58.102, +54:00:48.245).
Field size: 15.6051 x 10.4324 degrees
Field rotation angle: up is 3.77806 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits' -> 'fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 9 05:15 fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
-rw-r--r-- 1 apache apache 8.5K Jul 9 05:15 out477709.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits (fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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: "out477709.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out477709.axy"...
Only searching for solutions within 15.445 degrees of RA,Dec (359.993,54.0142)
log-odds ratio 28.4354 (2.23523e+12), 7 match, 0 conflict, 16 distractors, 24 index.
RA,Dec = (359.991,54.0126), pixel scale 5.93111 arcsec/pix.
Hit/miss: Hit/miss: ---++---+------++-+---+(best)-------+---------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out477709.solved to indicate this.
Field: out477709.xyls
Field center: (RA,Dec) = (359.992092, 54.013401) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:58.102, +54:00:48.245).
Field size: 15.6051 x 10.4324 degrees
Field rotation angle: up is 3.77806 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 9 05:15 fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
-rw-r--r-- 1 apache apache 8.5K Jul 9 05:15 out477709.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.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-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 95931 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.axy"...
Verifying WCS using indices with quads of size [63.1466, 946.606] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 8.96883
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 7.01761
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 4.94244
Verifying WCS using indices with quads of size [63.1466, 946.606] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 8.96883
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 7.01761
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 4.94244
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
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-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
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).
Total CPU time limit reached!
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
Image size: 926.7'x616.2' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:58.434 +54:00:51.21 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 19082 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/correct_sextractor_wcs_catalog_usingxy2sky909844.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1412, bad_region=4379, passed=19082
Got 19082 stars (including 13515 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat
util/solve_plate_with_UCAC5 got 19082 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 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 345.0823 through 0 to 14.8806, gap 14.8806 to 345.0823
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 322 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 238 matched stars entering correct_measured_positions(), 172 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.41"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 229 matched stars entering correct_measured_positions(), 4230 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.94"
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 345.0703 through 0 to 14.9054, gap 14.9054 to 345.0703
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 389 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 328 matched stars entering correct_measured_positions(), 4283 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.88"
Accuracy estimation diagnostic: 318 matched stars entering correct_measured_positions(), 5461 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.39"
Excluding outliers - 318 stars left (next iteration limit 251)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits N_match=318 sigma_overall_arcsec=9.718 sigma_q1_arcsec=26.403 sigma_q2_arcsec=24.845 sigma_q3_arcsec=7.006 sigma_q4_arcsec=9.725 n_q1=34 n_q2=22 n_q3=114 n_q4=148 worst_quadrant_to_overall_ratio=2.717
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits -region wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.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-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits): sigma 9.718->9.718, ratio 2.717->2.717; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits) flagged: sigma=9.557 (ref avg 0.495), ratio=2.901 (ref avg 1.122), 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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/lib/make_outxyls_for_astrometric_calibration found 18278 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-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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: "out921218.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out921218.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 29.035 (4.07132e+12), 7 match, 0 conflict, 16 distractors, 24 index.
RA,Dec = (0.00168463,54.0198), pixel scale 5.93121 arcsec/pix.
Hit/miss: Hit/miss: ---++-+--------++-+---+(best)-----------+-----------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out921218.solved to indicate this.
Field: out921218.xyls
Field center: (RA,Dec) = (0.003066, 54.020663) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:00.736, +54:01:14.385).
Field size: 15.6057 x 10.4329 degrees
Field rotation angle: up is 3.77254 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits' -> 'fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 9 05:22 fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
-rw-r--r-- 1 apache apache 8.5K Jul 9 05:22 out921218.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits (fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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: "out921218.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out921218.axy"...
Only searching for solutions within 15.445 degrees of RA,Dec (0.00444583,54.0215)
log-odds ratio 29.035 (4.07132e+12), 7 match, 0 conflict, 16 distractors, 24 index.
RA,Dec = (0.00168463,54.0198), pixel scale 5.93121 arcsec/pix.
Hit/miss: Hit/miss: ---++-+--------++-+---+(best)-----------+-----------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out921218.solved to indicate this.
Field: out921218.xyls
Field center: (RA,Dec) = (0.003066, 54.020663) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:00.736, +54:01:14.385).
Field size: 15.6057 x 10.4329 degrees
Field rotation angle: up is 3.77254 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 9 05:22 fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
-rw-r--r-- 1 apache apache 8.5K Jul 9 05:22 out921218.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.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-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 96531 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.axy"...
Verifying WCS using indices with quads of size [63.1477, 946.622] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS using indices with quads of size [63.1477, 946.622] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
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-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
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-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
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).
Total CPU time limit reached!
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Field: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
Image size: 926.7'x616.3' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 00:00:01.067 +54:01:17.35 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 19021 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/correct_sextractor_wcs_catalog_usingxy2sky1885449.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1441, bad_region=4361, passed=19021
Got 19021 stars (including 13456 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat
util/solve_plate_with_UCAC5 got 19021 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 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 345.0818 through 0 to 14.8804, gap 14.8804 to 345.0818
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 324 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 242 matched stars entering correct_measured_positions(), 170 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.34"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 233 matched stars entering correct_measured_positions(), 4152 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.81"
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 345.0703 through 0 to 14.9047, gap 14.9047 to 345.0703
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 394 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 331 matched stars entering correct_measured_positions(), 4202 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.75"
Accuracy estimation diagnostic: 325 matched stars entering correct_measured_positions(), 5324 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.28"
Excluding outliers - 325 stars left (next iteration limit 256)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits N_match=325 sigma_overall_arcsec=9.557 sigma_q1_arcsec=27.720 sigma_q2_arcsec=26.031 sigma_q3_arcsec=7.112 sigma_q4_arcsec=9.520 n_q1=32 n_q2=24 n_q3=118 n_q4=151 worst_quadrant_to_overall_ratio=2.901
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits -region wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.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-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits): sigma 9.557->9.557, ratio 2.901->2.901; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=9.718 -- 19.63x the reference average (0.495); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=9.557 -- 19.31x the reference average (0.495); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=2.717 -- 2.42x the reference average (1.122); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=2.901 -- 2.59x the reference average (1.122); plate solution may be of low accuracy
Astrometric residual vector field (catalog-matched stars):
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006_astrometric_residuals.png (973 matched stars from wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 0.43 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007_astrometric_residuals.png (972 matched stars from wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 0.46 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118_astrometric_residuals.png (318 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.17 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119_astrometric_residuals.png (325 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.09 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-13-50_20.00sec_-0.00C_LIGHT_0118.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-07-09_CI_Cas-04-Q2b1x1_031552_TTUQ2b1x1_3974526_icn2M4Df/wcs_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119.fits'
Preparing the HTML report for the field Cas-04-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:32:12.26 +52:55:03.9: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:19.07 +54:08:11.0: 14.83 +/- 0.15 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:11:10.62 +55:02:53.9: 11.95 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:44.11 +50:11:43.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:13:33.15 +53:52:03.8: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:38:16.61 +56:01:35.0: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:27.04 +51:26:22.6: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:11:08.37 +52:33:49.5: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:44.11 +50:11:43.0: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:32:12.26 +52:55:03.9: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:11:10.62 +55:02:53.9: 11.89 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:19.07 +54:08:11.0: 15.07 +/- 0.19 detection
Forced photometry reference-image weighted average: 14.93 +/- 0.12
Forced photometry reference-image weighted average: 11.92 +/- 0.01
Forced photometry filter KEPT candidate at 00:02:19.07 +54:08:11.0: ref_mag=14.93 +/- 0.12 new_mean_mag=11.6996 delta=3.23 (need > 0.90)
Forced photometry filter REJECTED candidate at 00:11:10.62 +55:02:53.9: ref_mag=11.92 +/- 0.01 new_mean_mag=11.8497 delta=0.07 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:13:33.15 +53:52:03.8: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:38:16.61 +56:01:35.0: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:27.04 +51:26:22.6: 15.47 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.47 +/- 0.34
Forced photometry filter KEPT candidate at 23:58:27.04 +51:26:22.6: ref_mag=15.47 +/- 0.34 new_mean_mag=7.3371 delta=8.14 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:11:08.37 +52:33:49.5: 15.61 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.61 +/- 0.33
Forced photometry filter KEPT candidate at 00:11:08.37 +52:33:49.5: ref_mag=15.61 +/- 0.33 new_mean_mag=11.2258 delta=4.39 (need > 0.90)
Adding exclusion_list_local.txt__out09534.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out18981.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21888.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31468.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33291.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34615.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35385.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 18s
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: 5s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31468_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 31468_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32039_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 32039_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:04:40.75 +55:32:13.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32303_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 32303_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:44:31.70 +56:34:50.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32478_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 32478_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:55:49.63 +53:44:37.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33291_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 33291_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33680_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 33680_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:50:44.46 +53:34:47.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34271_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 34271_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:06:02.41 +55:11:57.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34615_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 34615_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34759_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 34759_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35076_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 35076_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35385_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 35385_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18981_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 18981_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 08367_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 08367_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243679_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243679_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (38.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243686_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243686_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243692_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243692_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243702_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243702_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243720_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243720_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243722_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243722_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243725_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243725_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243726_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243726_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243730_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243730_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243737_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243737_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243739_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243739_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243742_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243742_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243747_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243747_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243750_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243750_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243754_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243754_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243757_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243757_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243765_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243765_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (29.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243767_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243767_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243769_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243769_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243770_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243770_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243772_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243772_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (32.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243783_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243783_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243785_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243785_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243787_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243787_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243788_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243788_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243792_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243792_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243794_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243794_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243799_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243799_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243800_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243800_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243802_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243802_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243805_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243805_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (25.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243810_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243810_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243812_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243812_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243813_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243813_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243814_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243814_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243815_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243815_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243819_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243819_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243821_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243821_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243822_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243822_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:58:35.12 +54:07:53.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243826_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243826_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243829_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243829_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243830_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243830_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243835_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243835_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243836_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243836_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243839_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243839_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243840_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243840_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243841_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243841_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243843_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243843_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243846_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243846_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243849_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243849_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243851_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243851_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243852_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243852_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243855_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243855_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243857_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243857_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243861_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243861_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243862_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243862_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243865_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243865_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243866_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243866_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243867_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243867_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243870_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243870_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243873_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243873_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243874_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243874_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243875_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243875_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243876_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243876_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243878_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243878_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (28.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243879_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243879_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243880_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243880_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243882_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243882_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243885_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243885_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243887_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243887_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243888_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243888_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243889_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243889_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243890_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243890_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243892_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243892_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243897_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243897_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243899_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243899_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243901_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243901_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243904_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243904_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243906_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243906_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243911_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243911_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243912_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243912_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243914_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243914_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243915_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243915_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243918_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243918_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243920_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243920_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243922_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243922_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243929_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243929_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243930_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243930_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243931_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243931_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243932_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243932_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243933_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243933_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243934_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243934_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (36.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243935_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243935_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243937_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243937_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243938_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243938_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243939_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243939_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243941_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243941_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243943_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243943_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243944_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243944_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243946_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243946_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243947_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243947_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243949_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243949_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243950_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243950_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243951_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243951_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243954_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243954_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243957_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 243957_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243959_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243959_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243960_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243960_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (27.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243961_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 243961_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247041_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 247041_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:06:03.25 +55:11:48.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247625_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 247625_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248027_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 248027_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248401_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 248401_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249337_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 249337_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249577_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 249577_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250433_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 250433_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250664_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 250664_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250706_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 250706_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251266_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 251266_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251771_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 251771_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251859_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 251859_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252088_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 252088_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252703_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 252703_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253101_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 253101_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253233_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 253233_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254328_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 254328_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254561_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 254561_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254795_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 254795_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255154_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 255154_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255388_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 255388_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255514_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 255514_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255656_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 255656_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255755_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 255755_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255788_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 255788_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256199_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 256199_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256585_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 256585_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256586_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 256586_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:47:30.03 +52:37:05.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256898_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 256898_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:47:34.98 +52:37:39.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256985_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 256985_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257231_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257231_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257248_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 257248_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257455_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257455_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257620_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 257620_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257648_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257648_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257688_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257688_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257751_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257751_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257824_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257824_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257912_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 257912_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257955_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 257955_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258008_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 258008_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258026_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258026_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258189_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258189_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (26.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258334_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258334_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258507_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258507_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258577_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258577_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258628_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258628_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258779_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 258779_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258783_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258783_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258874_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 258874_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259041_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259041_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259392_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259392_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259443_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259443_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259508_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259508_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259582_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 259582_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259633_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259633_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259680_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259680_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259822_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259822_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259835_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259835_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259887_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 259887_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259907_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 259907_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260026_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260026_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260166_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260166_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (27.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260273_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260273_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260350_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260350_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260447_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260447_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (26.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260598_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260598_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260763_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260763_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260942_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260942_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (31.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260978_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 260978_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261342_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261342_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261404_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261404_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261459_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261459_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261545_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261545_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261595_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261595_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261606_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261606_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261615_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261615_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:59:15.24 +53:35:49.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261625_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 261625_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261641_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261641_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261828_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261828_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261840_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 261840_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261946_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 261946_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261967_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 261967_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262177_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 262177_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (35.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262404_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 262404_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262596_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 262596_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262667_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 262667_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262706_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 262706_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262713_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 262713_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263139_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 263139_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263140_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263140_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (29.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263425_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263425_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263495_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 263495_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263561_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263561_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263578_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263578_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263614_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263614_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263640_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263640_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263725_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263725_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263775_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 263775_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263818_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 263818_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263828_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263828_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263857_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263857_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263929_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263929_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263999_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 263999_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264070_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264070_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264183_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264183_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264190_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264190_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264339_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264339_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264345_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264345_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264404_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 264404_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264448_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264448_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (33.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264522_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264522_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264584_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 264584_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264638_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264638_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (24.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264694_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264694_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264854_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264854_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:24:19.99 +53:13:42.8 in the exclusion list exclusion_list_tycho2.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264858_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264858_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264926_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 264926_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265012_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 265012_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265051_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 265051_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265126_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265126_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265249_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265249_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265322_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265322_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265517_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 265517_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265587_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265587_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265680_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265680_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265753_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265753_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265771_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 265771_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265863_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 265863_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265893_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265893_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265967_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 265967_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265969_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265969_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265979_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 265979_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266007_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266007_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266118_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 266118_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266317_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266317_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266493_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266493_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266686_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266686_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266719_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266719_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266729_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266729_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266784_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 266784_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266922_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 266922_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267052_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 267052_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267134_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 267134_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267322_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 267322_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267615_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 267615_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267712_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 267712_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267812_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 267812_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268011_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268011_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268288_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268288_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:01:58.40 +54:26:14.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268319_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 268319_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268324_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268324_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268338_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268338_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:27:30.68 +57:10:36.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268412_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 268412_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268419_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268419_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268484_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 268484_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268571_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 268571_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268661_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 268661_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268720_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268720_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268757_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 268757_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269084_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 269084_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269348_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 269348_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269389_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 269389_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269736_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 269736_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269895_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 269895_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269932_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 269932_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270324_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 270324_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270407_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 270407_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270572_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 270572_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270711_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 270711_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270910_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 270910_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271020_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 271020_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271027_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 271027_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271032_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 271032_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271243_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 271243_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271433_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 271433_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271531_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 271531_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271552_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 271552_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272048_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 272048_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272092_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 272092_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272302_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 272302_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272959_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 272959_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273044_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 273044_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273489_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 273489_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273511_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 273511_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273957_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 273957_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274421_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 274421_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274943_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 274943_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275109_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 275109_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275134_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 275134_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275387_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 275387_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275601_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 275601_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275707_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 275707_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275898_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 275898_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275972_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 275972_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276499_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 276499_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276934_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 276934_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277099_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 277099_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277229_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 277229_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277338_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 277338_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277438_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 277438_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277461_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 277461_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277487_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 277487_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277492_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 277492_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277533_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 277533_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277687_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 277687_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277781_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 277781_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278120_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 278120_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58579_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 58579_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:44:31.87 +56:34:45.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179137_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 179137_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 79234_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 79234_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:04:41.26 +55:32:14.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 146843_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 146843_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 00:11:08.39 +52:33:57.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 108520_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 108520_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125040_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
The candidate 125040_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119 did not pass the final checks
**** FOUND 23:55:51.13 +53:44:31.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 46239_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 46239_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71796_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 71796_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 130430_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 130430_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174810_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 174810_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69970_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
Preparing report for the candidate 69970_fd_Cas-04-Q2b1x1_2026-07-09_03-14-34_20.00sec_-0.00C_LIGHT_0119
make_report_in_HTML.sh Phase 2 (HTML assembly): 9s
make_report_in_HTML.sh TOTAL: 290s
Prepared the HTML report for the field Cas-04-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
23:38:16.61 +56:01:35.0
00:11:08.37 +52:33:49.5
23:58:27.04 +51:26:22.6
23:32:12.26 +52:55:03.9
00:20:44.11 +50:11:43.0
00:02:19.07 +54:08:11.0
00:13:33.15 +53:52:03.8
00:26:00.35 +53:55:15.5
23:50:45.88 +53:34:28.0
23:58:25.46 +51:26:27.8
00:20:45.27 +50:11:53.4
23:44:45.09 +58:01:07.3
23:46:04.57 +54:20:47.4
23:47:18.24 +54:24:27.4
00:05:48.00 +55:40:11.5
23:32:49.97 +51:33:20.2
00:20:45.15 +54:18:08.9
23:50:46.61 +52:51:41.2
23:48:32.96 +55:00:38.1
23:37:48.55 +55:18:46.0
00:03:44.46 +50:50:07.8
23:52:26.35 +53:22:23.6
00:15:30.46 +52:00:00.6
23:50:42.90 +52:47:03.3
00:23:06.17 +56:38:59.2
23:48:25.43 +53:27:14.5
23:45:17.16 +56:33:48.8
23:40:15.18 +55:54:40.3
23:51:14.96 +52:36:43.8
23:34:44.95 +50:14:51.3
00:04:32.90 +52:54:20.2
00:18:03.21 +50:32:31.8
23:35:22.67 +56:30:55.7
00:22:04.53 +54:21:13.0
23:51:37.10 +52:54:02.5
23:55:25.10 +51:47:33.2
23:29:43.59 +54:42:05.1
23:36:42.47 +50:50:13.4
23:45:29.28 +53:49:18.7
23:33:43.42 +56:50:45.6
23:29:17.32 +55:18:42.5
23:43:00.44 +52:41:51.6
23:43:36.10 +53:16:07.0
00:14:53.89 +53:15:42.4
23:33:26.69 +52:54:43.2
23:32:10.90 +52:54:26.7
00:31:48.37 +56:53:27.1
00:22:44.23 +52:22:58.0
00:23:22.97 +55:49:13.9
00:24:38.31 +56:58:50.9
00:27:10.97 +50:01:18.1
23:53:29.10 +53:32:26.0
00:13:38.09 +52:03:06.5
00:24:51.20 +53:02:33.5
23:53:49.14 +53:08:16.8
00:02:56.34 +56:52:15.6
00:20:04.73 +50:09:06.4
00:07:37.86 +53:34:09.5
00:12:56.74 +50:00:20.0
23:41:52.68 +53:03:28.6
23:58:59.53 +53:17:26.1
00:26:27.14 +51:06:31.0
00:29:32.20 +53:56:40.1
00:31:11.75 +56:46:20.1
00:25:44.55 +54:58:05.4
00:20:03.71 +51:55:20.5
00:22:23.70 +53:06:02.8
23:54:23.41 +55:37:41.3
00:22:36.64 +51:54:06.2
00:25:02.62 +52:51:24.1
00:14:16.81 +56:52:39.6
00:27:16.87 +54:05:35.9
00:11:48.29 +52:52:36.7
00:22:18.53 +54:16:24.8
23:35:46.63 +49:52:31.1
23:43:03.88 +54:27:17.2
00:18:10.07 +54:09:39.8
00:19:46.94 +51:04:47.8
00:30:03.91 +55:50:24.4
00:05:12.48 +52:08:44.2
23:57:06.40 +52:12:18.3
23:41:15.33 +54:56:13.8
00:00:55.88 +53:17:46.2
23:33:31.54 +56:43:43.0
23:30:29.06 +55:42:25.8
23:57:15.32 +56:43:46.6
23:33:30.72 +49:44:37.1
23:41:21.68 +55:49:16.9
23:51:18.77 +53:33:31.6
00:06:22.15 +52:40:48.3
00:16:56.10 +51:18:54.7
00:04:13.83 +51:49:57.8
23:48:20.02 +54:53:08.0
23:35:32.57 +53:11:46.4
00:07:44.94 +50:07:04.6
23:56:55.55 +56:39:43.0
23:52:08.08 +55:52:15.5
23:48:54.10 +52:52:59.3
23:34:01.28 +52:35:02.4
23:32:25.48 +52:35:05.5
23:51:52.62 +53:48:17.4
23:42:44.51 +53:52:54.1
00:14:38.20 +54:13:58.9
00:02:24.25 +54:59:50.0
00:02:03.49 +55:39:54.1
23:46:55.28 +58:01:13.4
23:59:54.83 +56:58:33.0
00:23:10.19 +55:47:39.9
23:38:16.57 +56:01:50.6
########### Completed Cas-04-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:32:12.26 +52:55:03.9
00:20:44.11 +50:11:43.0
00:02:19.07 +54:08:11.0
00:13:33.15 +53:52:03.8
00:11:08.37 +52:33:49.5
23:38:16.61 +56:01:35.0
23:58:27.04 +51:26:22.6
23:44:45.09 +58:01:07.3
23:46:04.57 +54:20:47.4
23:47:18.24 +54:24:27.4
00:05:48.00 +55:40:11.5
23:32:49.97 +51:33:20.2
00:20:45.15 +54:18:08.9
23:50:46.61 +52:51:41.2
23:48:32.96 +55:00:38.1
23:37:48.55 +55:18:46.0
00:03:44.46 +50:50:07.8
23:52:26.35 +53:22:23.6
00:15:30.46 +52:00:00.6
23:50:42.90 +52:47:03.3
00:23:06.17 +56:38:59.2
23:48:25.43 +53:27:14.5
23:45:17.16 +56:33:48.8
23:40:15.18 +55:54:40.3
23:51:14.96 +52:36:43.8
23:34:44.95 +50:14:51.3
00:04:32.90 +52:54:20.2
00:18:03.21 +50:32:31.8
23:35:22.67 +56:30:55.7
00:22:04.53 +54:21:13.0
23:51:37.10 +52:54:02.5
23:55:25.10 +51:47:33.2
23:29:43.59 +54:42:05.1
23:36:42.47 +50:50:13.4
23:45:29.28 +53:49:18.7
23:33:43.42 +56:50:45.6
23:29:17.32 +55:18:42.5
23:43:00.44 +52:41:51.6
23:43:36.10 +53:16:07.0
00:14:53.89 +53:15:42.4
23:33:26.69 +52:54:43.2
23:32:10.90 +52:54:26.7
00:31:48.37 +56:53:27.1
00:22:44.23 +52:22:58.0
00:23:22.97 +55:49:13.9
00:24:38.31 +56:58:50.9
00:27:10.97 +50:01:18.1
23:53:29.10 +53:32:26.0
00:13:38.09 +52:03:06.5
00:24:51.20 +53:02:33.5
23:53:49.14 +53:08:16.8
00:02:56.34 +56:52:15.6
00:20:04.73 +50:09:06.4
00:07:37.86 +53:34:09.5
00:12:56.74 +50:00:20.0
23:41:52.68 +53:03:28.6
23:58:59.53 +53:17:26.1
00:26:27.14 +51:06:31.0
00:29:32.20 +53:56:40.1
00:31:11.75 +56:46:20.1
00:25:44.55 +54:58:05.4
00:20:03.71 +51:55:20.5
00:22:23.70 +53:06:02.8
23:54:23.41 +55:37:41.3
00:22:36.64 +51:54:06.2
00:25:02.62 +52:51:24.1
00:14:16.81 +56:52:39.6
00:27:16.87 +54:05:35.9
00:11:48.29 +52:52:36.7
00:22:18.53 +54:16:24.8
23:35:46.63 +49:52:31.1
23:43:03.88 +54:27:17.2
00:18:10.07 +54:09:39.8
00:19:46.94 +51:04:47.8
00:30:03.91 +55:50:24.4
00:05:12.48 +52:08:44.2
23:57:06.40 +52:12:18.3
23:41:15.33 +54:56:13.8
00:00:55.88 +53:17:46.2
23:33:31.54 +56:43:43.0
23:30:29.06 +55:42:25.8
23:57:15.32 +56:43:46.6
23:33:30.72 +49:44:37.1
23:41:21.68 +55:49:16.9
23:51:18.77 +53:33:31.6
00:06:22.15 +52:40:48.3
00:16:56.10 +51:18:54.7
00:04:13.83 +51:49:57.8
23:48:20.02 +54:53:08.0
23:35:32.57 +53:11:46.4
00:07:44.94 +50:07:04.6
23:56:55.55 +56:39:43.0
23:52:08.08 +55:52:15.5
23:48:54.10 +52:52:59.3
23:34:01.28 +52:35:02.4
23:32:25.48 +52:35:05.5
23:51:52.62 +53:48:17.4
23:42:44.51 +53:52:54.1
00:14:38.20 +54:13:58.9
00:02:24.25 +54:59:50.0
00:02:03.49 +55:39:54.1
23:46:55.28 +58:01:13.4
00:20:45.27 +50:11:53.4
00:26:00.35 +53:55:15.5
23:59:54.83 +56:58:33.0
23:38:16.57 +56:01:50.6
23:50:45.88 +53:34:28.0
23:58:25.46 +51:26:27.8
00:23:10.19 +55:47:39.9
###################################################################################
23:32:12.26 +52:55:03.9 -- not an asteroid (will add it to exclusion list)
00:20:44.11 +50:11:43.0 -- not an asteroid (will add it to exclusion list)
00:02:19.07 +54:08:11.0 -- not an asteroid (will add it to exclusion list)
00:13:33.15 +53:52:03.8 -- not an asteroid (will add it to exclusion list)
00:11:08.37 +52:33:49.5 -- not an asteroid (will add it to exclusion list)
23:38:16.61 +56:01:35.0 -- not an asteroid (will add it to exclusion list)
23:58:27.04 +51:26:22.6 -- not an asteroid (will add it to exclusion list)
23:44:45.09 +58:01:07.3 -- not an asteroid (will add it to exclusion list)
23:46:04.57 +54:20:47.4 -- not an asteroid (will add it to exclusion list)
23:47:18.24 +54:24:27.4 -- not an asteroid (will add it to exclusion list)
00:05:48.00 +55:40:11.5 -- not an asteroid (will add it to exclusion list)
23:32:49.97 +51:33:20.2 -- not an asteroid (will add it to exclusion list)
00:20:45.15 +54:18:08.9 -- not an asteroid (will add it to exclusion list)
23:50:46.61 +52:51:41.2 -- not an asteroid (will add it to exclusion list)
23:48:32.96 +55:00:38.1 -- not an asteroid (will add it to exclusion list)
23:37:48.55 +55:18:46.0 -- not an asteroid (will add it to exclusion list)
00:03:44.46 +50:50:07.8 -- not an asteroid (will add it to exclusion list)
23:52:26.35 +53:22:23.6 -- not an asteroid (will add it to exclusion list)
00:15:30.46 +52:00:00.6 -- not an asteroid (will add it to exclusion list)
23:50:42.90 +52:47:03.3 -- not an asteroid (will add it to exclusion list)
00:23:06.17 +56:38:59.2 -- not an asteroid (will add it to exclusion list)
23:48:25.43 +53:27:14.5 -- not an asteroid (will add it to exclusion list)
23:45:17.16 +56:33:48.8 -- not an asteroid (will add it to exclusion list)
23:40:15.18 +55:54:40.3 -- not an asteroid (will add it to exclusion list)
23:51:14.96 +52:36:43.8 -- not an asteroid (will add it to exclusion list)
23:34:44.95 +50:14:51.3 -- not an asteroid (will add it to exclusion list)
00:04:32.90 +52:54:20.2 -- not an asteroid (will add it to exclusion list)
00:18:03.21 +50:32:31.8 -- not an asteroid (will add it to exclusion list)
23:35:22.67 +56:30:55.7 -- not an asteroid (will add it to exclusion list)
00:22:04.53 +54:21:13.0 -- not an asteroid (will add it to exclusion list)
23:51:37.10 +52:54:02.5 -- not an asteroid (will add it to exclusion list)
23:55:25.10 +51:47:33.2 -- not an asteroid (will add it to exclusion list)
23:29:43.59 +54:42:05.1 -- not an asteroid (will add it to exclusion list)
23:36:42.47 +50:50:13.4 -- not an asteroid (will add it to exclusion list)
23:45:29.28 +53:49:18.7 -- not an asteroid (will add it to exclusion list)
23:33:43.42 +56:50:45.6 -- not an asteroid (will add it to exclusion list)
23:29:17.32 +55:18:42.5 -- not an asteroid (will add it to exclusion list)
23:43:00.44 +52:41:51.6 -- not an asteroid (will add it to exclusion list)
23:43:36.10 +53:16:07.0 -- not an asteroid (will add it to exclusion list)
00:14:53.89 +53:15:42.4 -- not an asteroid (will add it to exclusion list)
23:33:26.69 +52:54:43.2 -- not an asteroid (will add it to exclusion list)
23:32:10.90 +52:54:26.7 -- not an asteroid (will add it to exclusion list)
00:31:48.37 +56:53:27.1 -- not an asteroid (will add it to exclusion list)
00:22:44.23 +52:22:58.0 -- not an asteroid (will add it to exclusion list)
00:23:22.97 +55:49:13.9 -- not an asteroid (will add it to exclusion list)
00:24:38.31 +56:58:50.9 -- not an asteroid (will add it to exclusion list)
00:27:10.97 +50:01:18.1 -- not an asteroid (will add it to exclusion list)
23:53:29.10 +53:32:26.0 -- not an asteroid (will add it to exclusion list)
00:13:38.09 +52:03:06.5 -- not an asteroid (will add it to exclusion list)
00:24:51.20 +53:02:33.5 -- not an asteroid (will add it to exclusion list)
23:53:49.14 +53:08:16.8 -- not an asteroid (will add it to exclusion list)
00:02:56.34 +56:52:15.6 -- not an asteroid (will add it to exclusion list)
00:20:04.73 +50:09:06.4 -- not an asteroid (will add it to exclusion list)
00:07:37.86 +53:34:09.5 -- not an asteroid (will add it to exclusion list)
00:12:56.74 +50:00:20.0 -- not an asteroid (will add it to exclusion list)
23:41:52.68 +53:03:28.6 -- not an asteroid (will add it to exclusion list)
23:58:59.53 +53:17:26.1 -- not an asteroid (will add it to exclusion list)
00:26:27.14 +51:06:31.0 -- not an asteroid (will add it to exclusion list)
00:29:32.20 +53:56:40.1 -- not an asteroid (will add it to exclusion list)
00:31:11.75 +56:46:20.1 -- not an asteroid (will add it to exclusion list)
00:25:44.55 +54:58:05.4 -- not an asteroid (will add it to exclusion list)
00:20:03.71 +51:55:20.5 -- not an asteroid (will add it to exclusion list)
00:22:23.70 +53:06:02.8 -- not an asteroid (will add it to exclusion list)
23:54:23.41 +55:37:41.3 -- not an asteroid (will add it to exclusion list)
00:22:36.64 +51:54:06.2 -- not an asteroid (will add it to exclusion list)
00:25:02.62 +52:51:24.1 -- not an asteroid (will add it to exclusion list)
00:14:16.81 +56:52:39.6 -- not an asteroid (will add it to exclusion list)
00:27:16.87 +54:05:35.9 -- not an asteroid (will add it to exclusion list)
00:11:48.29 +52:52:36.7 -- not an asteroid (will add it to exclusion list)
00:22:18.53 +54:16:24.8 -- not an asteroid (will add it to exclusion list)
23:35:46.63 +49:52:31.1 -- not an asteroid (will add it to exclusion list)
23:43:03.88 +54:27:17.2 -- not an asteroid (will add it to exclusion list)
00:18:10.07 +54:09:39.8 -- not an asteroid (will add it to exclusion list)
00:19:46.94 +51:04:47.8 -- not an asteroid (will add it to exclusion list)
00:30:03.91 +55:50:24.4 -- not an asteroid (will add it to exclusion list)
00:05:12.48 +52:08:44.2 -- not an asteroid (will add it to exclusion list)
23:57:06.40 +52:12:18.3 -- not an asteroid (will add it to exclusion list)
23:41:15.33 +54:56:13.8 -- not an asteroid (will add it to exclusion list)
00:00:55.88 +53:17:46.2 -- not an asteroid (will add it to exclusion list)
23:33:31.54 +56:43:43.0 -- not an asteroid (will add it to exclusion list)
23:30:29.06 +55:42:25.8 -- not an asteroid (will add it to exclusion list)
23:57:15.32 +56:43:46.6 -- not an asteroid (will add it to exclusion list)
23:33:30.72 +49:44:37.1 -- not an asteroid (will add it to exclusion list)
23:41:21.68 +55:49:16.9 -- not an asteroid (will add it to exclusion list)
23:51:18.77 +53:33:31.6 -- not an asteroid (will add it to exclusion list)
00:06:22.15 +52:40:48.3 -- not an asteroid (will add it to exclusion list)
00:16:56.10 +51:18:54.7 -- not an asteroid (will add it to exclusion list)
00:04:13.83 +51:49:57.8 -- not an asteroid (will add it to exclusion list)
23:48:20.02 +54:53:08.0 -- not an asteroid (will add it to exclusion list)
23:35:32.57 +53:11:46.4 -- not an asteroid (will add it to exclusion list)
00:07:44.94 +50:07:04.6 -- not an asteroid (will add it to exclusion list)
23:56:55.55 +56:39:43.0 -- not an asteroid (will add it to exclusion list)
23:52:08.08 +55:52:15.5 -- not an asteroid (will add it to exclusion list)
23:48:54.10 +52:52:59.3 -- not an asteroid (will add it to exclusion list)
23:34:01.28 +52:35:02.4 -- not an asteroid (will add it to exclusion list)
23:32:25.48 +52:35:05.5 -- not an asteroid (will add it to exclusion list)
23:51:52.62 +53:48:17.4 -- not an asteroid (will add it to exclusion list)
23:42:44.51 +53:52:54.1 -- not an asteroid (will add it to exclusion list)
00:14:38.20 +54:13:58.9 -- not an asteroid (will add it to exclusion list)
00:02:24.25 +54:59:50.0 -- not an asteroid (will add it to exclusion list)
00:02:03.49 +55:39:54.1 -- not an asteroid (will add it to exclusion list)
23:46:55.28 +58:01:13.4 -- not an asteroid (will add it to exclusion list)
00:20:45.27 +50:11:53.4 -- not an asteroid (will add it to exclusion list)
00:26:00.35 +53:55:15.5 -- not an asteroid (will add it to exclusion list)
23:59:54.83 +56:58:33.0 -- not an asteroid (will add it to exclusion list)
23:38:16.57 +56:01:50.6 -- not an asteroid (will add it to exclusion list)
23:50:45.88 +53:34:28.0 -- not an asteroid (will add it to exclusion list)
23:58:25.46 +51:26:27.8 -- not an asteroid (will add it to exclusion list)
00:23:10.19 +55:47:39.9 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:55.88 +53:17:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:03.49 +55:39:54.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:19.07 +54:08:11.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:24.25 +54:59:50.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:56.34 +56:52:15.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:44.46 +50:50:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:13.83 +51:49:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:32.90 +52:54:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:12.48 +52:08:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:48.00 +55:40:11.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:22.15 +52:40:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:37.86 +53:34:09.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:44.94 +50:07:04.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:08.37 +52:33:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:48.29 +52:52:36.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:56.74 +50:00:20.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:33.15 +53:52:03.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:38.09 +52:03:06.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:16.81 +56:52:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:38.20 +54:13:58.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:53.89 +53:15:42.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:30.46 +52:00:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:56.10 +51:18:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:03.21 +50:32:31.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:10.07 +54:09:39.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:46.94 +51:04:47.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:03.71 +51:55:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:04.73 +50:09:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:44.11 +50:11:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:45.15 +54:18:08.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:45.27 +50:11:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:04.53 +54:21:13.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:18.53 +54:16:24.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:23.70 +53:06:02.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:36.64 +51:54:06.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:44.23 +52:22:58.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:06.17 +56:38:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:10.19 +55:47:39.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:22.97 +55:49:13.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:38.31 +56:58:50.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:51.20 +53:02:33.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:02.62 +52:51:24.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:44.55 +54:58:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:00.35 +53:55:15.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:27.14 +51:06:31.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:10.97 +50:01:18.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:16.87 +54:05:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:32.20 +53:56:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:03.91 +55:50:24.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:11.75 +56:46:20.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:48.37 +56:53:27.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:17.32 +55:18:42.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:43.59 +54:42:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:29.06 +55:42:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:10.90 +52:54:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:12.26 +52:55:03.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:25.48 +52:35:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:49.97 +51:33:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:26.69 +52:54:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:30.72 +49:44:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:31.54 +56:43:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:43.42 +56:50:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:01.28 +52:35:02.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:44.95 +50:14:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:22.67 +56:30:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:32.57 +53:11:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:46.63 +49:52:31.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:42.47 +50:50:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:48.55 +55:18:46.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:16.57 +56:01:50.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:16.61 +56:01:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:15.18 +55:54:40.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:15.33 +54:56:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:21.68 +55:49:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:52.68 +53:03:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:44.51 +53:52:54.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:00.44 +52:41:51.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:03.88 +54:27:17.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:36.10 +53:16:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:45.09 +58:01:07.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:17.16 +56:33:48.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:29.28 +53:49:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:04.57 +54:20:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:55.28 +58:01:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:18.24 +54:24:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:20.02 +54:53:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:25.43 +53:27:14.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:32.96 +55:00:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:54.10 +52:52:59.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:42.90 +52:47:03.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:45.88 +53:34:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:46.61 +52:51:41.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:14.96 +52:36:43.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:18.77 +53:33:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:37.10 +52:54:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:52.62 +53:48:17.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:08.08 +55:52:15.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:26.35 +53:22:23.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:29.10 +53:32:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:49.14 +53:08:16.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:23.41 +55:37:41.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:25.10 +51:47:33.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:55.55 +56:39:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:06.40 +52:12:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:15.32 +56:43:46.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:25.46 +51:26:27.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:27.04 +51:26:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:59.53 +53:17:26.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:54.83 +56:58:33.0 -- 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:55.88 +53:17:46.2 -- not a known variable star
00:02:03.49 +55:39:54.1 -- not a known variable star
00:02:19.07 +54:08:11.0 -- not a known variable star
00:02:24.25 +54:59:50.0 -- a known variable star
00:02:56.34 +56:52:15.6 -- not a known variable star
00:03:44.46 +50:50:07.8 -- not a known variable star
00:04:13.83 +51:49:57.8 -- not a known variable star
00:04:32.90 +52:54:20.2 -- not a known variable star
00:05:12.48 +52:08:44.2 -- not a known variable star
00:05:48.00 +55:40:11.5 -- not a known variable star
00:06:22.15 +52:40:48.3 -- not a known variable star
00:07:37.86 +53:34:09.5 -- not a known variable star
00:07:44.94 +50:07:04.6 -- not a known variable star
00:11:08.37 +52:33:49.5 -- not a known variable star
00:11:48.29 +52:52:36.7 -- not a known variable star
00:12:56.74 +50:00:20.0 -- not a known variable star
00:13:33.15 +53:52:03.8 -- not a known variable star
00:13:38.09 +52:03:06.5 -- not a known variable star
00:14:16.81 +56:52:39.6 -- not a known variable star
00:14:38.20 +54:13:58.9 -- not a known variable star
00:14:53.89 +53:15:42.4 -- not a known variable star
00:15:30.46 +52:00:00.6 -- not a known variable star
00:16:56.10 +51:18:54.7 -- not a known variable star
00:18:03.21 +50:32:31.8 -- not a known variable star
00:18:10.07 +54:09:39.8 -- not a known variable star
00:19:46.94 +51:04:47.8 -- not a known variable star
00:20:03.71 +51:55:20.5 -- not a known variable star
00:20:04.73 +50:09:06.4 -- not a known variable star
00:20:44.11 +50:11:43.0 -- not a known variable star
00:20:45.15 +54:18:08.9 -- not a known variable star
00:20:45.27 +50:11:53.4 -- not a known variable star
00:22:04.53 +54:21:13.0 -- not a known variable star
00:22:18.53 +54:16:24.8 -- not a known variable star
00:22:23.70 +53:06:02.8 -- not a known variable star
00:22:36.64 +51:54:06.2 -- not a known variable star
00:22:44.23 +52:22:58.0 -- not a known variable star
00:23:06.17 +56:38:59.2 -- not a known variable star
00:23:10.19 +55:47:39.9 -- not a known variable star
00:23:22.97 +55:49:13.9 -- not a known variable star
00:24:38.31 +56:58:50.9 -- not a known variable star
00:24:51.20 +53:02:33.5 -- not a known variable star
00:25:02.62 +52:51:24.1 -- not a known variable star
00:25:44.55 +54:58:05.4 -- not a known variable star
00:26:00.35 +53:55:15.5 -- not a known variable star
00:26:27.14 +51:06:31.0 -- a known variable star
00:27:10.97 +50:01:18.1 -- not a known variable star
00:27:16.87 +54:05:35.9 -- not a known variable star
00:29:32.20 +53:56:40.1 -- not a known variable star
00:30:03.91 +55:50:24.4 -- a known variable star
00:31:11.75 +56:46:20.1 -- not a known variable star
00:31:48.37 +56:53:27.1 -- not a known variable star
23:29:17.32 +55:18:42.5 -- not a known variable star
23:29:43.59 +54:42:05.1 -- not a known variable star
23:30:29.06 +55:42:25.8 -- not a known variable star
23:32:10.90 +52:54:26.7 -- not a known variable star
23:32:12.26 +52:55:03.9 -- not a known variable star
23:32:25.48 +52:35:05.5 -- not a known variable star
23:32:49.97 +51:33:20.2 -- not a known variable star
23:33:26.69 +52:54:43.2 -- not a known variable star
23:33:30.72 +49:44:37.1 -- not a known variable star
23:33:31.54 +56:43:43.0 -- not a known variable star
23:33:43.42 +56:50:45.6 -- not a known variable star
23:34:01.28 +52:35:02.4 -- not a known variable star
23:34:44.95 +50:14:51.3 -- not a known variable star
23:35:22.67 +56:30:55.7 -- not a known variable star
23:35:32.57 +53:11:46.4 -- not a known variable star
23:35:46.63 +49:52:31.1 -- not a known variable star
23:36:42.47 +50:50:13.4 -- not a known variable star
23:37:48.55 +55:18:46.0 -- not a known variable star
23:38:16.57 +56:01:50.6 -- not a known variable star
23:38:16.61 +56:01:35.0 -- not a known variable star
23:40:15.18 +55:54:40.3 -- not a known variable star
23:41:15.33 +54:56:13.8 -- not a known variable star
23:41:21.68 +55:49:16.9 -- not a known variable star
23:41:52.68 +53:03:28.6 -- not a known variable star
23:42:44.51 +53:52:54.1 -- not a known variable star
23:43:00.44 +52:41:51.6 -- a known variable star
23:43:03.88 +54:27:17.2 -- not a known variable star
23:43:36.10 +53:16:07.0 -- not a known variable star
23:44:45.09 +58:01:07.3 -- a known variable star
23:45:17.16 +56:33:48.8 -- a known variable star
23:45:29.28 +53:49:18.7 -- not a known variable star
23:46:04.57 +54:20:47.4 -- not a known variable star
23:46:55.28 +58:01:13.4 -- not a known variable star
23:47:18.24 +54:24:27.4 -- not a known variable star
23:48:20.02 +54:53:08.0 -- not a known variable star
23:48:25.43 +53:27:14.5 -- not a known variable star
23:48:32.96 +55:00:38.1 -- not a known variable star
23:48:54.10 +52:52:59.3 -- not a known variable star
23:50:42.90 +52:47:03.3 -- not a known variable star
23:50:45.88 +53:34:28.0 -- not a known variable star
23:50:46.61 +52:51:41.2 -- not a known variable star
23:51:14.96 +52:36:43.8 -- not a known variable star
23:51:18.77 +53:33:31.6 -- not a known variable star
23:51:37.10 +52:54:02.5 -- not a known variable star
23:51:52.62 +53:48:17.4 -- not a known variable star
23:52:08.08 +55:52:15.5 -- not a known variable star
23:52:26.35 +53:22:23.6 -- not a known variable star
23:53:29.10 +53:32:26.0 -- not a known variable star
23:53:49.14 +53:08:16.8 -- not a known variable star
23:54:23.41 +55:37:41.3 -- not a known variable star
23:55:25.10 +51:47:33.2 -- not a known variable star
23:56:55.55 +56:39:43.0 -- not a known variable star
23:57:06.40 +52:12:18.3 -- not a known variable star
23:57:15.32 +56:43:46.6 -- not a known variable star
23:58:25.46 +51:26:27.8 -- not a known variable star
23:58:27.04 +51:26:22.6 -- not a known variable star
23:58:59.53 +53:17:26.1 -- not a known variable star
23:59:54.83 +56:58:33.0 -- a known variable star
Found 102 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
109 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 109 (excluding asteroids and hot pixels, 102 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)2461230.84306233 -observatory V36
07:34:54.82 +17:11:15.4 Mercury (4.8mag)
10:07:24.32 +13:07:19.1 Venus (-4.1mag)
04:21:11.12 +21:17:30.9 Mars (1.3mag)
08:15:45.70 +20:14:21.2 Jupiter (-1.8mag)
00:55:44.07 +03:20:04.1 Saturn (0.7mag)
04:07:02.38 +20:44:31.9 Uranus (5.8mag)
00:17:01.71 +00:20:46.0 Neptune (7.8mag)
20:31:00.46 -23:17:34.0 Pluto (14.4mag)
02:13:34.91 +17:38:17.4 Moon (-9.9mag)
-rw-r--r-- 1 apache apache 361 Jul 9 05:02 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461230.84306233:
08:15:43.74 +20:14:27.7 Io (6.1mag)
08:15:36.85 +20:14:54.6 Europa (6.3mag)
08:15:54.04 +20:13:54.9 Ganymede (5.6mag)
08:16:15.80 +20:12:32.5 Callisto (6.8mag)
08:14:20.03 +19:58:06.1 Himalia (15.7mag)
08:15:49.01 +20:14:09.4 Thebe (16.6mag)
08:13:41.68 +20:02:50.1 Elara (17.6mag)
08:19:15.99 +20:09:03.8 Pasiphae (17.8mag)
08:20:46.97 +20:19:17.7 Carme (19.0mag)
00:55:32.30 +03:20:07.0 Titan (8.5mag)
00:55:43.16 +03:20:15.7 Rhea (9.8mag)
00:55:14.72 +03:19:24.8 Iapetus (11.2mag)
00:55:56.45 +03:20:14.9 Hyperion (14.5mag)
00:55:46.14 +03:17:26.7 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jul 9 05:02 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461230.84306233:
17:44:54.46 -33:11:52.1 JWST
19:52:42.58 -09:48:09.7 Chandra
09:51:33.84 -55:39:56.4 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jul 9 05:02 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461230.84306233 -observatory V36
02:34:49.60 +14:18:24.0 17.9mag P/1996 R2 (Lagerkvist)
18:18:43.54 -34:19:57.5 13.7mag P/2010 H2 (Vales)
06:24:39.80 -68:07:29.2 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
06:00:27.16 +32:25:48.2 17.6mag C/2017 K2 (PANSTARRS)
17:03:24.47 +16:03:10.4 18.0mag C/2021 G2 (ATLAS)
01:41:51.99 +06:08:06.7 15.4mag P/2021 N1 (ZTF)
23:00:07.36 +32:17:06.7 17.3mag C/2022 E2 (ATLAS)
06:11:14.56 +26:56:04.9 16.7mag C/2022 N2 (PANSTARRS)
09:54:38.44 +29:49:32.7 16.8mag C/2022 QE78 (ATLAS)
09:09:05.25 +04:58:44.2 17.8mag C/2022 R6 (PANSTARRS)
18:07:50.32 +21:19:50.3 17.9mag C/2023 A3 (Tsuchinshan-ATLAS)
15:11:41.90 -11:21:55.9 17.7mag P/2023 B1 (PANSTARRS)
21:50:25.51 +67:37:27.3 17.8mag C/2023 H5 (Lemmon)
16:32:54.57 -09:58:20.1 13.9mag C/2023 R1 (PANSTARRS)
07:58:54.86 +65:39:18.1 17.9mag C/2024 A1 (ATLAS)
07:31:29.05 +29:57:03.5 14.6mag C/2024 E1 (Wierzchos)
15:16:49.57 +15:17:59.6 17.5mag C/2024 G6 (ATLAS)
19:42:34.68 +39:11:26.4 13.8mag C/2024 J3 (ATLAS)
21:48:36.04 +45:50:55.5 17.8mag C/2024 R4 (PANSTARRS)
04:48:40.93 -13:50:35.8 15.7mag C/2024 T5 (ATLAS)
06:33:43.83 +29:14:16.4 18.0mag C/2025 J1 (Borisov)
07:13:37.14 -12:48:09.4 16.4mag C/2025 R3 (PANSTARRS)
09:54:56.00 +22:28:44.4 17.6mag C/2025 V2 (Rankin)
12:44:17.56 +03:58:46.4 17.1mag C/2025 Y1 (ATLAS)
16:54:50.87 +79:05:36.0 17.4mag C/2026 A2 (Bok)
02:45:10.52 +45:11:42.2 16.7mag C/2026 B2 (Sun-Gao)
11:24:52.83 +04:21:36.6 16.9mag A/2026 E1
21:17:26.02 -14:43:37.2 7.3mag 10P/Tempel
11:12:59.37 -01:50:42.3 16.1mag 29P/Schwassmann-Wachmann
03:58:42.60 +29:26:32.6 17.8mag 47P/Ashbrook-Jackson
10:05:57.89 +14:19:55.5 17.0mag 63P/Wild
00:47:54.28 -05:06:25.3 15.6mag 65P/Gunn
08:23:47.50 +34:15:47.9 17.9mag 76P/West-Kohoutek-Ikemura
04:24:57.12 +20:07:23.5 13.7mag 78P/Gehrels
02:20:40.42 +10:28:00.3 16.2mag 88P/Howell
06:32:30.38 +30:35:23.4 15.7mag 93P/Lovas
04:17:44.02 +31:04:30.3 16.9mag 114P/Wiseman-Skiff
08:06:13.51 +30:48:46.3 15.3mag 123P/West-Hartley
10:46:15.22 +01:35:55.1 16.8mag 124P/Mrkos
04:50:06.07 +20:46:56.8 16.2mag 128P/Shoemaker-Holt
05:34:20.58 +19:43:11.4 17.8mag 131P/Mueller
00:01:15.23 +02:53:37.9 17.9mag 139P/Vaisala-Oterma
07:09:46.98 +17:14:08.5 15.4mag 141P-D/Machholz
03:16:24.19 -21:11:32.2 15.5mag 161P/Hartley-IRAS
05:29:25.89 +33:43:24.1 15.3mag 162P/SidingSpring
19:06:53.33 +14:28:57.6 14.8mag 169P/NEAT
01:38:35.93 +07:28:51.0 17.7mag 220P/McNaught
16:36:08.12 -08:20:53.6 17.0mag 235P/LINEAR
08:43:08.90 +33:23:27.6 17.9mag 240P/NEAT
20:42:33.59 -49:20:32.2 17.8mag 259P/Garradd
01:56:29.27 +11:37:19.8 15.7mag 260P/McNaught
05:34:10.22 +36:45:26.6 17.4mag 295P/LINEAR
15:06:40.93 +06:08:42.4 17.6mag 391P/Kowalski
08:33:41.96 +19:43:01.9 17.9mag 450P/LONEOS
07:50:10.57 +39:17:58.6 17.9mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.7K Jul 9 05:02 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
11:06:55.46 -04:07:04.50 AT2026qqg 2026-07-5.01 16.82
19:07:23.69 -74:13:37.30 AT2026qly 2026-07-5.02 17.31
17:57:43.80 +27:18:40.10 ASASSN-26ea 2026-07-5.07 16.67
19:59:01.43 -32:07:34.30 ASASSN-26eb 2026-07-4.97 15.52
18:46:50.35 -57:44:13.20 SN 2026qqp 2026-07-5.03 -0.92
19:17:31.69 -39:55:29.90 ASASSN-26dz 2026-07-5.14 15.91
19:14:31.37 +12:03:52.90 AT 2026rdg 2026-07-3.43 11.81
04:05:50.09 -70:24:34.40 AT 2026qpr 2026-06-30.4 15.96
13:45:37.49 -05:59:35.80 SN 2026pub 2026-06-30.09 16.01
16:41:15.63 +39:17:14.70 SN 2026pel 2026-06-26.38 16.07
10:14:40.19 -35:38:21.30 ASASSN-26dy 2026-06-25.99 15.63
14:47:21.56 -40:15:51.30 ASASSN-26dv 2026-06-23.03 14.62
13:38:49.79 -77:21:06.70 ASASSN-26dw 2026-06-23.04 16.09
00:59:27.90 +33:08:13.20 SN 2026mke 2026-06-22.39 17.13
11:10:44.73 -30:20:45.50 SN 2026nmv 2026-06-22.06 16.56
21:36:15.68 -21:19:12.50 AT2026oxh 2026-06-22.15 17.14
17:31:38.38 -56:05:51.90 ASASSN-26dx 2026-06-22.02 14.72
14:10:13.44 -38:46:46.10 AT2026pvk 2026-06-22.06 16.53
20:56:47.23 -18:31:05.20 AT2026plb 2026-06-21.31 16.4
15:44:29.68 +21:00:59.30 SN2026ore 2026-06-21.29 17.57
23:50:05.98 -14:01:41.30 AT2026oxl 2026-06-21.52 17.64
17:36:54.73 -18:10:04.20 AT2026ouj 2026-06-20.92 15.15
00:34:04.08 -30:22:09.20 AT2026ntk 2026-06-18.09 17.34
20:49:13.39 +25:17:59.20 ASASSN-26du 2026-06-15.39 15.93
23:09:30.84 +32:40:42.00 SN2026oxc 2026-06-14.35 16.83
02:02:26.78 +32:04:21.30 AT2026ovz 2026-06-14.59 15.39
21:26:28.11 -72:31:19.50 AT2026nwc 2026-06-11 17.05
17:54:57.33 +26:32:34.20 SN 2026odc 2026-06-11.23 17.62
13:55:59.94 +17:30:37.20 SN 2026nyq 2026-06-11.1 16.24
00:50:45.14 -71:38:36.90 ASASSN-26dt 2026-06-11.13 10.22
14:42:19.73 +19:11:35.60 SN2026nyp 2026-06-10.3 16.32
12:23:23.92 +12:56:43.50 SN2026mta 2026-06-8.29 16.69
12:30:18.51 +47:12:33.20 SN2026oao 2026-06-9.32 17.02
10:51:05.21 -42:28:56.60 AT2026nvf 2026-06-8.12 16.75
13:50:22.48 -07:35:00.00 SN2026npn 2026-06-8.02 17.58
00:56:07.17 +43:01:43.20 ASASSN-26dq 2026-06-7.43 13.58
01:07:49.46 +41:59:43.70 SN 2026obc 2026-06-7.43 15.15
21:11:25.22 +14:14:31.90 ASASSN-26dr 2026-06-7.24 16.24
06:21:27.06 -65:16:42.00 ASASSN-26ds 2026-06-2.97 15.02
20:07:38.15 -21:07:05.40 SN2026mho 2026-05-25.18 -1.12
11:29:42.55 +79:01:03.10 AT2026min 2026-05-24.21 16.63
11:44:33.11 -68:48:32.90 ASASSN-26no 2026-05-24.03 8.35
19:00:42.82 -48:31:01.60 ASASSN-26dp 2026-05-22.31 -3.28
14:23:56.72 -58:37:47.60 ASASSN-26dn 2026-05-20.01 14.64
11:24:54.06 +47:57:01.60 AT2026nma 2026-05-20.29 15.46
21:27:08.58 +33:24:38.10 AT2026lli 2026-05-19.34 15.86
00:31:01.41 -13:38:51.70 AT2026nad 2026-05-19.39 15.34
15:16:06.61 -79:16:32.40 ASASSN-26dm 2026-05-19.03 14.44
11:24:25.21 -59:23:19.10 ASASSN-26dl 2026-05-18.02 13.55
13:45:51.52 -53:16:01.00 ASASSN-26dk 2026-05-18.16 12.96
02:05:49.69 -30:29:09.60 ASASSN-26dh 2026-05-18.43 15.37
17:50:22.87 -39:42:33.90 ASASSN-26dj 2026-05-17.05 15.7
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
09:46:31.08 -33:41:51.00 ASASSN-26di 2026-05-12.14 14.63
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:48.82 -61:36:13.20 ASASSN-26dd 2026-05-5.21 15.15
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.97 -54:34:58.00 ASASSN-26da 2026-04-25.32 16.11
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.47 -16:06:07.00 ASASSN-26cz 2026-04-22.24 16.32
11:06:55.46 -04:07:04.50 2026-07-5.01 16.82
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.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
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
11:06:55.46 -04:07:04.50 2026-07-5.01 16.82
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
-rw-r--r-- 1 apache apache 5.6K Jul 9 05:02 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
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
00:43:01.82 +41:18:16.6 PNV J00430182+4118166 2026-05-21.8651 18.83Cmag
00:42:51.20 +41:16:59.4 PNV J00425120+4116594 2022-10-26.135 19.3mag
12:24:25.10 +28:47:12.0 TCP J12242510+2847120 2026-05-31.6015 14.8mag
00:56:07.13 +43:01:40.6 TCP J00560713+4301406 2026-06-01.4135 12.2mag
00:42:41.64 +41:15:16.2 PNV J00424164+4115162 2026-06-02.029 17.4mag
00:42:38.68 +41:15:58.2 PNV J00423868+4115582 2026-06-05.1224 19.97Umag
19:00:42.95 -48:31:01.7 PNV J19004295-4831017 2026-05-25.0752 14.2mag
09:55:21.28 +69:02:52.6 PNV J09552128+6902526 2026-06-13.933 18.9mag
19:51:21.42 +37:06:40.0 TCP J19512142+3706400 2026-06-17.2942 16.8mag
19:57:03.87 +37:41:46.4 TCP J19570387+3741464 2026-06-18.2638 17.5mag
00:42:32.04 +41:10:28.3 PNV J00423204+4110283 2026-06-26.059 16.6mag
-rw-r--r-- 1 apache apache 189K Jul 9 05:02 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
11:33:44.560 +08:30:07.07 AT 2026sat 2026-02-24.39 21.41
08:00:10.849 +05:26:59.81 AT 2026sas 2026-02-21.30 21.05
10:51:43.146 -09:31:06.23 AT 2026sar 2026-02-19.48 20.29
10:51:34.352 +08:06:49.38 AT 2026saq 2026-02-13.44 20.68
09:38:33.432 +10:45:07.43 AT 2026sap 2026-02-13.36 20.97
15:59:23.653 +14:20:57.72 AT 2026sao 2026-02-13.59 20.61
15:41:32.287 +11:12:49.49 AT 2026san 2026-02-13.58 20.47
09:15:15.347 +11:04:37.70 AT 2026sam 2026-02-13.35 20.55
13:05:47.988 -13:00:23.88 AT 2026sal 2026-02-17.60 20.41
13:52:20.715 -15:18:06.40 AT 2026sak 2026-02-17.61 21.24
07:50:38.140 +40:44:32.00 AT 2026saj 2026-02-14.33 20.92
08:13:01.261 +05:09:04.21 AT 2026sai 2026-02-14.36 21
08:04:49.349 +05:00:10.52 AT 2026sah 2026-02-14.38 21.43
09:35:57.314 -01:44:43.08 AT 2026sag 2026-02-14.42 20.63
12:39:37.267 -02:49:17.09 AT 2026saf 2026-02-24.50 20.68
12:07:45.006 -03:33:54.20 AT 2026sae 2026-02-12.60 20.61
11:58:32.550 -07:18:56.49 AT 2026sad 2026-02-12.60 20.54
16:15:47.199 +17:27:18.98 AT 2026sac 2026-02-04.66 20.37
12:57:52.802 +17:54:51.67 AT 2026sab 2026-02-14.51 20.41
13:12:34.769 +20:19:12.56 AT 2026saa 2026-02-14.51 20.37
-rw-r--r-- 1 apache apache 30K Jul 9 05:02 tns_transients_list.txt
