This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G
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 06 24.3304 2461215.8304 11.01 00:20:45.24 +50:11:48.3
117.91308 -12.37575 galactic Cas Second-epoch detections are separated by 8.0" and 8.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:20:45.24 +50:11: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:20:45.24 +50:11:48.3: 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:45.24 +50:11:48.3: 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 06 24.3304* 00 20 45.24 +50 11 48.3 11.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,2461215.8304,11.01,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 20260624.3304 11.01CV 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 06 24.3304 2461215.8304 11.53 00:14:53.77 +53:15:40.4
117.41078 -9.21835 galactic Cas Second-epoch detections are separated by 1.8" and 8.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 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.77 +53:15:40.4: 12.58 +/- 0.02 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.77 +53:15:40.4: 12.58 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.58 +/- 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 06 24.3304* 00 14 53.77 +53 15 40.4 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
Gaia DR3 419245673457567232,2461215.8304,11.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
Gaia DR3 419245673457567232 20260624.3304 11.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 06 24.3304 2461215.8304 11.72 23:52:37.81 +56:44:34.2
114.89823 -5.20883 galactic Cas Second-epoch detections are separated by 0.9" and 8.8 pix
The object was found in VSX 7" DH Cas
Type: M
# Max. Min./Amp. JD0 Period
13.500 pg < 16.800 pg 2427942.00000 322.000000000000 C
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:52:37.81 +56:44:34.2: 12.85 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:37.81 +56:44:34.2: 12.78 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.81 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 52 37.81 +56 44 34.2 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
DH Cas,2461215.8304,11.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
DH Cas 20260624.3304 11.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 06 24.3304 2461215.8304 11.71 00:02:19.47 +54:07:55.8
115.70256 -8.04876 galactic Cas Second-epoch detections are separated by 4.5" and 8.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 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.47 +54:07:55.8: 13.47 +/- 0.04 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.47 +54:07:55.8: 13.46 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.46 +/- 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 06 24.3304* 00 02 19.47 +54 07 55.8 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,2461215.8304,11.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
Gaia DR3 420317392359633792 20260624.3304 11.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 06 24.3304 2461215.8304 11.80 00:17:34.48 +51:29:01.4
117.57233 -11.03529 galactic Cas Second-epoch detections are separated by 7.0" and 8.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:17:34.48 +51:29:01.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:17:34.48 +51:29:01.4: 15.59 +/- 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:17:34.48 +51:29:01.4: 15.59 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 00 17 34.48 +51 29 01.4 11.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,2461215.8304,11.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
target 20260624.3304 11.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 06 24.3304 2461215.8304 11.85 00:08:26.91 +53:20:25.4
116.45957 -8.99026 galactic Cas Second-epoch detections are separated by 8.7" and 8.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:08:26.91 +53:20:25.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:08:26.91 +53:20:25.4: 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 00:08:26.91 +53:20:25.4: 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 06 24.3304* 00 08 26.91 +53 20 25.4 11.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,2461215.8304,11.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 11.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 11.88 00:11:36.91 +53:41:32.0
116.98731 -8.71926 galactic Cas Second-epoch detections are separated by 8.4" and 8.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 420021000955394944 | 00:11:40.48 +53:41:00.8 (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:36.91 +53:41:32.0: 15.57 +/- 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:36.91 +53:41:32.0: 15.56 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 00 11 36.91 +53 41 32.0 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420021000955394944,2461215.8304,11.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
Gaia DR3 420021000955394944 20260624.3304 11.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 06 24.3304 2461215.8304 11.97 00:01:47.62 +53:05:06.4
115.42068 -9.06110 galactic Cas Second-epoch detections are separated by 5.6" and 8.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:01:47.62 +53:05:06.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:01:47.62 +53:05:06.4: 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:01:47.62 +53:05:06.4: 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 06 24.3304* 00 01 47.62 +53 05 06.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
target,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 11.99 00:03:57.40 +54:08:00.3
115.93996 -8.09249 galactic Cas Second-epoch detections are separated by 3.3" and 8.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 J001.0029+54.1348 | 00:03:59.75 +54:07:47.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:03:57.40 +54:08:00.3: 14.24 +/- 0.10 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:03:57.40 +54:08:00.3: 14.21 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.23 +/- 0.07
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 06 24.3304* 00 03 57.40 +54 08 00.3 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
ATO J001.0029+54.1348,2461215.8304,11.99,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.0029+54.1348 20260624.3304 11.99CV 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 06 24.3304 2461215.8304 11.96 00:18:28.50 +53:39:28.5
117.99987 -8.89788 galactic Cas Second-epoch detections are separated by 6.1" and 8.7 pix
The object was found in VSX20" Gaia DR3 419316321382504448
Type: ROT
# Max. Min./Amp. JD0 Period
16.900 G 17.050 G 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:18:28.50 +53:39:28.5: 15.16 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:18:28.50 +53:39:28.5: 15.25 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.20 +/- 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 06 24.3304* 00 18 28.50 +53 39 28.5 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 419316321382504448,2461215.8304,11.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
Gaia DR3 419316321382504448 20260624.3304 11.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
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 11.97 00:02:37.91 +53:39:41.0
115.65676 -8.51953 galactic Cas Second-epoch detections are separated by 5.2" and 8.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 396262380046129408 | 00:02:40.18 +53:39:02.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:02:37.91 +53:39:41.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:02:37.91 +53:39:41.0: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 00 02 37.91 +53 39 41.0 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 396262380046129408,2461215.8304,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
Gaia DR3 396262380046129408 20260624.3304 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 06 24.3304 2461215.8304 12.05 23:51:15.90 +52:09:19.5
113.63720 -9.62707 galactic Cas Second-epoch detections are separated by 4.4" and 9.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 J357.8125+52.1652 | 23:51:15.90 +52:09:19.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:15.90 +52:09:19.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 23:51:15.90 +52:09:19.5: 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 06 24.3304* 23 51 15.90 +52 09 19.5 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
ATO J357.8125+52.1652,2461215.8304,12.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
ATO J357.8125+52.1652 20260624.3304 12.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 06 24.3304 2461215.8304 12.10 23:46:02.67 +53:33:15.4
113.20862 -8.07841 galactic Cas Second-epoch detections are separated by 3.1" and 9.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:46:02.67 +53:33:15.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:02.67 +53:33:15.4: 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 23:46:02.67 +53:33:15.4: 15.61 +/- 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 06 24.3304* 23 46 02.67 +53 33 15.4 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,12.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 20260624.3304 12.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 06 24.3304 2461215.8304 12.12 00:00:59.21 +53:46:34.6
115.43783 -8.35977 galactic Cas Second-epoch detections are separated by 1.6" and 9.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 396276428875775232 | 00:01:01.08 +53:45:51.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:00:59.21 +53:46:34.6: 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:00:59.21 +53:46:34.6: 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 06 24.3304* 00 00 59.21 +53 46 34.6 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 396276428875775232,2461215.8304,12.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
Gaia DR3 396276428875775232 20260624.3304 12.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 06 24.3304 2461215.8304 12.13 23:55:38.47 +52:35:17.7
114.39604 -9.35630 galactic Cas Second-epoch detections are separated by 5.1" and 9.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:55:38.47 +52:35:17.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:55:38.47 +52:35:17.7: 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 23:55:38.47 +52:35:17.7: 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 06 24.3304* 23 55 38.47 +52 35 17.7 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,2461215.8304,12.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 20260624.3304 12.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 06 24.3304 2461215.8304 12.11 00:17:42.48 +53:21:25.8
117.84560 -9.18115 galactic Cas Second-epoch detections are separated by 2.2" and 8.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:17:42.48 +53:21: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 00:17:42.48 +53:21:25.8: 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:17:42.48 +53:21:25.8: 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 06 24.3304* 00 17 42.48 +53 21 25.8 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 12.10 00:02:01.81 +53:59:20.0
115.63199 -8.18110 galactic Cas Second-epoch detections are separated by 0.3" and 8.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 | NSVS J0002034+535901 | 00:02:03.89 +53:58:58.7 (Gaia DR3) | SR (local) | 2458357.13120 (local) | Gaia3var=VARIABLE J-Ks=0.393+/-0.066 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:01.81 +53:59:20.0: 14.09 +/- 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:01.81 +53:59:20.0: 14.04 +/- 0.07 detection
Forced photometry reference-image weighted average: 14.06 +/- 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 06 24.3304* 00 02 01.81 +53 59 20.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
NSVS J0002034+535901,2461215.8304,12.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
NSVS J0002034+535901 20260624.3304 12.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 06 24.3304 2461215.8304 12.09 00:02:53.68 +53:25:40.8
115.65074 -8.75609 galactic Cas Second-epoch detections are separated by 6.6" and 8.9 pix
The object was found in VSX11" Gaia DR3 396250560296237568
Type: ROT
# Max. Min./Amp. JD0 Period
17.460 G 17.610 G 0.617510000000 M
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:53.68 +53:25:40.8: 14.91 +/- 0.16 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:53.68 +53:25:40.8: 14.62 +/- 0.12 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 06 24.3304* 00 02 53.68 +53 25 40.8 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 396250560296237568,2461215.8304,12.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 396250560296237568 20260624.3304 12.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 12.07 00:18:51.66 +53:23:47.0
118.02347 -9.16460 galactic Cas Second-epoch detections are separated by 2.3" and 8.8 pix
The object was found in VSX20" Gaia DR3 419288730503843840
Type: S
# Max. Min./Amp. JD0 Period
18.070 G 19.980 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 00:18:51.66 +53:23:47.0: 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:18:51.66 +53:23:47.0: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 00 18 51.66 +53 23 47.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
Gaia DR3 419288730503843840,2461215.8304,12.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 419288730503843840 20260624.3304 12.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 12.10 00:07:59.03 +52:54:52.8
116.31708 -9.39807 galactic Cas Second-epoch detections are separated by 3.5" and 9.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:07:59.03 +52:54:52.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:07:59.03 +52:54:52.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:07:59.03 +52:54:52.8: 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 06 24.3304* 00 07 59.03 +52 54 52.8 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,2461215.8304,12.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 20260624.3304 12.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 06 24.3304 2461215.8304 7.62 23:58:26.85 +51:26:16.7
114.57633 -10.57204 galactic Cas Second-epoch detections are separated by 4.4" and 9.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:26.85 +51:26:16.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:58:26.85 +51:26:16.7: 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:58:26.85 +51:26:16.7: 15.50 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.50 +/- 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 06 24.3304* 23 58 26.85 +51 26 16.7 7.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,2461215.8304,7.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 20260624.3304 7.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 06 24.3304 2461215.8304 14.63 23:40:10.84 +53:34:46.8
112.36751 -7.82413 galactic Cas Second-epoch detections are separated by 3.1" and 9.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:40:10.84 +53:34:46.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:40:10.84 +53:34:46.8: 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:40:10.84 +53:34:46.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 06 24.3304* 23 40 10.84 +53 34 46.8 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,2461215.8304,14.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.74 23:36:06.73 +56:16:10.0
112.56535 -5.07868 galactic Cas Second-epoch detections are separated by 4.0" and 9.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:36:06.73 +56:16:10.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:36:06.73 +56:16:10.0: 15.66 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:36:06.73 +56:16:10.0: 15.82 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.66 +/- 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 06 24.3304* 23 36 06.73 +56 16 10.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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.61 23:41:15.06 +56:15:32.9
113.25043 -5.28760 galactic Cas Second-epoch detections are separated by 2.9" and 8.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:41:15.06 +56:15:32.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:41:15.06 +56:15:32.9: 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:41:15.06 +56:15:32.9: 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 06 24.3304* 23 41 15.06 +56 15 32.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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.57 23:33:42.08 +56:14:35.8
112.23630 -5.00566 galactic Cas Second-epoch detections are separated by 4.3" and 8.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:33:42.08 +56:14:35.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:33:42.08 +56:14:35.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:33:42.08 +56:14:35.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 06 24.3304* 23 33 42.08 +56 14 35.8 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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.40 23:43:06.00 +52:01:14.3
112.37159 -9.44437 galactic Cas Second-epoch detections are separated by 5.8" and 8.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:43:06.00 +52:01:14.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:43:06.00 +52:01:14.3: 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:43:06.00 +52:01:14.3: 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 06 24.3304* 23 43 06.00 +52 01 14.3 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,2461215.8304,14.40,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 20260624.3304 14.40CV 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 06 24.3304 2461215.8304 14.62 23:35:58.13 +53:28:50.4
111.73334 -7.74218 galactic Cas Second-epoch detections are separated by 3.0" and 9.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:35:58.13 +53:28:50.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:35:58.13 +53:28:50.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:58.13 +53:28:50.4: 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 06 24.3304* 23 35 58.13 +53 28 50.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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 14.47 23:32:22.01 +56:57:40.9
112.27632 -4.26555 galactic Cas Second-epoch detections are separated by 3.0" and 9.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:32:22.01 +56:57:40.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:22.01 +56:57:40.9: 15.41 +/- 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:22.01 +56:57:40.9: 15.37 +/- 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 06 24.3304* 23 32 22.01 +56 57 40.9 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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.29 23:38:19.66 +50:33:19.2
111.23440 -10.64848 galactic And Second-epoch detections are separated by 8.8" and 9.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:38:19.66 +50:33:19.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:38:19.66 +50:33:19.2: 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 23:38:19.66 +50:33:19.2: 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 06 24.3304* 23 38 19.66 +50 33 19.2 14.3 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,2461215.8304,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.21 23:35:02.95 +55:49:49.2
112.29465 -5.45576 galactic Cas Second-epoch detections are separated by 3.9" and 9.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:35:02.95 +55:49:49.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:35:02.95 +55:49:49.2: 15.63 +/- 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:02.95 +55:49:49.2: 15.66 +/- 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 06 24.3304* 23 35 02.95 +55 49 49.2 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.74 00:28:30.15 +51:38:26.4
119.30971 -11.06970 galactic Cas Second-epoch detections are separated by 7.7" and 8.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:30.15 +51:38:26.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:28:30.15 +51:38:26.4: 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:28:30.15 +51:38:26.4: 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 06 24.3304* 00 28 30.15 +51 38 26.4 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 14.14 23:42:28.80 +53:37:20.5
112.71066 -7.87531 galactic Cas Second-epoch detections are separated by 3.7" and 9.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:42:28.80 +53:37:20.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:42:28.80 +53:37:20.5: 15.63 +/- 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:28.80 +53:37:20.5: 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 06 24.3304* 23 42 28.80 +53 37 20.5 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,14.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.19 23:33:30.65 +56:13:29.9
112.20547 -5.01526 galactic Cas Second-epoch detections are separated by 3.9" and 9.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:33:30.65 +56:13:29.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:33:30.65 +56:13:29.9: 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 23:33:30.65 +56:13:29.9: 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 06 24.3304* 23 33 30.65 +56 13 29.9 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,2461215.8304,14.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
target 20260624.3304 14.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 06 24.3304 2461215.8304 13.86 00:22:53.72 +52:49:47.9
118.56392 -9.79954 galactic Cas Second-epoch detections are separated by 8.7" and 8.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:22:53.72 +52:49:47.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:22:53.72 +52:49:47.9: 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:22:53.72 +52:49:47.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 06 24.3304* 00 22 53.72 +52 49 47.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.86 23:43:27.06 +52:27:01.4
112.53916 -9.04409 galactic Cas Second-epoch detections are separated by 1.4" and 9.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 1944978693076177792 | 23:43:30.16 +52:27:34.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:43:27.06 +52:27:01.4: 15.58 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:27.06 +52:27:01.4: 15.33 +/- 0.26 detection
Forced photometry reference-image weighted average: 15.43 +/- 0.20
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 06 24.3304* 23 43 27.06 +52 27 01.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1944978693076177792,2461215.8304,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
Gaia DR3 1944978693076177792 20260624.3304 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 06 24.3304 2461215.8304 13.74 00:22:23.83 +51:17:43.7
118.30946 -11.31544 galactic Cas Second-epoch detections are separated by 8.1" and 8.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 394865549300345984 | 00:22:28.07 +51:17:39.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:22:23.83 +51:17:43.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:22:23.83 +51:17:43.7: 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 06 24.3304* 00 22 23.83 +51 17 43.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
Gaia DR3 394865549300345984,2461215.8304,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
Gaia DR3 394865549300345984 20260624.3304 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 06 24.3304 2461215.8304 13.98 23:37:26.49 +55:33:35.8
112.54070 -5.81181 galactic Cas Second-epoch detections are separated by 4.1" and 9.0 pix
The object was found in VSX25" Gaia DR3 1997511297066481664
Type: ROT
# Max. Min./Amp. JD0 Period
15.910 G 15.940 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:37:26.49 +55:33:35.8: 15.12 +/- 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:37:26.49 +55:33:35.8: 15.15 +/- 0.20 detection
Forced photometry reference-image weighted average: 15.14 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 37 26.49 +55 33 35.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
Gaia DR3 1997511297066481664,2461215.8304,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
Gaia DR3 1997511297066481664 20260624.3304 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 06 24.3304 2461215.8304 13.93 23:42:54.61 +53:06:01.8
112.63313 -8.39547 galactic Cas Second-epoch detections are separated by 4.2" and 9.0 pix
The object was found in VSX16" Gaia DR3 1993097204558103040
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.480 G 13.510 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 23:42:54.61 +53:06:01.8: 15.12 +/- 0.18 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:42:54.61 +53:06:01.8: 14.90 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.99 +/- 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 06 24.3304* 23 42 54.61 +53 06 01.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
Gaia DR3 1993097204558103040,2461215.8304,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993097204558103040 20260624.3304 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 13.74 23:37:32.63 +51:50:44.1
111.48818 -9.37672 galactic Cas Second-epoch detections are separated by 8.0" and 9.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:37:32.63 +51:50:44.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:37:32.63 +51:50:44.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 23:37:32.63 +51:50:44.1: 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 06 24.3304* 23 37 32.63 +51 50 44.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
target,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 12.59 23:58:48.31 +53:26:35.2
115.04972 -8.62122 galactic Cas Second-epoch detections are separated by 8.7" and 9.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:58:48.31 +53:26:35.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:58:48.31 +53:26:35.2: 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:58:48.31 +53:26:35.2: 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 06 24.3304* 23 58 48.31 +53 26 35.2 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,2461215.8304,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
target 20260624.3304 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 06 24.3304 2461215.8304 12.04 23:43:35.72 +53:16:14.1
112.77852 -8.25847 galactic Cas Second-epoch detections are separated by 3.1" and 9.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:43:35.72 +53:16:14.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:43:35.72 +53:16:14.1: 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:43:35.72 +53:16:14.1: 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 06 24.3304* 23 43 35.72 +53 16 14.1 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,2461215.8304,12.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 20260624.3304 12.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 06 24.3304 2461215.8304 12.74 23:31:40.38 +57:27:20.8
112.33676 -3.76591 galactic Cas Second-epoch detections are separated by 2.6" and 9.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 1998859607561085696 | 23:31:43.20 +57:26:57.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G0 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:31:40.38 +57:27:20.8: 15.42 +/- 0.27 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:31:40.38 +57:27:20.8: 15.66 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.51 +/- 0.21
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 06 24.3304* 23 31 40.38 +57 27 20.8 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
Gaia DR3 1998859607561085696,2461215.8304,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
Gaia DR3 1998859607561085696 20260624.3304 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 06 24.3304 2461215.8304 12.82 23:29:16.91 +55:18:50.1
111.35687 -5.70071 galactic Cas Second-epoch detections are separated by 5.1" and 9.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 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:16.91 +55:18:50.1: 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:29:16.91 +55:18:50.1: 15.50 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.50 +/- 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 06 24.3304* 23 29 16.91 +55 18 50.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
Gaia DR3 1997633755177085440,2461215.8304,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
Gaia DR3 1997633755177085440 20260624.3304 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 06 24.3304 2461215.8304 13.32 23:32:06.54 +57:45:11.4
112.48291 -3.50025 galactic Cas Second-epoch detections are separated by 4.3" and 9.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:06.54 +57:45:11.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:32:06.54 +57:45:11.4: 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:32:06.54 +57:45:11.4: 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 06 24.3304* 23 32 06.54 +57 45 11.4 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 13.27 23:35:02.39 +56:30:46.6
112.49378 -4.80259 galactic Cas Second-epoch detections are separated by 3.9" and 9.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:35:02.39 +56:30:46.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:35:02.39 +56:30:46.6: 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 23:35:02.39 +56:30:46.6: 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 06 24.3304* 23 35 02.39 +56 30 46.6 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,13.27,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 20260624.3304 13.27CV 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 06 24.3304 2461215.8304 13.26 23:31:59.31 +55:07:39.8
111.66807 -5.99703 galactic Cas Second-epoch detections are separated by 8.3" and 9.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 1997431032719635200 | 23:32:02.67 +55:07:46.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:31:59.31 +55:07:39.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 23:31:59.31 +55:07:39.8: 15.53 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.53 +/- 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 06 24.3304* 23 31 59.31 +55 07 39.8 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
Gaia DR3 1997431032719635200,2461215.8304,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
Gaia DR3 1997431032719635200 20260624.3304 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 06 24.3304 2461215.8304 13.26 23:47:34.99 +52:37:51.9
113.20098 -9.03003 galactic Cas Second-epoch detections are separated by 4.1" and 9.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:34.99 +52:37:51.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:47:34.99 +52:37:51.9: 15.94 +/- 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:34.99 +52:37:51.9: 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 06 24.3304* 23 47 34.99 +52 37 51.9 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,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
target 20260624.3304 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 06 24.3304 2461215.8304 13.09 00:23:23.05 +55:49:17.4
118.97051 -6.83432 galactic Cas Second-epoch detections are separated by 2.9" and 8.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 | ATO J005.8518+55.8256 | 00:23:23.05 +55:49:17.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:23:23.05 +55:49:17.4: 14.40 +/- 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:23.05 +55:49:17.4: 14.57 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.47 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 00 23 23.05 +55 49 17.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
ATO J005.8518+55.8256,2461215.8304,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.8518+55.8256 20260624.3304 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 13.39 23:33:32.89 +50:54:47.0
110.60570 -10.08509 galactic Cas Second-epoch detections are separated by 2.5" and 9.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:33:32.89 +50:54:47.0 (user input) | T | P | (position from user input) J-Ks=0.495+/-0.189 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:32.89 +50:54:47.0: 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:33:32.89 +50:54:47.0: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 33 32.89 +50 54 47.0 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.34 23:43:35.64 +50:08:35.6
111.94210 -11.27528 galactic Cas Second-epoch detections are separated by 7.5" and 9.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 J355.9043+50.1468 | 23:43:37.53 +50:09:00.0 (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:43:35.64 +50:08:35.6: 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:43:35.64 +50:08:35.6: 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 06 24.3304* 23 43 35.64 +50 08 35.6 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 J355.9043+50.1468,2461215.8304,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 J355.9043+50.1468 20260624.3304 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 06 24.3304 2461215.8304 13.43 23:38:55.08 +51:35:15.9
111.62106 -9.68430 galactic Cas Second-epoch detections are separated by 8.0" and 9.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:38:55.08 +51:35:15.9 (user input) | T | P | (position from user input) J-Ks=0.401+/-0.042 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:38:55.08 +51:35:15.9: 15.18 +/- 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:38:55.08 +51:35:15.9: 14.79 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.91 +/- 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 06 24.3304* 23 38 55.08 +51 35 15.9 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.43 00:05:01.07 +51:13:17.4
115.55809 -10.98443 galactic Cas Second-epoch detections are separated by 4.9" and 9.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.2384+51.2194 | 00:05:01.07 +51:13:17.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:05:01.07 +51:13:17.4: 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:05:01.07 +51:13:17.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 06 24.3304* 00 05 01.07 +51 13 17.4 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
ATO J001.2384+51.2194,2461215.8304,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
ATO J001.2384+51.2194 20260624.3304 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 06 24.3304 2461215.8304 13.68 23:36:56.67 +55:34:18.8
112.47642 -5.78035 galactic Cas Second-epoch detections are separated by 4.5" and 9.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:36:56.67 +55:34:18.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:36:56.67 +55:34:18.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 23:36:56.67 +55:34:18.8: 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 06 24.3304* 23 36 56.67 +55 34 18.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,2461215.8304,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
target 20260624.3304 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 06 24.3304 2461215.8304 13.79 23:33:32.06 +56:43:59.2
112.36043 -4.53115 galactic Cas Second-epoch detections are separated by 2.3" and 9.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:33:32.06 +56:43:59.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:33:32.06 +56:43:59.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:33:32.06 +56:43:59.2: 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 06 24.3304* 23 33 32.06 +56 43 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
target,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.56 00:27:52.66 +52:58:19.2
119.33704 -9.73522 galactic Cas Second-epoch detections are separated by 8.0" and 8.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:27:52.66 +52:58:19.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:27:52.66 +52:58:19.2: 14.79 +/- 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:27:52.66 +52:58:19.2: 14.64 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.72 +/- 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 06 24.3304* 00 27 52.66 +52 58 19.2 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,2461215.8304,13.56,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 20260624.3304 13.56CV 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 06 24.3304 2461215.8304 13.85 23:44:09.71 +53:03:31.9
112.80543 -8.48503 galactic Cas Second-epoch detections are separated by 3.2" and 9.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:44:09.71 +53:03:31.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:44:09.71 +53:03:31.9: 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:44:09.71 +53:03:31.9: 15.62 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.62 +/- 0.28
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 44 09.71 +53 03 31.9 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,2461215.8304,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 13.81 23:43:26.63 +51:45:07.9
112.35147 -9.71728 galactic Cas Second-epoch detections are separated by 7.7" and 9.3 pix
The object was found in VSX 5" Gaia DR3 1944888739280134016
Type:
# Max. Min./Amp. JD0 Period
15.710 G 15.760 G 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 23:43:26.63 +51:45:07.9: 15.37 +/- 0.22 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:26.63 +51:45:07.9: 15.39 +/- 0.22 detection
Forced photometry reference-image weighted average: 15.38 +/- 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 06 24.3304* 23 43 26.63 +51 45 07.9 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 1944888739280134016,2461215.8304,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 1944888739280134016 20260624.3304 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 06 24.3304 2461215.8304 13.64 00:22:44.08 +56:26:51.3
118.94971 -6.20207 galactic Cas Second-epoch detections are separated by 8.2" and 8.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:22:44.08 +56:26: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 00:22:44.08 +56:26:51.3: 14.91 +/- 0.20 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.08 +56:26:51.3: 14.88 +/- 0.20 detection
Forced photometry reference-image weighted average: 14.90 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 00 22 44.08 +56 26 51.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,2461215.8304,13.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 20260624.3304 13.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 06 24.3304 2461215.8304 13.79 23:57:05.80 +52:12:20.7
114.53263 -9.77756 galactic Cas Second-epoch detections are separated by 6.4" and 8.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:57:05.80 +52:12:20.7 (user input) | T | P | (position from user input) J-Ks=0.682+/-0.245 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:57:05.80 +52:12:20.7: 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 23:57:05.80 +52:12:20.7: 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 06 24.3304* 23 57 05.80 +52 12 20.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.63 00:19:46.79 +51:04:48.3
117.86777 -11.48011 galactic Cas Second-epoch detections are separated by 8.8" and 8.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:19:46.79 +51:04: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:19:46.79 +51:04:48.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 00:19:46.79 +51:04:48.3: 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 06 24.3304* 00 19 46.79 +51 04 48.3 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,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
target 20260624.3304 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 06 24.3304 2461215.8304 13.90 23:32:12.99 +55:32:45.4
111.82671 -5.60838 galactic Cas Second-epoch detections are separated by 7.4" and 9.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:12.99 +55:32:45.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:32:12.99 +55:32:45.4: 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.99 +55:32:45.4: 15.59 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 32 12.99 +55 32 45.4 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 14.01 23:35:17.11 +55:37:18.2
112.26535 -5.66497 galactic Cas Second-epoch detections are separated by 4.8" and 9.2 pix
The object was found in VSX25" Gaia DR3 1997480373305143680
Type:
# Max. Min./Amp. JD0 Period
16.620 G 17.400 G F
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:35:17.11 +55:37:18.2: 15.45 +/- 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:17.11 +55:37:18.2: 15.44 +/- 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 06 24.3304* 23 35 17.11 +55 37 18.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
Gaia DR3 1997480373305143680,2461215.8304,14.01,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 1997480373305143680 20260624.3304 14.01CV 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 06 24.3304 2461215.8304 13.85 00:01:19.02 +51:15:17.9
114.98532 -10.84180 galactic Cas Second-epoch detections are separated by 3.5" and 8.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:01:19.02 +51:15:17.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:01:19.02 +51:15:17.9: 15.96 +/- 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:01:19.02 +51:15:17.9: 15.99 +/- 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 06 24.3304* 00 01 19.02 +51 15 17.9 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,2461215.8304,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 13.94 23:29:08.74 +56:37:28.9
111.75157 -4.45013 galactic Cas Second-epoch detections are separated by 4.0" and 9.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:08.74 +56:37:28.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:29:08.74 +56:37:28.9: 15.40 +/- 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:08.74 +56:37:28.9: 15.45 +/- 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 06 24.3304* 23 29 08.74 +56 37 28.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8304,13.94,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 20260624.3304 13.94CV 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 06 24.3304 2461215.8304 13.79 00:27:16.95 +54:05:39.3
119.35435 -8.60962 galactic Cas Second-epoch detections are separated by 7.2" and 9.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.95 +54:05:39.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:27:16.95 +54:05:39.3: 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.95 +54:05:39.3: 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 06 24.3304* 00 27 16.95 +54 05 39.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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 13.93 00:06:21.20 +52:40:38.1
116.02926 -9.58921 galactic Cas Second-epoch detections are separated by 5.7" and 8.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:06:21.20 +52:40: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 00:06:21.20 +52:40:38.1: 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:06:21.20 +52:40:38.1: 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 06 24.3304* 00 06 21.20 +52 40 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,2461215.8304,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 13.96 23:56:27.04 +53:44:46.4
114.76851 -8.25171 galactic Cas Second-epoch detections are separated by 5.0" and 9.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 J359.1089+53.7337 | 23:56:27.04 +53:44: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:56:27.04 +53:44:46.4: 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:56:27.04 +53:44:46.4: 15.61 +/- 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 06 24.3304* 23 56 27.04 +53 44 46.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J359.1089+53.7337,2461215.8304,13.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
ATO J359.1089+53.7337 20260624.3304 13.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
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.16 23:37:38.39 +56:52:47.2
112.94254 -4.55381 galactic Cas Second-epoch detections are separated by 1.0" and 9.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:37:38.39 +56:52:47.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:37:38.39 +56:52:47.2: 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 23:37:38.39 +56:52:47.2: 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 06 24.3304* 23 37 38.39 +56 52 47.2 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,2461215.8304,14.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
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.17 23:32:42.99 +56:50:33.3
112.28609 -4.39319 galactic Cas Second-epoch detections are separated by 6.7" and 9.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:32:42.99 +56:50:33.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:32:42.99 +56:50:33.3: 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:42.99 +56:50:33.3: 15.54 +/- 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 06 24.3304* 23 32 42.99 +56 50 33.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
target,2461215.8304,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.31 23:30:55.98 +51:08:07.2
110.27732 -9.74763 galactic Cas Second-epoch detections are separated by 0.3" and 9.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:30:55.98 +51:08:07.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:30:55.98 +51:08:07.2: 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:30:55.98 +51:08:07.2: 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 06 24.3304* 23 30 55.98 +51 08 07.2 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,2461215.8304,14.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
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.15 23:48:03.24 +51:53:54.3
113.08814 -9.75776 galactic Cas Second-epoch detections are separated by 7.7" and 9.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:48:03.24 +51:53:54.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:03.24 +51:53:54.3: 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 23:48:03.24 +51:53:54.3: 15.63 +/- 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 06 24.3304* 23 48 03.24 +51 53 54.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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.14 00:08:30.18 +51:27:23.6
116.14585 -10.84859 galactic Cas Second-epoch detections are separated by 6.5" and 9.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 J002.1354+51.4626 | 00:08:30.18 +51:27:23.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 00:08:30.18 +51:27:23.6: 15.96 +/- 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:08:30.18 +51:27:23.6: 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 06 24.3304* 00 08 30.18 +51 27 23.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
ATO J002.1354+51.4626,2461215.8304,14.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.1354+51.4626 20260624.3304 14.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.55 23:32:13.79 +56:56:26.7
112.25222 -4.27955 galactic Cas Second-epoch detections are separated by 4.3" and 8.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:13.79 +56:56: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:13.79 +56:56:26.7: 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:32:13.79 +56:56:26.7: 15.46 +/- 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 06 24.3304* 23 32 13.79 +56 56 26.7 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,2461215.8304,14.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
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.48 23:29:45.27 +56:06:24.2
111.66941 -4.96849 galactic Cas Second-epoch detections are separated by 4.6" and 8.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 J352.4287+56.1147 | 23:29:45.27 +56:06:24.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 23:29:45.27 +56:06:24.2: 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:29:45.27 +56:06:24.2: 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 06 24.3304* 23 29 45.27 +56 06 24.2 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
ATO J352.4287+56.1147,2461215.8304,14.48,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 J352.4287+56.1147 20260624.3304 14.48CV 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 06 24.3304 2461215.8304 14.46 23:32:08.30 +53:57:16.0
111.32975 -7.12135 galactic Cas Second-epoch detections are separated by 5.3" and 9.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:32:08.30 +53:57:16.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:32:08.30 +53:57:16.0: 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:32:08.30 +53:57:16.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 06 24.3304* 23 32 08.30 +53 57 16.0 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,2461215.8304,14.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.62 23:31:13.09 +57:29:23.6
112.28883 -3.71478 galactic Cas Second-epoch detections are separated by 3.6" and 8.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 | ZTF J233107.24+572947.2 | 23:31:09.14 +57:29:28.1 (Gaia DR3) | BY (local) | 2458380.82990 (local) | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:31:13.09 +57:29:23.6: 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:31:13.09 +57:29:23.6: 15.72 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.72 +/- 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 06 24.3304* 23 31 13.09 +57 29 23.6 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
ZTF J233107.24+572947.2,2461215.8304,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
ZTF J233107.24+572947.2 20260624.3304 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 06 24.3304 2461215.8304 14.69 23:30:57.09 +50:50:58.9
110.19001 -10.02003 galactic Cas Second-epoch detections are separated by 4.1" and 9.4 pix
The object was found in VSX20" Gaia DR3 1943282627667931008
Type: ROT
# Max. Min./Amp. JD0 Period
15.470 G 15.520 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:30:57.09 +50:50:58.9: 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:30:57.09 +50:50:58.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 06 24.3304* 23 30 57.09 +50 50 58.9 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 1943282627667931008,2461215.8304,14.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
Gaia DR3 1943282627667931008 20260624.3304 14.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 06 24.3304 2461215.8304 14.46 23:32:32.78 +50:43:05.5
110.39247 -10.22279 galactic Cas Second-epoch detections are separated by 8.8" and 9.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 1943228133123051136 | 23:32:29.63 +50:43:30.4 (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:32:32.78 +50:43:05.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 23:32:32.78 +50:43:05.5: 15.65 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 32 32.78 +50 43 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
Gaia DR3 1943228133123051136,2461215.8304,14.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1943228133123051136 20260624.3304 14.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3304 2461215.8304 14.74 23:30:04.58 +56:12:42.1
111.74492 -4.88267 galactic Cas Second-epoch detections are separated by 4.7" and 9.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:30:04.58 +56:12:42.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:30:04.58 +56:12:42.1: 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 23:30:04.58 +56:12:42.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 06 24.3304* 23 30 04.58 +56 12 42.1 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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.63 23:31:19.55 +50:23:15.9
110.10164 -10.47758 galactic And Second-epoch detections are separated by 6.3" and 9.1 pix
The object was found in VSX24" ZTF J233120.15+502253.1
Type: EW
# Max. Min./Amp. JD0 Period
19.478 r Y 0.498 r 2458456.65790 0.323717400000
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:31:19.55 +50:23:15.9: 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 23:31:19.55 +50:23:15.9: 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 06 24.3304* 23 31 19.55 +50 23 15.9 14.6 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
ZTF J233120.15+502253.1,2461215.8304,14.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J233120.15+502253.1 20260624.3304 14.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 06 24.3304 2461215.8304 14.47 23:36:42.72 +53:33:03.3
111.86055 -7.70686 galactic Cas Second-epoch detections are separated by 1.6" and 9.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:36:42.72 +53:33: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:36:42.72 +53:33: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:36:42.72 +53:33:03.3: 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 06 24.3304* 23 36 42.72 +53 33 03.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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.61 23:32:25.41 +55:22:16.4
111.80167 -5.78379 galactic Cas Second-epoch detections are separated by 2.5" and 9.1 pix
The object was found in VSX25" Gaia DR3 1997450239813241728
Type: ROT
# Max. Min./Amp. JD0 Period
16.970 G 17.050 G 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 23:32:25.41 +55:22:16.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:32:25.41 +55:22:16.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 06 24.3304* 23 32 25.41 +55 22 16.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 1997450239813241728,2461215.8304,14.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
Gaia DR3 1997450239813241728 20260624.3304 14.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 06 24.3304 2461215.8304 14.62 23:29:18.55 +55:17:00.3
111.35097 -5.73089 galactic Cas Second-epoch detections are separated by 7.1" and 9.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:29:18.55 +55:17:00.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:29:18.55 +55:17:00.3: 15.57 +/- 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:18.55 +55:17:00.3: 15.56 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 29 18.55 +55 17 00.3 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 14.62 23:31:22.28 +54:31:58.3
111.40021 -6.53635 galactic Cas Second-epoch detections are separated by 6.3" and 9.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:31:22.28 +54:31:58.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:31:22.28 +54:31:58.3: 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 23:31:22.28 +54:31:58.3: 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 06 24.3304* 23 31 22.28 +54 31 58.3 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 14.84 23:33:49.78 +57:33:02.7
112.64224 -3.76229 galactic Cas Second-epoch detections are separated by 4.3" and 8.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:33:49.78 +57:33:02.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:33:49.78 +57:33:02.7: 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:49.78 +57:33:02.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 06 24.3304* 23 33 49.78 +57 33 02.7 14.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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.61 23:31:14.89 +51:41:33.5
110.49980 -9.23299 galactic Cas Second-epoch detections are separated by 8.3" and 9.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:31:14.89 +51:41: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 23:31:14.89 +51:41:33.5: 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:31:14.89 +51:41:33.5: 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 06 24.3304* 23 31 14.89 +51 41 33.5 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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.63 23:31:51.39 +51:36:15.2
110.56317 -9.34618 galactic Cas Second-epoch detections are separated by 6.2" and 8.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 J352.9701+51.6121 | 23:31:51.39 +51:36:15.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 23:31:51.39 +51:36:15.2: 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:31:51.39 +51:36:15.2: 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 06 24.3304* 23 31 51.39 +51 36 15.2 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
ATO J352.9701+51.6121,2461215.8304,14.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 J352.9701+51.6121 20260624.3304 14.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 06 24.3304 2461215.8304 14.45 00:05:47.98 +53:57:46.7
116.17748 -8.30918 galactic Cas Second-epoch detections are separated by 7.3" and 8.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:05:47.98 +53:57:46.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:05:47.98 +53:57:46.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 00:05:47.98 +53:57:46.7: 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 06 24.3304* 00 05 47.98 +53 57 46.7 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,2461215.8304,14.45,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 20260624.3304 14.45CV 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 06 24.3304 2461215.8304 14.60 23:33:33.34 +55:13:44.8
111.91327 -5.96773 galactic Cas Second-epoch detections are separated by 6.5" and 9.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:33:33.34 +55:13:44.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:33:33.34 +55:13:44.8: 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:33:33.34 +55:13:44.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 06 24.3304* 23 33 33.34 +55 13 44.8 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,2461215.8304,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 20260624.3304 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 06 24.3304 2461215.8304 14.73 23:31:19.52 +57:10:23.0
112.20556 -4.02086 galactic Cas Second-epoch detections are separated by 4.1" and 8.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:31:19.52 +57:10:23.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:31:19.52 +57:10:23.0: 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:31:19.52 +57:10:23.0: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 31 19.52 +57 10 23.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
target,2461215.8304,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
target 20260624.3304 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 06 24.3304 2461215.8304 14.67 23:39:23.46 +56:29:07.7
113.06369 -4.99960 galactic Cas Second-epoch detections are separated by 0.9" and 8.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:39:23.46 +56:29:07.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:39:23.46 +56:29:07.7: 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 23:39:23.46 +56:29:07.7: 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 06 24.3304* 23 39 23.46 +56 29 07.7 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
target,2461215.8304,14.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.72 23:32:52.38 +55:31:51.8
111.91117 -5.65060 galactic Cas Second-epoch detections are separated by 2.8" and 8.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:52.38 +55:31:51.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:32:52.38 +55:31:51.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:32:52.38 +55:31:51.8: 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 06 24.3304* 23 32 52.38 +55 31 51.8 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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.70 23:36:37.82 +55:28:14.6
112.40449 -5.86456 galactic Cas Second-epoch detections are separated by 4.8" and 9.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:36:37.82 +55:28:14.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:36:37.82 +55:28:14.6: 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:36:37.82 +55:28:14.6: 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 06 24.3304* 23 36 37.82 +55 28 14.6 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
target,2461215.8304,14.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
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.80 23:29:23.63 +56:53:27.5
111.86759 -4.20790 galactic Cas Second-epoch detections are separated by 3.0" and 9.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 J352.3636+56.8997 | 23:29:23.63 +56:53:27.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:29:23.63 +56:53:27.5: 15.53 +/- 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:23.63 +56:53:27.5: 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 06 24.3304* 23 29 23.63 +56 53 27.5 14.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 J352.3636+56.8997,2461215.8304,14.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
ATO J352.3636+56.8997 20260624.3304 14.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 06 24.3304 2461215.8304 14.69 23:40:23.01 +53:45:30.1
112.44615 -7.66053 galactic Cas Second-epoch detections are separated by 4.6" and 8.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 J355.1070+53.7538 | 23:40:23.01 +53:45:30.1 (user input) | LPV (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:40:23.01 +53:45:30.1: 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 23:40:23.01 +53:45:30.1: 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 06 24.3304* 23 40 23.01 +53 45 30.1 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
ATO J355.1070+53.7538,2461215.8304,14.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 J355.1070+53.7538 20260624.3304 14.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 06 24.3304 2461215.8304 14.88 23:34:20.01 +55:18:49.2
112.04487 -5.91986 galactic Cas Second-epoch detections are separated by 4.4" and 9.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:20.01 +55:18:49.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:34:20.01 +55:18:49.2: 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:34:20.01 +55:18:49.2: 15.77 +/- 0.36 detection
Forced photometry reference-image weighted average: 15.77 +/- 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 06 24.3304* 23 34 20.01 +55 18 49.2 14.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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.71 23:35:13.50 +50:52:41.8
110.85154 -10.19715 galactic Cas Second-epoch detections are separated by 0.9" and 9.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:35:13.50 +50:52:41.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:35:13.50 +50:52:41.8: 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:35:13.50 +50:52:41.8: 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 06 24.3304* 23 35 13.50 +50 52 41.8 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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.66 23:45:59.31 +54:45:21.6
113.50701 -6.91364 galactic Cas Second-epoch detections are separated by 4.8" and 8.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:45:59.31 +54:45:21.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:45:59.31 +54:45:21.6: 15.53 +/- 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:59.31 +54:45:21.6: 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 06 24.3304* 23 45 59.31 +54 45 21.6 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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.75 23:31:14.33 +57:14:39.8
112.21624 -3.94936 galactic Cas Second-epoch detections are separated by 6.9" and 10.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:31:14.33 +57:14: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 23:31:14.33 +57:14:39.8: 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 23:31:14.33 +57:14:39.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 06 24.3304* 23 31 14.33 +57 14 39.8 14.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,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.75 23:31:38.41 +56:08:43.3
111.93227 -5.01273 galactic Cas Second-epoch detections are separated by 3.3" and 9.1 pix
The object was found in VSX 9" Gaia DR3 1997732470704339456
Type: E
# Max. Min./Amp. JD0 Period
18.210 G 18.400 G 1.070610000000
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:31:38.41 +56:08:43.3: 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:31:38.41 +56:08:43.3: 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 06 24.3304* 23 31 38.41 +56 08 43.3 14.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 1997732470704339456,2461215.8304,14.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
Gaia DR3 1997732470704339456 20260624.3304 14.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 06 24.3304 2461215.8304 14.66 23:31:44.80 +51:29:27.8
110.51147 -9.44862 galactic Cas Second-epoch detections are separated by 5.7" and 8.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:31:44.80 +51:29: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:31:44.80 +51:29:27.8: 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 23:31:44.80 +51:29:27.8: 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 06 24.3304* 23 31 44.80 +51 29 27.8 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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.63 23:33:00.05 +50:29:51.5
110.39404 -10.45482 galactic And Second-epoch detections are separated by 8.9" and 9.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:00.05 +50:29:51.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:33:00.05 +50:29:51.5: 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:33:00.05 +50:29:51.5: 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 06 24.3304* 23 33 00.05 +50 29 51.5 14.6 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,2461215.8304,14.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.80 23:37:01.99 +51:37:44.4
111.34841 -9.56153 galactic Cas Second-epoch detections are separated by 2.8" and 8.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:37:01.99 +51:37:44.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:37:01.99 +51:37:44.4: 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:37:01.99 +51:37:44.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 06 24.3304* 23 37 01.99 +51 37 44.4 14.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,2461215.8304,14.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
target 20260624.3304 14.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 06 24.3304 2461215.8304 14.66 23:43:30.06 +50:56:49.9
112.14420 -10.49604 galactic Cas Second-epoch detections are separated by 6.8" and 8.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:43:30.06 +50:56:49.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:43:30.06 +50:56:49.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:43:30.06 +50:56:49.9: 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 06 24.3304* 23 43 30.06 +50 56 49.9 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
target,2461215.8304,14.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 20260624.3304 14.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 06 24.3304 2461215.8304 14.69 00:06:31.80 +52:20:36.8
115.99647 -9.92242 galactic Cas Second-epoch detections are separated by 4.8" and 8.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:06:31.80 +52:20:36.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:06:31.80 +52:20:36.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 00:06:31.80 +52:20:36.8: 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 06 24.3304* 00 06 31.80 +52 20 36.8 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
target,2461215.8304,14.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 14.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 06 24.3304 2461215.8304 7.71 00:23:10.78 +55:47:35.0
118.93860 -6.85944 galactic Cas Second-epoch detections are separated by 4.7" and 8.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 | 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.78 +55:47:35.0: 10.06 +/- 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.78 +55:47:35.0: 10.08 +/- 0.01 detection
Forced photometry reference-image weighted average: 10.07 +/- 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 06 24.3304* 00 23 10.78 +55 47 35.0 7.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
T Cas,2461215.8304,7.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
T Cas 20260624.3304 7.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 06 24.3304 2461215.8304 12.16 00:02:02.19 +53:59:29.3
115.63342 -8.17874 galactic Cas Second-epoch detections are separated by 8.9" and 8.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 | NSVS J0002034+535901 | 00:02:03.89 +53:58:58.7 (Gaia DR3) | SR (local) | 2458357.13120 (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:02.19 +53:59:29.3: 14.83 +/- 0.13 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:02.19 +53:59:29.3: 14.88 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.86 +/- 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 06 24.3304* 00 02 02.19 +53 59 29.3 12.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
NSVS J0002034+535901,2461215.8304,12.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
NSVS J0002034+535901 20260624.3304 12.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 06 24.3304 2461215.8304 11.64 23:34:59.30 +50:35:48.5
110.73056 -10.45496 galactic And Second-epoch detections are separated by 8.6" and 9.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:34:59.30 +50:35:48.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:34:59.30 +50:35:48.5: 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:34:59.30 +50:35:48.5: 15.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3304* 23 34 59.30 +50 35 48.5 11.6 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,2461215.8304,11.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 20260624.3304 11.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 06 24.3304 2461215.8304 10.48 23:55:49.34 +53:44:23.7
114.67547 -8.23790 galactic Cas Second-epoch detections are separated by 4.0" and 8.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:55:49.34 +53:44:23.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:55:49.34 +53:44:23.7: 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:55:49.34 +53:44:23.7: 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 06 24.3304* 23 55 49.34 +53 44 23.7 10.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,2461215.8304,10.48,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 20260624.3304 10.48CV 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 06 24.3304 2461215.8304 10.59 23:38:16.13 +56:01:54.5
112.78658 -5.39194 galactic Cas Second-epoch detections are separated by 3.3" and 9.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:38:16.13 +56:01:54.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:38:16.13 +56:01:54.5: 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 23:38:16.13 +56:01:54.5: 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 06 24.3304* 23 38 16.13 +56 01 54.5 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,2461215.8304,10.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 20260624.3304 10.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 06 24.3304 2461215.8304 13.09 00:13:24.43 +52:37:43.0
117.09203 -9.81138 galactic Cas Second-epoch detections are separated by 6.6" and 8.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:24.43 +52:37: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:13:24.43 +52:37:43.0: 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 00:13:24.43 +52:37:43.0: 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 06 24.3304* 00 13 24.43 +52 37 43.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
target,2461215.8304,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3304 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## 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: 2461215.83067758 24.06.2026 07:56:00.543 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 66
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: 19 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): 26974
Objects passed selection criteria: 26893
Measurements per detected object (mean, median, min, max): 3.0 3.0 2 4
Measurements per selected object (mean, median, min, max): 3.0 3.0 2 4
Average stars detected per image: 21187.8
Average stars matched: 19035.8 (89.8432 %)
Memory usage VmPeak: 127964 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Jun 23 15:09:51 CDT 2026
VaST build number 1.0rc89-109-g76dded0d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-23)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed Jun 24 04:19:53 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: 2461215.83067758 24.06.2026 07:56:00.543 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 378
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: 693 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): 203198
Objects passed selection criteria: 202587
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: 156639
Average stars matched: 140271 (89.5508 %)
Memory usage VmPeak: 2390760 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Jun 23 15:09:51 CDT 2026
VaST build number 1.0rc89-109-g76dded0d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-23)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed Jun 24 05:12:38 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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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: 2461215.83007665
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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits'
wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
Image size: 926.8'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: 23:59:52.132 +54:01:55.33 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:52.132 +54:01:55.33
Angular distance between the image centers 0.0404 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-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
Image size: 926.8'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: 23:59:56.250 +54:01:16.61 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 23:59:56.250 +54:01:16.61
Angular distance between the image centers 0.0310 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:52.132 +54:01:55.33
Second-epoch second image center 23:59:56.250 +54:01:16.61
Angular distance between the image centers 0.01474 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits &> /tmp/tmp.GinrAJ3G6j
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.rAagVAEXYr
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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits &> /tmp/tmp.Atb5Xo8geB
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits &> /tmp/tmp.pXKY29Lgdj
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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 63 candidate transients before the final filtering. (Hard limit: 8000)
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.6 pix fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
2.6 pix fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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.8 mag. fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
14.8 mag. fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
All-image limiting magnitude estimate: 14.8 (SNR ) 12.0 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.GinrAJ3G6j (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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/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.rAagVAEXYr (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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/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.Atb5Xo8geB (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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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=2036, bad_region=4699, passed=25704
Got 25704 stars (including 19303 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat
util/solve_plate_with_UCAC5 got 25704 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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 344.9613 through 0 to 14.8802, gap 14.8802 to 344.9613
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 327 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 240 matched stars entering correct_measured_positions(), 161 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.19"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 230 matched stars entering correct_measured_positions(), 5457 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.80"
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 344.9479 through 0 to 14.9031, gap 14.9031 to 344.9479
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 411 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 340 matched stars entering correct_measured_positions(), 5517 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.75"
Accuracy estimation diagnostic: 336 matched stars entering correct_measured_positions(), 7687 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.15"
Excluding outliers - 336 stars left (next iteration limit 253)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits N_match=336 sigma_overall_arcsec=10.871 sigma_q1_arcsec=21.963 sigma_q2_arcsec=36.618 sigma_q3_arcsec=8.135 sigma_q4_arcsec=10.638 n_q1=33 n_q2=18 n_q3=124 n_q4=161 worst_quadrant_to_overall_ratio=3.369
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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.pXKY29Lgdj (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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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=2187, bad_region=4771, passed=25696
Got 25696 stars (including 19181 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat
util/solve_plate_with_UCAC5 got 25696 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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.0017 through 0 to 14.8807, gap 14.8807 to 345.0017
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 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: 232 matched stars entering correct_measured_positions(), 157 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.68"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 224 matched stars entering correct_measured_positions(), 5441 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.07"
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 344.9890 through 0 to 14.9047, gap 14.9047 to 344.9890
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 401 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(), 5494 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.98"
Accuracy estimation diagnostic: 321 matched stars entering correct_measured_positions(), 7401 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.93"
Excluding outliers - 321 stars left (next iteration limit 246)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits N_match=321 sigma_overall_arcsec=10.473 sigma_q1_arcsec=25.431 sigma_q2_arcsec=31.247 sigma_q3_arcsec=7.988 sigma_q4_arcsec=8.682 n_q1=34 n_q2=19 n_q3=122 n_q4=146 worst_quadrant_to_overall_ratio=2.983
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits sigma_overall=10.871 worst_q_ratio=3.369
new2=fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits sigma_overall=10.473 worst_q_ratio=2.983
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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits) flagged: sigma=10.871 (ref avg 0.495), ratio=3.369 (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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/lib/make_outxyls_for_astrometric_calibration found 24256 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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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: "out2682720.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2682720.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
log-odds ratio 28.336 (2.02372e+12), 8 match, 0 conflict, 7 distractors, 366 index.
RA,Dec = (0.0881403,53.9686), pixel scale 5.88081 arcsec/pix.
Hit/miss: Hit/miss: ----++++---++++(best)------------------------++-----++--------------------------++--+--+++----------------
Field 1: solved with index index-4112.fits.
Field 1 solved: writing to file ./out2682720.solved to indicate this.
Field: out2682720.xyls
Field center: (RA,Dec) = (0.089488, 53.969431) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:21.477, +53:58:09.953).
Field size: 15.3113 x 10.3004 degrees
Field rotation angle: up is 7.49772 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits' -> 'fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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 Jun 24 04:33 fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
-rw-r--r-- 1 apache apache 8.5K Jun 24 04:33 out2682720.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits (fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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: "out2682720.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2682720.axy"...
Only searching for solutions within 15.3283 degrees of RA,Dec (0.0908333,53.9703)
log-odds ratio 23.7402 (2.04277e+10), 8 match, 0 conflict, 21 distractors, 24 index.
RA,Dec = (359.964,54.0304), pixel scale 5.93189 arcsec/pix.
Hit/miss: Hit/miss: ----+-++-----++---+-----+---+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2682720.solved to indicate this.
Field: out2682720.xyls
Field center: (RA,Dec) = (359.965844, 54.031205) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:51.803, +54:01:52.339).
Field size: 15.6067 x 10.4343 degrees
Field rotation angle: up is 3.39113 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 Jun 24 04:33 fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
-rw-r--r-- 1 apache apache 8.5K Jun 24 04:33 out2682720.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 100000 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.axy"...
Verifying WCS using indices with quads of size [63.1548, 946.729] 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.1548, 946.729] 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).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
Image size: 926.8'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: 23:59:52.132 +54:01:55.33 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 25704 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/correct_sextractor_wcs_catalog_usingxy2sky3342762.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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=2036, bad_region=4699, passed=25704
Got 25704 stars (including 19303 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat
util/solve_plate_with_UCAC5 got 25704 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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 344.9613 through 0 to 14.8802, gap 14.8802 to 344.9613
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 327 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 240 matched stars entering correct_measured_positions(), 161 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.19"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 230 matched stars entering correct_measured_positions(), 5457 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.80"
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 344.9479 through 0 to 14.9031, gap 14.9031 to 344.9479
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 411 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 340 matched stars entering correct_measured_positions(), 5517 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.75"
Accuracy estimation diagnostic: 336 matched stars entering correct_measured_positions(), 7687 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.15"
Excluding outliers - 336 stars left (next iteration limit 253)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits N_match=336 sigma_overall_arcsec=10.871 sigma_q1_arcsec=21.963 sigma_q2_arcsec=36.618 sigma_q3_arcsec=8.135 sigma_q4_arcsec=10.638 n_q1=33 n_q2=18 n_q3=124 n_q4=161 worst_quadrant_to_overall_ratio=3.369
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits): sigma 10.871->10.871, ratio 3.369->3.369; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits) flagged: sigma=10.473 (ref avg 0.495), ratio=2.983 (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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/lib/make_outxyls_for_astrometric_calibration found 24326 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-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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: "out3343093.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3343093.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 23.5653 (1.715e+10), 8 match, 0 conflict, 21 distractors, 24 index.
RA,Dec = (359.982,54.0196), pixel scale 5.93177 arcsec/pix.
Hit/miss: Hit/miss: ----+++-------++--+-----+---+(best)-----------------------------------------------------------------------
fit-wcs.c:118:fit_sip_wcs: Too few correspondences for the SIP order specified (5 < 6)
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3343093.solved to indicate this.
Field: out3343093.xyls
Field center: (RA,Dec) = (359.983005, 54.020449) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:55.921, +54:01:13.617).
Field size: 15.6065 x 10.434 degrees
Field rotation angle: up is 3.38247 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits' -> 'fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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 Jun 24 04:44 fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
-rw-r--r-- 1 apache apache 8.5K Jun 24 04:44 out3343093.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits (fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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: "out3343093.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3343093.axy"...
Only searching for solutions within 15.4467 degrees of RA,Dec (359.984,54.0213)
log-odds ratio 23.5653 (1.715e+10), 8 match, 0 conflict, 21 distractors, 24 index.
RA,Dec = (359.982,54.0196), pixel scale 5.93177 arcsec/pix.
Hit/miss: Hit/miss: ----+++-------++--+-----+---+(best)-----------------------------------------------------------------------
fit-wcs.c:118:fit_sip_wcs: Too few correspondences for the SIP order specified (5 < 6)
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3343093.solved to indicate this.
Field: out3343093.xyls
Field center: (RA,Dec) = (359.983005, 54.020449) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:55.921, +54:01:13.617).
Field size: 15.6065 x 10.434 degrees
Field rotation angle: up is 3.38247 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 Jun 24 04:44 fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
-rw-r--r-- 1 apache apache 8.5K Jun 24 04:44 out3343093.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 100000 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.axy"...
Verifying WCS using indices with quads of size [63.1536, 946.71] 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.1536, 946.71] 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).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
Image size: 926.8'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: 23:59:56.250 +54:01:16.61 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 25696 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/correct_sextractor_wcs_catalog_usingxy2sky409431.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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=2187, bad_region=4771, passed=25696
Got 25696 stars (including 19181 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat
util/solve_plate_with_UCAC5 got 25696 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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.0017 through 0 to 14.8807, gap 14.8807 to 345.0017
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 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: 232 matched stars entering correct_measured_positions(), 157 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.68"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 224 matched stars entering correct_measured_positions(), 5441 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.07"
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 344.9890 through 0 to 14.9047, gap 14.9047 to 344.9890
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 401 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(), 5494 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.98"
Accuracy estimation diagnostic: 321 matched stars entering correct_measured_positions(), 7401 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.93"
Excluding outliers - 321 stars left (next iteration limit 246)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits N_match=321 sigma_overall_arcsec=10.473 sigma_q1_arcsec=25.431 sigma_q2_arcsec=31.247 sigma_q3_arcsec=7.988 sigma_q4_arcsec=8.682 n_q1=34 n_q2=19 n_q3=122 n_q4=146 worst_quadrant_to_overall_ratio=2.983
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits): sigma 10.473->10.473, ratio 2.983->2.983; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=10.871 -- 21.96x the reference average (0.495); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=10.473 -- 21.16x the reference average (0.495); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=3.369 -- 3.00x the reference average (1.122); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=2.983 -- 2.66x 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-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094_astrometric_residuals.png (336 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 3.83 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095_astrometric_residuals.png (321 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.43 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-55-08_20.00sec_5.00C_LIGHT_0094.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_025641_TTUQ2b1x1_3262277_v6E3c78G/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095.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:52:37.81 +56:44:34.2: 12.85 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:45.24 +50:11:48.3: 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:14:53.77 +53:15:40.4: 12.58 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:19.47 +54:07:55.8: 13.47 +/- 0.04 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:59:39.67 +56:24:07.1: 12.39 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:17:34.48 +51:29:01.4: 15.59 +/- 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:19.47 +54:07:55.8: 13.46 +/- 0.04 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:37.81 +56:44:34.2: 12.78 +/- 0.02 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.77 +53:15:40.4: 12.58 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:45.24 +50:11:48.3: 15.62 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.46 +/- 0.03
Forced photometry filter KEPT candidate at 00:02:19.47 +54:07:55.8: ref_mag=13.46 +/- 0.03 new_mean_mag=11.7127 delta=1.75 (need > 0.90)
Forced photometry reference-image weighted average: 12.58 +/- 0.01
Forced photometry reference-image weighted average: 12.81 +/- 0.02
Forced photometry filter KEPT candidate at 00:14:53.77 +53:15:40.4: ref_mag=12.58 +/- 0.01 new_mean_mag=11.5288 delta=1.05 (need > 0.90)
Forced photometry filter KEPT candidate at 23:52:37.81 +56:44:34.2: ref_mag=12.81 +/- 0.02 new_mean_mag=11.7244 delta=1.08 (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:17:34.48 +51:29:01.4: 15.59 +/- 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:36.91 +53:41:32.0: 15.57 +/- 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:08:26.91 +53:20:25.4: 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:59:39.67 +56:24:07.1: 12.31 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:03:57.40 +54:08:00.3: 14.24 +/- 0.10 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:01:47.62 +53:05:06.4: 15.82 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 12.35 +/- 0.01
Forced photometry filter REJECTED candidate at 23:59:39.67 +56:24:07.1: ref_mag=12.35 +/- 0.01 new_mean_mag=11.7142 delta=0.63 (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:01:47.62 +53:05:06.4: 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:11:36.91 +53:41:32.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 00:08:26.91 +53:20:25.4: 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:03:57.40 +54:08:00.3: 14.21 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.23 +/- 0.07
Forced photometry filter KEPT candidate at 00:03:57.40 +54:08:00.3: ref_mag=14.23 +/- 0.07 new_mean_mag=11.9892 delta=2.24 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:47:40.63 +57:49:58.7: 12.03 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:47:40.63 +57:49:58.7: 12.03 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.03 +/- 0.01
Forced photometry filter REJECTED candidate at 23:47:40.63 +57:49:58.7: ref_mag=12.03 +/- 0.01 new_mean_mag=12.0197 delta=0.01 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:09:24.07 +55:18:48.9: 11.99 +/- 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:09:24.07 +55:18:48.9: 12.02 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.00 +/- 0.01
Forced photometry filter REJECTED candidate at 00:09:24.07 +55:18:48.9: ref_mag=12.00 +/- 0.01 new_mean_mag=12.0380 delta=-0.04 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:58.28 +54:51:10.3: 12.84 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:58.28 +54:51:10.3: 12.85 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.85 +/- 0.02
Forced photometry filter REJECTED candidate at 23:58:58.28 +54:51:10.3: ref_mag=12.85 +/- 0.02 new_mean_mag=12.0142 delta=0.83 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:15:56.95 +57:26:22.3: 12.17 +/- 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:15:56.95 +57:26:22.3: 12.15 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.16 +/- 0.01
Forced photometry filter REJECTED candidate at 00:15:56.95 +57:26:22.3: ref_mag=12.16 +/- 0.01 new_mean_mag=12.0143 delta=0.15 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:18:28.50 +53:39:28.5: 15.16 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:18:28.50 +53:39:28.5: 15.25 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.20 +/- 0.16
Forced photometry filter KEPT candidate at 00:18:28.50 +53:39:28.5: ref_mag=15.20 +/- 0.16 new_mean_mag=11.9609 delta=3.24 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:02:37.91 +53:39:41.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:02:37.91 +53:39:41.0: 15.77 +/- 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:16:04.41 +58:08:26.1: 12.08 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:16:04.41 +58:08:26.1: 12.07 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.07 +/- 0.01
Forced photometry filter REJECTED candidate at 00:16:04.41 +58:08:26.1: ref_mag=12.07 +/- 0.01 new_mean_mag=12.0168 delta=0.06 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:47:38.74 +57:49:33.7: 12.17 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:47:38.74 +57:49:33.7: 12.14 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.16 +/- 0.01
Forced photometry filter REJECTED candidate at 23:47:38.74 +57:49:33.7: ref_mag=12.16 +/- 0.01 new_mean_mag=12.0902 delta=0.07 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:52:56.69 +55:11:44.3: 12.20 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:56.69 +55:11:44.3: 12.17 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.18 +/- 0.01
Forced photometry filter REJECTED candidate at 23:52:56.69 +55:11:44.3: ref_mag=12.18 +/- 0.01 new_mean_mag=12.0752 delta=0.11 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:56:45.55 +54:09:40.5: 12.80 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:56:45.55 +54:09:40.5: 12.93 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.85 +/- 0.02
Forced photometry filter REJECTED candidate at 23:56:45.55 +54:09:40.5: ref_mag=12.85 +/- 0.02 new_mean_mag=12.0697 delta=0.79 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:51:15.90 +52:09:19.5: 15.81 +/- 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:03:43.07 +55:00:57.2: 12.08 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:46:02.67 +53:33:15.4: 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 23:51:15.90 +52:09:19.5: 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:03:43.07 +55:00:57.2: 12.10 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.09 +/- 0.01
Forced photometry filter REJECTED candidate at 00:03:43.07 +55:00:57.2: ref_mag=12.09 +/- 0.01 new_mean_mag=12.0699 delta=0.02 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:46:02.67 +53:33:15.4: 15.61 +/- 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:03:54.74 +54:26:14.5: 12.19 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:34.35 +56:48:24.5: 12.22 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:03:54.74 +54:26:14.5: 12.22 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.20 +/- 0.01
Forced photometry filter REJECTED candidate at 00:03:54.74 +54:26:14.5: ref_mag=12.20 +/- 0.01 new_mean_mag=12.0950 delta=0.11 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:55:34.35 +56:48:24.5: 12.16 +/- 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:00:59.21 +53:46:34.6: 15.70 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 12.19 +/- 0.01
Forced photometry filter REJECTED candidate at 23:55:34.35 +56:48:24.5: ref_mag=12.19 +/- 0.01 new_mean_mag=12.1315 delta=0.05 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:29.67 +57:27:13.3: 12.32 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:52.75 +57:22:02.4: 12.21 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:55:29.67 +57:27:13.3: 12.31 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.32 +/- 0.01
Forced photometry filter REJECTED candidate at 23:55:29.67 +57:27:13.3: ref_mag=12.32 +/- 0.01 new_mean_mag=12.1351 delta=0.18 (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:00:59.21 +53:46:34.6: 15.69 +/- 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:04:09.70 +55:53:02.9: 12.14 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:52.75 +57:22:02.4: 12.21 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.21 +/- 0.01
Forced photometry filter REJECTED candidate at 23:58:52.75 +57:22:02.4: ref_mag=12.21 +/- 0.01 new_mean_mag=12.1386 delta=0.07 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:38.47 +52:35:17.7: 15.74 +/- 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:17:42.48 +53:21:25.8: 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:04:09.70 +55:53:02.9: 12.15 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.15 +/- 0.01
Forced photometry filter REJECTED candidate at 00:04:09.70 +55:53:02.9: ref_mag=12.15 +/- 0.01 new_mean_mag=12.1046 delta=0.04 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:55:38.47 +52:35:17.7: 15.70 +/- 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:01.81 +53:59:20.0: 14.09 +/- 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:17:42.48 +53:21:25.8: 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:02:53.68 +53:25:40.8: 14.91 +/- 0.16 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:03:11.42 +54:39:48.9: 12.23 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:01.81 +53:59:20.0: 14.04 +/- 0.07 detection
Forced photometry reference-image weighted average: 14.06 +/- 0.05
Forced photometry filter KEPT candidate at 00:02:01.81 +53:59:20.0: ref_mag=14.06 +/- 0.05 new_mean_mag=12.0946 delta=1.97 (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:02:53.68 +53:25:40.8: 14.62 +/- 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:03:11.42 +54:39:48.9: 12.27 +/- 0.02 detection
Forced photometry reference-image weighted average: 14.73 +/- 0.10
Forced photometry filter KEPT candidate at 00:02:53.68 +53:25:40.8: ref_mag=14.73 +/- 0.10 new_mean_mag=12.0883 delta=2.64 (need > 0.90)
Forced photometry reference-image weighted average: 12.25 +/- 0.01
Forced photometry filter REJECTED candidate at 00:03:11.42 +54:39:48.9: ref_mag=12.25 +/- 0.01 new_mean_mag=12.1215 delta=0.13 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:24.68 +54:33:36.8: 12.22 +/- 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:04:47.45 +55:17:12.5: 12.13 +/- 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:05:24.68 +54:33:36.8: 12.19 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.20 +/- 0.01
Forced photometry filter REJECTED candidate at 00:05:24.68 +54:33:36.8: ref_mag=12.20 +/- 0.01 new_mean_mag=12.1092 delta=0.09 (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:04:47.45 +55:17:12.5: 12.16 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.15 +/- 0.01
Forced photometry filter REJECTED candidate at 00:04:47.45 +55:17:12.5: ref_mag=12.15 +/- 0.01 new_mean_mag=12.1403 delta=0.01 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:18:51.66 +53:23:47.0: 15.79 +/- 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:07:59.03 +52:54:52.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:51.66 +53:23:47.0: 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:07:59.03 +52:54:52.8: 15.83 +/- 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:20:13.33 +50:44:34.9: 13.00 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:13.33 +50:44:34.9: 13.04 +/- 0.03 detection
Forced photometry reference-image weighted average: 13.02 +/- 0.02
Forced photometry filter KEPT candidate at 00:20:13.33 +50:44:34.9: ref_mag=13.02 +/- 0.02 new_mean_mag=12.0964 delta=0.92 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:26.85 +51:26:16.7: 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:58:26.85 +51:26:16.7: 15.50 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.50 +/- 0.34
Forced photometry filter KEPT candidate at 23:58:26.85 +51:26:16.7: ref_mag=15.50 +/- 0.34 new_mean_mag=7.6142 delta=7.89 (need > 0.90)
Adding exclusion_list_gaiadr2.txt__out36887.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out21888.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33361.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34535.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35015.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35017.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35489.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35592.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35632.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35987.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36008.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36173.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36203.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36446.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36467.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36596.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36672.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36696.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36713.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36746.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36870.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36872.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 58s
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: 34s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31478_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 31478_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32286_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 32286_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:04:40.60 +55:32:14.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32388_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 32388_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:55:50.29 +53:44:28.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33065_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 33065_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:06:02.23 +55:11:58.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33103_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 33103_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:44:31.49 +56:34:50.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33361_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 33361_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33832_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 33832_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34535_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 34535_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35015_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 35015_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35017_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 35017_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35042_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 35042_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35275_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 35275_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35470_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 35470_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35489_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 35489_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35592_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 35592_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35632_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 35632_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35987_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 35987_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36008_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36008_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36031_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36031_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36095_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36095_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36159_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36159_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36160_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36160_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36173_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36173_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36203_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36203_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36288_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36288_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36290_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36290_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36313_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36313_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36332_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36332_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36340_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36340_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36380_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36380_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36412_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36412_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:59:52.53 +53:47:44.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36446_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36446_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36458_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36458_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36467_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36467_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36477_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36477_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36509_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36509_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36512_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36512_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36528_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36528_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (28.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36596_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36596_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36616_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36616_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36658_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36658_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36669_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36669_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36672_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36672_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36694_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36694_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36695_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36695_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36696_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36696_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36698_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36698_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36713_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36713_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36723_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36723_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36746_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36746_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36747_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36747_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:59:01.53 +53:20:01.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36772_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36772_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36805_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36805_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36812_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36812_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36815_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36815_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36848_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36848_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36870_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36870_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36872_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 36872_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36878_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36878_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36887_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 36887_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:20:13.33 +50:44:34.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.10, MAG_FAINT_SEARCH_LIMIT=13.08)GAIADR2_OUTPUT=# 2.614 394918639395604224 005.05668383004 +50.74295730896 12.8074 12.2705 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#2.614#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21888_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 21888_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 08367_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 08367_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 09534_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 09534_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243684_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243684_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243686_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243686_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243687_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243687_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243690_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243690_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (26.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243699_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243699_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (24.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243702_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243702_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243704_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243704_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243709_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243709_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (31.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243721_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243721_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243724_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243724_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243734_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243734_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243740_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243740_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243747_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243747_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243749_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243749_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243752_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243752_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243753_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243753_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243758_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243758_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (33.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243763_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243763_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243775_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243775_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243780_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243780_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243790_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243790_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243793_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243793_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243799_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243799_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243803_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243803_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (30.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243804_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243804_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243805_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243805_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243808_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243808_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243809_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243809_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243812_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243812_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243813_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243813_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243816_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243816_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243820_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243820_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243822_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243822_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243823_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243823_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243826_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243826_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243827_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243827_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243830_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243830_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243832_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243832_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:07:58.59 +57:10:21.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243834_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243834_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243839_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243839_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243852_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243852_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:06:29.72 +56:31:32.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243854_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243854_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243856_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243856_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (28.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243857_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243857_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243858_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243858_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243859_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243859_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243861_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243861_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243862_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243862_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243863_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243863_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243864_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243864_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243865_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243865_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243868_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243868_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (26.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243869_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243869_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243870_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 243870_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243871_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243871_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:59:16.11 +55:57:37.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243872_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 243872_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245598_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 245598_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:06:02.91 +55:11:53.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245647_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 245647_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247200_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 247200_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247423_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 247423_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247814_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 247814_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248060_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 248060_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (30.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248868_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 248868_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:55:26.88 +58:05:25.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249995_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 249995_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (25.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250139_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 250139_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:44:11.55 +56:38:07.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251115_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 251115_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252341_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 252341_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252415_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 252415_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253484_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 253484_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:59:20.05 +55:58:48.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253649_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 253649_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:42:06.21 +57:15:56.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253984_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 253984_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254225_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 254225_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:56:19.99 +55:11:15.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255395_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 255395_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257630_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 257630_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257770_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 257770_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257790_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 257790_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258650_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 258650_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259162_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 259162_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259243_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 259243_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259412_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 259412_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259606_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 259606_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259892_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 259892_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:53:27.57 +56:50:28.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259902_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 259902_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:54:50.46 +56:11:33.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259945_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 259945_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260316_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 260316_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (26.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260551_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 260551_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:11:54.87 +57:16:17.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260560_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 260560_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260766_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 260766_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261350_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 261350_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261458_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 261458_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261523_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 261523_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:41:21.99 +57:32:49.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261666_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 261666_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261909_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 261909_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262114_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 262114_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262170_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 262170_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:52:57.95 +55:03:16.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262361_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 262361_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (31.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262427_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 262427_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263128_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 263128_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263683_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 263683_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263713_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 263713_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:12:15.13 +57:18:53.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264037_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264037_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264079_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 264079_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264433_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264433_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264544_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264544_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:24:31.06 +56:56:58.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264562_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264562_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (35.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264593_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264593_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:38:01.52 +58:05:44.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264857_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264857_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264951_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 264951_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:00:23.20 +56:50:07.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265042_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265042_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265109_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265109_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265206_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 265206_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265423_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265423_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265531_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265531_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:20:27.54 +57:50:28.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265562_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265562_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265668_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 265668_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265689_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265689_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265877_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 265877_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:54:09.75 +56:00:06.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266260_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 266260_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266298_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 266298_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (47.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266317_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 266317_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266472_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 266472_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266648_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 266648_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266710_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 266710_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:15:08.77 +56:19:24.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266996_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 266996_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267197_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267197_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267315_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267315_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267407_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267407_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267625_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267625_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267658_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267658_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:24:19.73 +53:13:46.4 in the exclusion list exclusion_list_tycho2.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267714_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267714_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267799_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267799_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:18:30.31 +55:38:55.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267821_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 267821_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268533_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 268533_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268612_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 268612_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268671_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 268671_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268686_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 268686_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268915_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 268915_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268980_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 268980_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:02:27.23 +54:33:05.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269005_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269005_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269163_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269163_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269168_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 269168_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269221_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269221_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269321_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269321_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:53:02.02 +55:10:29.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269625_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269625_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:58:13.60 +56:29:31.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269648_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 269648_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269710_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269710_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269830_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269830_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269885_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 269885_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270027_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 270027_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270242_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 270242_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270494_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 270494_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270593_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 270593_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270678_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 270678_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:09:24.02 +58:04:08.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270686_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 270686_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270713_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 270713_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270853_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 270853_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270881_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 270881_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (45.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271056_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 271056_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:09:26.51 +56:02:09.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271149_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 271149_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271234_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 271234_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:18:51.54 +57:49:36.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271239_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 271239_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:51:58.72 +56:02:28.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271633_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 271633_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271896_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 271896_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272118_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 272118_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272285_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 272285_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272489_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 272489_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272654_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 272654_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:55:42.40 +57:23:28.8 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272900_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 272900_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272987_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 272987_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273236_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 273236_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273318_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 273318_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273422_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 273422_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273489_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 273489_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (33.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273710_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 273710_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273766_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 273766_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273827_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 273827_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274002_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 274002_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (34.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274180_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 274180_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274224_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 274224_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (31.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274330_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 274330_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274541_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 274541_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274592_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 274592_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275013_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275013_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275046_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275046_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275074_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275074_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275558_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 275558_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275562_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275562_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275656_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275656_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275721_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275721_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275765_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275765_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275852_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 275852_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276084_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 276084_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276359_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 276359_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276985_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 276985_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277033_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 277033_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277203_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 277203_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277615_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 277615_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277640_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 277640_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277749_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 277749_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277957_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 277957_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278302_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 278302_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278501_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 278501_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279299_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 279299_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279422_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 279422_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279723_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 279723_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279908_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 279908_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (28.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279975_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 279975_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279989_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 279989_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (35.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280070_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 280070_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280253_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 280253_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280315_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 280315_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280480_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 280480_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280501_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 280501_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280882_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 280882_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281015_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 281015_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281280_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 281280_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281513_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 281513_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281726_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 281726_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281761_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 281761_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281862_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 281862_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281885_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 281885_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281913_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 281913_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281977_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 281977_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282031_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282031_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282069_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282069_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282495_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 282495_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282542_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282542_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282644_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282644_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282655_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282655_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282681_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282681_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282944_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282944_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282946_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 282946_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282964_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 282964_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283032_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283032_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283071_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283071_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283376_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283376_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283404_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283404_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (30.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283420_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283420_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283444_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283444_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283477_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283477_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283528_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283528_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283644_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283644_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283647_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283647_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283653_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 283653_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283725_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283725_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283743_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283743_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283809_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283809_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283959_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283959_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283976_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 283976_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284004_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284004_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284019_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284019_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284020_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284020_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284050_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284050_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284112_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284112_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284115_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284115_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284190_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284190_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284221_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284221_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284300_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284300_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284334_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284334_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284355_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284355_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284377_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284377_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284452_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284452_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284521_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284521_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284549_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284549_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284552_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284552_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284565_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284565_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (29.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284590_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284590_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284591_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284591_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284634_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284634_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284700_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284700_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284708_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284708_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (29.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284751_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284751_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284773_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284773_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284802_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284802_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284807_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284807_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284813_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284813_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284853_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284853_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284865_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284865_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284948_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284948_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284972_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284972_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284974_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 284974_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284986_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 284986_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285045_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285045_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285089_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285089_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285101_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 285101_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285160_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 285160_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285263_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285263_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285334_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285334_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285335_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285335_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (28.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285401_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285401_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (34.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285415_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285415_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285426_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285426_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285427_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285427_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285436_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285436_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285461_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285461_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (27.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285466_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 285466_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285633_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285633_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285750_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285750_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285834_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 285834_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285858_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 285858_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285965_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 285965_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286021_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 286021_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286080_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 286080_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286276_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 286276_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (38.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69970_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 69970_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 130430_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 130430_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174810_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 174810_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (33.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 117774_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 117774_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 119320_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 119320_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177194_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 177194_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 98268_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 98268_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:58:59.34 +54:51:05.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 160198_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 160198_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (27.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 79234_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 79234_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 00:04:40.94 +55:32:15.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58579_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 58579_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:44:32.13 +56:34:48.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179137_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 179137_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125040_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 125040_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 53473_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
The candidate 53473_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095 did not pass the final checks
**** FOUND 23:52:38.81 +56:44:32.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71796_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 71796_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143637_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
Preparing report for the candidate 143637_fd_Cas-04-Q2b1x1_2026-06-24_02-56-00_20.00sec_4.90C_LIGHT_0095
make_report_in_HTML.sh Phase 2 (HTML assembly): 10s
make_report_in_HTML.sh TOTAL: 362s
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:58:26.85 +51:26:16.7
00:20:45.24 +50:11:48.3
00:14:53.77 +53:15:40.4
23:52:37.81 +56:44:34.2
00:02:19.47 +54:07:55.8
00:17:34.48 +51:29:01.4
00:08:26.91 +53:20:25.4
00:11:36.91 +53:41:32.0
00:01:47.62 +53:05:06.4
00:03:57.40 +54:08:00.3
00:18:28.50 +53:39:28.5
00:02:37.91 +53:39:41.0
23:51:15.90 +52:09:19.5
23:46:02.67 +53:33:15.4
00:00:59.21 +53:46:34.6
23:55:38.47 +52:35:17.7
00:17:42.48 +53:21:25.8
00:02:01.81 +53:59:20.0
00:02:53.68 +53:25:40.8
00:18:51.66 +53:23:47.0
00:07:59.03 +52:54:52.8
00:02:02.19 +53:59:29.3
23:55:49.34 +53:44:23.7
00:13:24.43 +52:37:43.0
23:34:59.30 +50:35:48.5
23:40:10.84 +53:34:46.8
23:36:06.73 +56:16:10.0
23:41:15.06 +56:15:32.9
23:33:42.08 +56:14:35.8
23:43:06.00 +52:01:14.3
23:35:58.13 +53:28:50.4
23:32:22.01 +56:57:40.9
23:38:19.66 +50:33:19.2
23:35:02.95 +55:49:49.2
00:28:30.15 +51:38:26.4
23:42:28.80 +53:37:20.5
23:33:30.65 +56:13:29.9
00:22:53.72 +52:49:47.9
23:43:27.06 +52:27:01.4
00:22:23.83 +51:17:43.7
23:37:26.49 +55:33:35.8
23:42:54.61 +53:06:01.8
23:37:32.63 +51:50:44.1
23:58:48.31 +53:26:35.2
23:43:35.72 +53:16:14.1
23:31:40.38 +57:27:20.8
23:29:16.91 +55:18:50.1
23:32:06.54 +57:45:11.4
23:35:02.39 +56:30:46.6
23:31:59.31 +55:07:39.8
23:47:34.99 +52:37:51.9
00:23:23.05 +55:49:17.4
23:33:32.89 +50:54:47.0
23:43:35.64 +50:08:35.6
23:38:55.08 +51:35:15.9
00:05:01.07 +51:13:17.4
23:36:56.67 +55:34:18.8
23:33:32.06 +56:43:59.2
00:27:52.66 +52:58:19.2
23:44:09.71 +53:03:31.9
23:43:26.63 +51:45:07.9
00:22:44.08 +56:26:51.3
23:57:05.80 +52:12:20.7
00:19:46.79 +51:04:48.3
23:32:12.99 +55:32:45.4
23:35:17.11 +55:37:18.2
00:01:19.02 +51:15:17.9
23:29:08.74 +56:37:28.9
00:27:16.95 +54:05:39.3
00:06:21.20 +52:40:38.1
23:56:27.04 +53:44:46.4
23:37:38.39 +56:52:47.2
23:32:42.99 +56:50:33.3
23:30:55.98 +51:08:07.2
23:48:03.24 +51:53:54.3
00:08:30.18 +51:27:23.6
23:32:13.79 +56:56:26.7
23:29:45.27 +56:06:24.2
23:32:08.30 +53:57:16.0
23:31:13.09 +57:29:23.6
23:30:57.09 +50:50:58.9
23:32:32.78 +50:43:05.5
23:30:04.58 +56:12:42.1
23:31:19.55 +50:23:15.9
23:36:42.72 +53:33:03.3
23:32:25.41 +55:22:16.4
23:29:18.55 +55:17:00.3
23:31:22.28 +54:31:58.3
23:33:49.78 +57:33:02.7
23:31:14.89 +51:41:33.5
23:31:51.39 +51:36:15.2
00:05:47.98 +53:57:46.7
23:33:33.34 +55:13:44.8
23:31:19.52 +57:10:23.0
23:39:23.46 +56:29:07.7
23:32:52.38 +55:31:51.8
23:36:37.82 +55:28:14.6
23:29:23.63 +56:53:27.5
23:40:23.01 +53:45:30.1
23:34:20.01 +55:18:49.2
23:35:13.50 +50:52:41.8
23:45:59.31 +54:45:21.6
23:31:14.33 +57:14:39.8
23:31:38.41 +56:08:43.3
23:31:44.80 +51:29:27.8
23:33:00.05 +50:29:51.5
23:37:01.99 +51:37:44.4
23:43:30.06 +50:56:49.9
00:06:31.80 +52:20:36.8
00:23:10.78 +55:47:35.0
23:38:16.13 +56:01:54.5
########### 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 ####
00:20:45.24 +50:11:48.3
00:14:53.77 +53:15:40.4
23:52:37.81 +56:44:34.2
00:02:19.47 +54:07:55.8
00:17:34.48 +51:29:01.4
00:08:26.91 +53:20:25.4
00:11:36.91 +53:41:32.0
00:01:47.62 +53:05:06.4
00:03:57.40 +54:08:00.3
00:18:28.50 +53:39:28.5
00:02:37.91 +53:39:41.0
23:51:15.90 +52:09:19.5
23:46:02.67 +53:33:15.4
00:00:59.21 +53:46:34.6
23:55:38.47 +52:35:17.7
00:17:42.48 +53:21:25.8
00:02:01.81 +53:59:20.0
00:02:53.68 +53:25:40.8
00:18:51.66 +53:23:47.0
00:07:59.03 +52:54:52.8
23:58:26.85 +51:26:16.7
23:40:10.84 +53:34:46.8
23:36:06.73 +56:16:10.0
23:41:15.06 +56:15:32.9
23:33:42.08 +56:14:35.8
23:43:06.00 +52:01:14.3
23:35:58.13 +53:28:50.4
23:32:22.01 +56:57:40.9
23:38:19.66 +50:33:19.2
23:35:02.95 +55:49:49.2
00:28:30.15 +51:38:26.4
23:42:28.80 +53:37:20.5
23:33:30.65 +56:13:29.9
00:22:53.72 +52:49:47.9
23:43:27.06 +52:27:01.4
00:22:23.83 +51:17:43.7
23:37:26.49 +55:33:35.8
23:42:54.61 +53:06:01.8
23:37:32.63 +51:50:44.1
23:58:48.31 +53:26:35.2
23:43:35.72 +53:16:14.1
23:31:40.38 +57:27:20.8
23:29:16.91 +55:18:50.1
23:32:06.54 +57:45:11.4
23:35:02.39 +56:30:46.6
23:31:59.31 +55:07:39.8
23:47:34.99 +52:37:51.9
00:23:23.05 +55:49:17.4
23:33:32.89 +50:54:47.0
23:43:35.64 +50:08:35.6
23:38:55.08 +51:35:15.9
00:05:01.07 +51:13:17.4
23:36:56.67 +55:34:18.8
23:33:32.06 +56:43:59.2
00:27:52.66 +52:58:19.2
23:44:09.71 +53:03:31.9
23:43:26.63 +51:45:07.9
00:22:44.08 +56:26:51.3
23:57:05.80 +52:12:20.7
00:19:46.79 +51:04:48.3
23:32:12.99 +55:32:45.4
23:35:17.11 +55:37:18.2
00:01:19.02 +51:15:17.9
23:29:08.74 +56:37:28.9
00:27:16.95 +54:05:39.3
00:06:21.20 +52:40:38.1
23:56:27.04 +53:44:46.4
23:37:38.39 +56:52:47.2
23:32:42.99 +56:50:33.3
23:30:55.98 +51:08:07.2
23:48:03.24 +51:53:54.3
00:08:30.18 +51:27:23.6
23:32:13.79 +56:56:26.7
23:29:45.27 +56:06:24.2
23:32:08.30 +53:57:16.0
23:31:13.09 +57:29:23.6
23:30:57.09 +50:50:58.9
23:32:32.78 +50:43:05.5
23:30:04.58 +56:12:42.1
23:31:19.55 +50:23:15.9
23:36:42.72 +53:33:03.3
23:32:25.41 +55:22:16.4
23:29:18.55 +55:17:00.3
23:31:22.28 +54:31:58.3
23:33:49.78 +57:33:02.7
23:31:14.89 +51:41:33.5
23:31:51.39 +51:36:15.2
00:05:47.98 +53:57:46.7
23:33:33.34 +55:13:44.8
23:31:19.52 +57:10:23.0
23:39:23.46 +56:29:07.7
23:32:52.38 +55:31:51.8
23:36:37.82 +55:28:14.6
23:29:23.63 +56:53:27.5
23:40:23.01 +53:45:30.1
23:34:20.01 +55:18:49.2
23:35:13.50 +50:52:41.8
23:45:59.31 +54:45:21.6
23:31:14.33 +57:14:39.8
23:31:38.41 +56:08:43.3
23:31:44.80 +51:29:27.8
23:33:00.05 +50:29:51.5
23:37:01.99 +51:37:44.4
23:43:30.06 +50:56:49.9
00:06:31.80 +52:20:36.8
00:23:10.78 +55:47:35.0
00:02:02.19 +53:59:29.3
23:34:59.30 +50:35:48.5
23:55:49.34 +53:44:23.7
23:38:16.13 +56:01:54.5
00:13:24.43 +52:37:43.0
###################################################################################
00:20:45.24 +50:11:48.3 -- not an asteroid (will add it to exclusion list)
00:14:53.77 +53:15:40.4 -- not an asteroid (will add it to exclusion list)
23:52:37.81 +56:44:34.2 -- not an asteroid (will add it to exclusion list)
00:02:19.47 +54:07:55.8 -- not an asteroid (will add it to exclusion list)
00:17:34.48 +51:29:01.4 -- not an asteroid (will add it to exclusion list)
00:08:26.91 +53:20:25.4 -- not an asteroid (will add it to exclusion list)
00:11:36.91 +53:41:32.0 -- not an asteroid (will add it to exclusion list)
00:01:47.62 +53:05:06.4 -- not an asteroid (will add it to exclusion list)
00:03:57.40 +54:08:00.3 -- not an asteroid (will add it to exclusion list)
00:18:28.50 +53:39:28.5 -- not an asteroid (will add it to exclusion list)
00:02:37.91 +53:39:41.0 -- not an asteroid (will add it to exclusion list)
23:51:15.90 +52:09:19.5 -- not an asteroid (will add it to exclusion list)
23:46:02.67 +53:33:15.4 -- not an asteroid (will add it to exclusion list)
00:00:59.21 +53:46:34.6 -- not an asteroid (will add it to exclusion list)
23:55:38.47 +52:35:17.7 -- not an asteroid (will add it to exclusion list)
00:17:42.48 +53:21:25.8 -- not an asteroid (will add it to exclusion list)
00:02:01.81 +53:59:20.0 -- not an asteroid (will add it to exclusion list)
00:02:53.68 +53:25:40.8 -- not an asteroid (will add it to exclusion list)
00:18:51.66 +53:23:47.0 -- not an asteroid (will add it to exclusion list)
00:07:59.03 +52:54:52.8 -- not an asteroid (will add it to exclusion list)
23:58:26.85 +51:26:16.7 -- not an asteroid (will add it to exclusion list)
23:40:10.84 +53:34:46.8 -- not an asteroid (will add it to exclusion list)
23:36:06.73 +56:16:10.0 -- not an asteroid (will add it to exclusion list)
23:41:15.06 +56:15:32.9 -- not an asteroid (will add it to exclusion list)
23:33:42.08 +56:14:35.8 -- not an asteroid (will add it to exclusion list)
23:43:06.00 +52:01:14.3 -- not an asteroid (will add it to exclusion list)
23:35:58.13 +53:28:50.4 -- not an asteroid (will add it to exclusion list)
23:32:22.01 +56:57:40.9 -- not an asteroid (will add it to exclusion list)
23:38:19.66 +50:33:19.2 -- not an asteroid (will add it to exclusion list)
23:35:02.95 +55:49:49.2 -- not an asteroid (will add it to exclusion list)
00:28:30.15 +51:38:26.4 -- not an asteroid (will add it to exclusion list)
23:42:28.80 +53:37:20.5 -- not an asteroid (will add it to exclusion list)
23:33:30.65 +56:13:29.9 -- not an asteroid (will add it to exclusion list)
00:22:53.72 +52:49:47.9 -- not an asteroid (will add it to exclusion list)
23:43:27.06 +52:27:01.4 -- not an asteroid (will add it to exclusion list)
00:22:23.83 +51:17:43.7 -- not an asteroid (will add it to exclusion list)
23:37:26.49 +55:33:35.8 -- not an asteroid (will add it to exclusion list)
23:42:54.61 +53:06:01.8 -- not an asteroid (will add it to exclusion list)
23:37:32.63 +51:50:44.1 -- not an asteroid (will add it to exclusion list)
23:58:48.31 +53:26:35.2 -- not an asteroid (will add it to exclusion list)
23:43:35.72 +53:16:14.1 -- not an asteroid (will add it to exclusion list)
23:31:40.38 +57:27:20.8 -- not an asteroid (will add it to exclusion list)
23:29:16.91 +55:18:50.1 -- not an asteroid (will add it to exclusion list)
23:32:06.54 +57:45:11.4 -- not an asteroid (will add it to exclusion list)
23:35:02.39 +56:30:46.6 -- not an asteroid (will add it to exclusion list)
23:31:59.31 +55:07:39.8 -- not an asteroid (will add it to exclusion list)
23:47:34.99 +52:37:51.9 -- not an asteroid (will add it to exclusion list)
00:23:23.05 +55:49:17.4 -- not an asteroid (will add it to exclusion list)
23:33:32.89 +50:54:47.0 -- not an asteroid (will add it to exclusion list)
23:43:35.64 +50:08:35.6 -- not an asteroid (will add it to exclusion list)
23:38:55.08 +51:35:15.9 -- not an asteroid (will add it to exclusion list)
00:05:01.07 +51:13:17.4 -- not an asteroid (will add it to exclusion list)
23:36:56.67 +55:34:18.8 -- not an asteroid (will add it to exclusion list)
23:33:32.06 +56:43:59.2 -- not an asteroid (will add it to exclusion list)
00:27:52.66 +52:58:19.2 -- not an asteroid (will add it to exclusion list)
23:44:09.71 +53:03:31.9 -- not an asteroid (will add it to exclusion list)
23:43:26.63 +51:45:07.9 -- not an asteroid (will add it to exclusion list)
00:22:44.08 +56:26:51.3 -- not an asteroid (will add it to exclusion list)
23:57:05.80 +52:12:20.7 -- not an asteroid (will add it to exclusion list)
00:19:46.79 +51:04:48.3 -- not an asteroid (will add it to exclusion list)
23:32:12.99 +55:32:45.4 -- not an asteroid (will add it to exclusion list)
23:35:17.11 +55:37:18.2 -- not an asteroid (will add it to exclusion list)
00:01:19.02 +51:15:17.9 -- not an asteroid (will add it to exclusion list)
23:29:08.74 +56:37:28.9 -- not an asteroid (will add it to exclusion list)
00:27:16.95 +54:05:39.3 -- not an asteroid (will add it to exclusion list)
00:06:21.20 +52:40:38.1 -- not an asteroid (will add it to exclusion list)
23:56:27.04 +53:44:46.4 -- not an asteroid (will add it to exclusion list)
23:37:38.39 +56:52:47.2 -- not an asteroid (will add it to exclusion list)
23:32:42.99 +56:50:33.3 -- not an asteroid (will add it to exclusion list)
23:30:55.98 +51:08:07.2 -- not an asteroid (will add it to exclusion list)
23:48:03.24 +51:53:54.3 -- not an asteroid (will add it to exclusion list)
00:08:30.18 +51:27:23.6 -- not an asteroid (will add it to exclusion list)
23:32:13.79 +56:56:26.7 -- not an asteroid (will add it to exclusion list)
23:29:45.27 +56:06:24.2 -- not an asteroid (will add it to exclusion list)
23:32:08.30 +53:57:16.0 -- not an asteroid (will add it to exclusion list)
23:31:13.09 +57:29:23.6 -- not an asteroid (will add it to exclusion list)
23:30:57.09 +50:50:58.9 -- not an asteroid (will add it to exclusion list)
23:32:32.78 +50:43:05.5 -- not an asteroid (will add it to exclusion list)
23:30:04.58 +56:12:42.1 -- not an asteroid (will add it to exclusion list)
23:31:19.55 +50:23:15.9 -- not an asteroid (will add it to exclusion list)
23:36:42.72 +53:33:03.3 -- not an asteroid (will add it to exclusion list)
23:32:25.41 +55:22:16.4 -- not an asteroid (will add it to exclusion list)
23:29:18.55 +55:17:00.3 -- not an asteroid (will add it to exclusion list)
23:31:22.28 +54:31:58.3 -- not an asteroid (will add it to exclusion list)
23:33:49.78 +57:33:02.7 -- not an asteroid (will add it to exclusion list)
23:31:14.89 +51:41:33.5 -- not an asteroid (will add it to exclusion list)
23:31:51.39 +51:36:15.2 -- not an asteroid (will add it to exclusion list)
00:05:47.98 +53:57:46.7 -- not an asteroid (will add it to exclusion list)
23:33:33.34 +55:13:44.8 -- not an asteroid (will add it to exclusion list)
23:31:19.52 +57:10:23.0 -- not an asteroid (will add it to exclusion list)
23:39:23.46 +56:29:07.7 -- not an asteroid (will add it to exclusion list)
23:32:52.38 +55:31:51.8 -- not an asteroid (will add it to exclusion list)
23:36:37.82 +55:28:14.6 -- not an asteroid (will add it to exclusion list)
23:29:23.63 +56:53:27.5 -- not an asteroid (will add it to exclusion list)
23:40:23.01 +53:45:30.1 -- not an asteroid (will add it to exclusion list)
23:34:20.01 +55:18:49.2 -- not an asteroid (will add it to exclusion list)
23:35:13.50 +50:52:41.8 -- not an asteroid (will add it to exclusion list)
23:45:59.31 +54:45:21.6 -- not an asteroid (will add it to exclusion list)
23:31:14.33 +57:14:39.8 -- not an asteroid (will add it to exclusion list)
23:31:38.41 +56:08:43.3 -- not an asteroid (will add it to exclusion list)
23:31:44.80 +51:29:27.8 -- not an asteroid (will add it to exclusion list)
23:33:00.05 +50:29:51.5 -- not an asteroid (will add it to exclusion list)
23:37:01.99 +51:37:44.4 -- not an asteroid (will add it to exclusion list)
23:43:30.06 +50:56:49.9 -- not an asteroid (will add it to exclusion list)
00:06:31.80 +52:20:36.8 -- not an asteroid (will add it to exclusion list)
00:23:10.78 +55:47:35.0 -- not an asteroid (will add it to exclusion list)
00:02:02.19 +53:59:29.3 -- not an asteroid (will add it to exclusion list)
23:34:59.30 +50:35:48.5 -- not an asteroid (will add it to exclusion list)
23:55:49.34 +53:44:23.7 -- not an asteroid (will add it to exclusion list)
23:38:16.13 +56:01:54.5 -- not an asteroid (will add it to exclusion list)
00:13:24.43 +52:37:43.0 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:59.21 +53:46:34.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:19.02 +51:15:17.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:47.62 +53:05:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:01.81 +53:59:20.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:02.19 +53:59:29.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:19.47 +54:07:55.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:37.91 +53:39:41.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:53.68 +53:25:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:57.40 +54:08:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:01.07 +51:13:17.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:47.98 +53:57:46.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:21.20 +52:40:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:31.80 +52:20:36.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:59.03 +52:54:52.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:26.91 +53:20:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:30.18 +51:27:23.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:36.91 +53:41:32.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:24.43 +52:37:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:53.77 +53:15:40.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:34.48 +51:29:01.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:42.48 +53:21:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:28.50 +53:39:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:51.66 +53:23:47.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:46.79 +51:04:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:45.24 +50:11:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:23.83 +51:17:43.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:44.08 +56:26:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:53.72 +52:49:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:10.78 +55:47:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:23.05 +55:49:17.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:16.95 +54:05:39.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:52.66 +52:58:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:30.15 +51:38:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:08.74 +56:37:28.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:16.91 +55:18:50.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:18.55 +55:17:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:23.63 +56:53:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:45.27 +56:06:24.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:04.58 +56:12:42.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:55.98 +51:08:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:57.09 +50:50:58.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:13.09 +57:29:23.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:14.33 +57:14:39.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:14.89 +51:41:33.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:19.52 +57:10:23.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:19.55 +50:23:15.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:22.28 +54:31:58.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:38.41 +56:08:43.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:40.38 +57:27:20.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:44.80 +51:29:27.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:51.39 +51:36:15.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:59.31 +55:07:39.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:06.54 +57:45:11.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:08.30 +53:57:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:12.99 +55:32:45.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:13.79 +56:56:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:22.01 +56:57:40.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:25.41 +55:22:16.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:32.78 +50:43:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:42.99 +56:50:33.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:52.38 +55:31:51.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:00.05 +50:29:51.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:30.65 +56:13:29.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:32.06 +56:43:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:32.89 +50:54:47.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:33.34 +55:13:44.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:42.08 +56:14:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:49.78 +57:33:02.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:20.01 +55:18:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:59.30 +50:35:48.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:02.39 +56:30:46.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:02.95 +55:49:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:13.50 +50:52:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:17.11 +55:37:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:58.13 +53:28:50.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:06.73 +56:16:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:37.82 +55:28:14.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:42.72 +53:33:03.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:56.67 +55:34:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:01.99 +51:37:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:26.49 +55:33:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:32.63 +51:50:44.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:38.39 +56:52:47.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:16.13 +56:01:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:19.66 +50:33:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:55.08 +51:35:15.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:23.46 +56:29:07.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:10.84 +53:34:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:23.01 +53:45:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:15.06 +56:15:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:28.80 +53:37:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:54.61 +53:06:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:06.00 +52:01:14.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:26.63 +51:45:07.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:27.06 +52:27:01.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:30.06 +50:56:49.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:35.64 +50:08:35.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:35.72 +53:16:14.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:09.71 +53:03:31.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:59.31 +54:45:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:02.67 +53:33:15.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:34.99 +52:37:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:03.24 +51:53:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:15.90 +52:09:19.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:37.81 +56:44:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:38.47 +52:35:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:49.34 +53:44:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:27.04 +53:44:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:05.80 +52:12:20.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:26.85 +51:26:16.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:48.31 +53:26:35.2 -- 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:59.21 +53:46:34.6 -- not a known variable star
00:01:19.02 +51:15:17.9 -- not a known variable star
00:01:47.62 +53:05:06.4 -- not a known variable star
00:02:01.81 +53:59:20.0 -- not a known variable star
00:02:02.19 +53:59:29.3 -- not a known variable star
00:02:19.47 +54:07:55.8 -- not a known variable star
00:02:37.91 +53:39:41.0 -- not a known variable star
00:02:53.68 +53:25:40.8 -- a known variable star
00:03:57.40 +54:08:00.3 -- not a known variable star
00:05:01.07 +51:13:17.4 -- not a known variable star
00:05:47.98 +53:57:46.7 -- not a known variable star
00:06:21.20 +52:40:38.1 -- not a known variable star
00:06:31.80 +52:20:36.8 -- not a known variable star
00:07:59.03 +52:54:52.8 -- not a known variable star
00:08:26.91 +53:20:25.4 -- not a known variable star
00:08:30.18 +51:27:23.6 -- not a known variable star
00:11:36.91 +53:41:32.0 -- not a known variable star
00:13:24.43 +52:37:43.0 -- not a known variable star
00:14:53.77 +53:15:40.4 -- not a known variable star
00:17:34.48 +51:29:01.4 -- not a known variable star
00:17:42.48 +53:21:25.8 -- not a known variable star
00:18:28.50 +53:39:28.5 -- a known variable star
00:18:51.66 +53:23:47.0 -- a known variable star
00:19:46.79 +51:04:48.3 -- not a known variable star
00:20:45.24 +50:11:48.3 -- not a known variable star
00:22:23.83 +51:17:43.7 -- not a known variable star
00:22:44.08 +56:26:51.3 -- not a known variable star
00:22:53.72 +52:49:47.9 -- not a known variable star
00:23:10.78 +55:47:35.0 -- not a known variable star
00:23:23.05 +55:49:17.4 -- not a known variable star
00:27:16.95 +54:05:39.3 -- not a known variable star
00:27:52.66 +52:58:19.2 -- not a known variable star
00:28:30.15 +51:38:26.4 -- not a known variable star
23:29:08.74 +56:37:28.9 -- not a known variable star
23:29:16.91 +55:18:50.1 -- not a known variable star
23:29:18.55 +55:17:00.3 -- not a known variable star
23:29:23.63 +56:53:27.5 -- not a known variable star
23:29:45.27 +56:06:24.2 -- not a known variable star
23:30:04.58 +56:12:42.1 -- not a known variable star
23:30:55.98 +51:08:07.2 -- not a known variable star
23:30:57.09 +50:50:58.9 -- a known variable star
23:31:13.09 +57:29:23.6 -- not a known variable star
23:31:14.33 +57:14:39.8 -- not a known variable star
23:31:14.89 +51:41:33.5 -- not a known variable star
23:31:19.52 +57:10:23.0 -- not a known variable star
23:31:19.55 +50:23:15.9 -- a known variable star
23:31:22.28 +54:31:58.3 -- not a known variable star
23:31:38.41 +56:08:43.3 -- a known variable star
23:31:40.38 +57:27:20.8 -- not a known variable star
23:31:44.80 +51:29:27.8 -- not a known variable star
23:31:51.39 +51:36:15.2 -- not a known variable star
23:31:59.31 +55:07:39.8 -- not a known variable star
23:32:06.54 +57:45:11.4 -- not a known variable star
23:32:08.30 +53:57:16.0 -- not a known variable star
23:32:12.99 +55:32:45.4 -- not a known variable star
23:32:13.79 +56:56:26.7 -- not a known variable star
23:32:22.01 +56:57:40.9 -- not a known variable star
23:32:25.41 +55:22:16.4 -- a known variable star
23:32:32.78 +50:43:05.5 -- not a known variable star
23:32:42.99 +56:50:33.3 -- not a known variable star
23:32:52.38 +55:31:51.8 -- not a known variable star
23:33:00.05 +50:29:51.5 -- not a known variable star
23:33:30.65 +56:13:29.9 -- not a known variable star
23:33:32.06 +56:43:59.2 -- not a known variable star
23:33:32.89 +50:54:47.0 -- not a known variable star
23:33:33.34 +55:13:44.8 -- not a known variable star
23:33:42.08 +56:14:35.8 -- not a known variable star
23:33:49.78 +57:33:02.7 -- not a known variable star
23:34:20.01 +55:18:49.2 -- not a known variable star
23:34:59.30 +50:35:48.5 -- not a known variable star
23:35:02.39 +56:30:46.6 -- not a known variable star
23:35:02.95 +55:49:49.2 -- not a known variable star
23:35:13.50 +50:52:41.8 -- not a known variable star
23:35:17.11 +55:37:18.2 -- a known variable star
23:35:58.13 +53:28:50.4 -- not a known variable star
23:36:06.73 +56:16:10.0 -- not a known variable star
23:36:37.82 +55:28:14.6 -- not a known variable star
23:36:42.72 +53:33:03.3 -- not a known variable star
23:36:56.67 +55:34:18.8 -- not a known variable star
23:37:01.99 +51:37:44.4 -- not a known variable star
23:37:26.49 +55:33:35.8 -- a known variable star
23:37:32.63 +51:50:44.1 -- not a known variable star
23:37:38.39 +56:52:47.2 -- not a known variable star
23:38:16.13 +56:01:54.5 -- not a known variable star
23:38:19.66 +50:33:19.2 -- not a known variable star
23:38:55.08 +51:35:15.9 -- not a known variable star
23:39:23.46 +56:29:07.7 -- not a known variable star
23:40:10.84 +53:34:46.8 -- not a known variable star
23:40:23.01 +53:45:30.1 -- not a known variable star
23:41:15.06 +56:15:32.9 -- not a known variable star
23:42:28.80 +53:37:20.5 -- not a known variable star
23:42:54.61 +53:06:01.8 -- a known variable star
23:43:06.00 +52:01:14.3 -- not a known variable star
23:43:26.63 +51:45:07.9 -- a known variable star
23:43:27.06 +52:27:01.4 -- not a known variable star
23:43:30.06 +50:56:49.9 -- not a known variable star
23:43:35.64 +50:08:35.6 -- not a known variable star
23:43:35.72 +53:16:14.1 -- not a known variable star
23:44:09.71 +53:03:31.9 -- not a known variable star
23:45:59.31 +54:45:21.6 -- not a known variable star
23:46:02.67 +53:33:15.4 -- not a known variable star
23:47:34.99 +52:37:51.9 -- not a known variable star
23:48:03.24 +51:53:54.3 -- not a known variable star
23:51:15.90 +52:09:19.5 -- not a known variable star
23:52:37.81 +56:44:34.2 -- a known variable star
23:55:38.47 +52:35:17.7 -- not a known variable star
23:55:49.34 +53:44:23.7 -- not a known variable star
23:56:27.04 +53:44:46.4 -- not a known variable star
23:57:05.80 +52:12:20.7 -- not a known variable star
23:58:26.85 +51:26:16.7 -- not a known variable star
23:58:48.31 +53:26:35.2 -- not a known variable star
Found 99 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
111 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 111 (excluding asteroids and hot pixels, 99 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)2461215.83007665 -observatory V36
07:46:12.16 +20:24:28.4 Mercury (1.2mag)
09:00:59.22 +18:59:26.3 Venus (-4.0mag)
03:36:49.16 +18:58:56.0 Mars (1.3mag)
08:02:18.50 +20:54:25.1 Jupiter (-1.8mag)
00:53:19.68 +03:09:19.7 Saturn (0.8mag)
04:03:55.22 +20:35:58.1 Uranus (5.8mag)
00:16:50.42 +00:20:25.0 Neptune (7.8mag)
20:32:16.71 -23:11:02.2 Pluto (14.5mag)
13:43:03.38 -16:07:35.7 Moon (-11.1mag)
-rw-r--r-- 1 apache apache 362 Jun 24 04:19 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461215.83007665:
08:02:24.02 +20:54:08.5 Io (6.2mag)
08:02:18.14 +20:54:25.4 Europa (6.3mag)
08:02:17.87 +20:54:32.4 Ganymede (5.6mag)
08:02:42.39 +20:53:03.1 Callisto (6.9mag)
08:01:39.42 +20:33:16.0 Himalia (15.6mag)
08:02:22.64 +20:54:11.3 Thebe (16.6mag)
08:01:13.62 +20:42:18.2 Elara (17.6mag)
08:05:15.00 +20:57:17.2 Pasiphae (17.8mag)
08:08:07.93 +20:57:32.9 Carme (18.9mag)
00:53:10.02 +03:09:13.8 Titan (8.6mag)
00:53:24.79 +03:09:13.2 Rhea (9.9mag)
00:53:23.99 +03:11:20.3 Iapetus (11.3mag)
00:53:08.23 +03:09:38.8 Hyperion (14.6mag)
00:53:41.55 +03:08:54.9 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jun 24 04:20 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461215.83007665:
17:30:38.03 -35:17:44.0 JWST
15:48:21.65 +51:40:42.9 Chandra
22:27:46.63 +57:00:45.1 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jun 24 04:19 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461215.83007665 -observatory V36
18:31:02.60 -33:41:40.7 13.7mag P/2010 H2 (Vales)
06:09:33.70 -67:59:53.5 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
05:55:01.91 +32:11:34.3 17.6mag C/2017 K2 (PANSTARRS)
17:08:25.67 +15:55:33.4 17.9mag C/2021 G2 (ATLAS)
23:51:18.74 -27:54:54.0 15.6mag P/2021 N1 (ZTF)
23:07:34.26 +32:05:45.1 17.2mag C/2022 E2 (ATLAS)
05:53:37.36 +27:00:33.2 16.6mag C/2022 N2 (PANSTARRS)
09:42:04.04 +30:28:05.4 16.7mag C/2022 QE78 (ATLAS)
08:59:44.53 +04:34:53.3 17.8mag C/2022 R6 (PANSTARRS)
18:17:31.21 +21:40:38.1 17.8mag C/2023 A3 (Tsuchinshan-ATLAS)
15:14:25.80 -11:06:49.6 17.6mag P/2023 B1 (PANSTARRS)
22:05:20.55 +67:20:29.5 17.8mag C/2023 H5 (Lemmon)
17:06:27.66 -08:21:52.4 13.7mag C/2023 R1 (PANSTARRS)
13:19:13.74 +79:10:16.6 18.0mag C/2023 X2 (Lemmon)
07:34:16.34 +64:55:54.8 17.8mag C/2024 A1 (ATLAS)
07:10:56.83 +29:04:33.6 14.2mag C/2024 E1 (Wierzchos)
15:25:33.77 +14:40:31.4 17.5mag C/2024 G6 (ATLAS)
19:59:36.68 +35:40:57.8 13.9mag C/2024 J3 (ATLAS)
22:01:17.26 +43:20:13.4 18.0mag C/2024 R4 (PANSTARRS)
04:34:06.97 -14:42:07.5 15.9mag C/2024 T5 (ATLAS)
06:20:42.27 +31:44:30.3 17.9mag C/2025 J1 (Borisov)
11:32:17.48 +51:45:21.2 18.0mag C/2025 L1 (ATLAS)
07:01:38.25 -11:42:21.2 15.4mag C/2025 R3 (PANSTARRS)
09:38:50.27 +23:00:13.6 17.8mag C/2025 V2 (Rankin)
12:40:44.55 +04:28:09.4 17.1mag C/2025 Y1 (ATLAS)
17:38:09.87 +77:55:51.3 17.6mag C/2026 A2 (Bok)
02:26:12.87 +44:26:26.1 16.4mag C/2026 B2 (Sun-Gao)
11:16:44.22 +01:06:47.0 16.7mag A/2026 E1
20:52:20.10 -10:40:35.0 7.9mag 10P/Tempel
11:06:49.23 -01:18:58.8 16.1mag 29P/Schwassmann-Wachmann
03:36:26.51 +27:42:21.7 17.8mag 47P/Ashbrook-Jackson
09:34:20.02 +19:00:17.2 17.0mag 63P/Wild
00:39:20.95 -05:31:12.0 15.6mag 65P/Gunn
07:35:51.58 +34:25:18.9 17.4mag 76P/West-Kohoutek-Ikemura
03:48:24.09 +19:00:09.3 13.8mag 78P/Gehrels
01:53:49.25 +08:03:14.2 15.9mag 88P/Howell
05:46:13.19 +30:57:16.1 15.4mag 93P/Lovas
03:30:27.66 +29:50:45.5 17.2mag 114P/Wiseman-Skiff
07:29:31.15 +32:09:49.0 15.4mag 123P/West-Hartley
10:18:46.54 +07:48:16.0 16.7mag 124P/Mrkos
04:25:38.22 +20:11:06.7 16.3mag 128P/Shoemaker-Holt
05:05:25.10 +19:36:45.1 17.8mag 131P/Mueller
07:02:07.16 +16:15:51.8 16.7mag 141P/Machholz
07:06:08.53 +17:45:59.4 16.6mag 141P-A/Machholz
06:11:01.68 +17:25:26.3 13.5mag 141P-D/Machholz
03:08:22.15 -22:40:44.2 16.2mag 161P/Hartley-IRAS
04:36:11.69 +29:38:03.2 15.1mag 162P/SidingSpring
19:29:32.13 +07:14:47.4 15.9mag 169P/NEAT
01:00:59.68 +05:22:10.9 17.7mag 220P/McNaught
16:41:28.49 -08:04:27.4 16.7mag 235P/LINEAR
08:10:42.19 +34:35:31.9 17.7mag 240P/NEAT
20:43:17.29 -45:29:45.8 18.0mag 259P/Garradd
01:15:16.94 +04:39:23.6 16.0mag 260P/McNaught
04:49:36.24 +35:04:14.4 17.5mag 295P/LINEAR
15:09:19.07 +07:17:33.4 17.5mag 391P/Kowalski
08:20:31.00 +20:16:07.0 17.9mag 450P/LONEOS
07:26:11.99 +40:29:59.1 17.9mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Jun 24 04:19 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
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:32.95 -68:48:30.00 ASASSN-26no 2026-05-24 8.41
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.18 +22:02:03.40 AT2026lxf 2026-05-8.07 13.94
10:23:49.41 -20:57:25.30 ASASSN-26df 2026-05-8.21 16.52
22:14:40.56 +05:04:51.60 2026lda 2026-05-7.56 16.2
21:35:33.81 -14:05:16.30 ASASSN-26de 2026-05-6.29 14.51
16:21:49.13 -61:36:14.60 ASASSN-26dd 2026-05-5.15 15.93
14:26:40.22 -24:48:37.50 AT2026lig 2026-05-4.27 14.63
13:17:51.04 +30:25:13.50 SN2026kcp 2026-05-4.46 16.43
11:27:55.57 -13:38:56.90 SN2026kza 2026-05-1.08 15.59
22:28:27.10 +30:17:54.30 SN 2026fov 2026-04-29.6 14.36
21:00:10.71 -32:17:03.90 AT2026kis 2026-04-27.36 16.15
14:32:57.37 -58:13:26.40 ASASSN-26dc 2026-04-27.27 13.42
15:32:05.35 -43:54:34.60 ASASSN-26db 2026-04-27.37 16.06
16:34:34.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.52 -16:06:06.00 ASASSN-26cz 2026-04-22.28 16.29
20:49:13.39 +25:17:59.20 2026-06-15.39 15.93
13:45:02.03 +15:17:14.50 ASASSN-26cy 2026-04-21.27 15.78
13:20:52.22 -35:57:03.60 AT2026jcm 2026-04-19.01 16.65
13:36:15.66 -36:53:48.40 SN 2026iqy 2026-04-18.92 17.31
06:34:01.33 -40:07:34.00 ASASSN-26cx 2026-04-19.07 16.16
23:33:57.97 -45:12:11.90 SN 2026idu 2026-04-19.41 15.9
12:10:50.92 +66:55:31.20 SN 2026icv 2026-04-17.14 16.03
21:36:59.06 -60:43:35.90 ASASSN-26cv 2026-04-17.35 -1.18
08:13:26.26 -27:07:30.50 ASASSN-26cw 2026-04-17.07 -1.01
14:49:14.01 -27:29:20.10 ASASSN-26cu 2026-04-16.29 -2.7
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
20:49:13.39 +25:17:59.20 2026-06-15.39 15.93
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.14 13.64
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:35.90 ASASSN-26co 2026-04-7.15 14.93
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.68 -22:39:32.70 ASASSN-26cm 2026-04-4.27 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
-rw-r--r-- 1 apache apache 5.6K Jun 24 04:19 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
00:43:35.02 +41:46:28.0 PNV J00433502+4146280 2026-04-23.056 15.9mag
00:42:55.64 +41:14:12.2 PNV J00425564+4114122 2026-04-24.042 16.2mag
21:14:03.38 +56:46:44.1 TCP J21140338+5646441 2026-05-05.3534 16.7mag
15:03:05.19 +22:02:04.1 TCP J15030519+2202041 2026-05-08.3260 13.9mag
07:15:18.25 +47:53:16.7 TCP J07151825+4753167 2026-05-09.1599 14.4mag
16:00:18.44 -22:30:10.6 TCP J16001844-2230106 2026-05-09.6135 13.3mag
00:42:47.45 +41:16:58.5 PNV J00424745+4116585 2026-05-10.030 16.8mag
09:55:02.89 +69:02:13.8 PNV J09550289+6902138 2026-05-18.925 20.7mag
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
-rw-r--r-- 1 apache apache 189K Jun 24 04:19 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
23:01:17.643 -11:26:13.47 AT 2026phu 2026-06-10.46 19.7938
15:34:01.460 +32:14:21.95 AT 2026pht 2026-06-03.80 20.63
13:52:20.180 +26:36:28.29 AT 2026phs 2026-06-03.76 21.08
19:02:22.130 +47:04:24.55 AT 2026phr 2026-04-16.90 20.76
15:04:03.130 +51:40:36.19 AT 2026phq 2026-06-08.80 20.69
14:59:06.740 +49:19:47.55 AT 2026php 2026-06-03.82 21.24
15:25:14.430 +52:47:19.27 AT 2026pho 2026-06-03.82 20.69
15:32:10.430 +55:31:52.79 AT 2026phn 2026-06-03.82 20.55
15:05:31.070 +54:01:58.04 AT 2026phm 2026-06-03.82 20.97
15:26:20.470 +34:15:03.49 AT 2026phl 2026-06-03.81 21.22
15:30:53.386 +36:56:04.14 AT 2026phk 2026-06-03.81 20.62
15:53:00.067 +39:11:14.03 AT 2026phj 2026-06-03.81 20.35
15:16:47.570 +42:26:03.51 AT 2026phi 2026-06-03.80 21.4
15:30:43.080 +44:43:29.89 AT 2026phh 2026-06-03.80 20.99
15:34:17.400 +45:38:16.24 AT 2026phg 2026-06-03.80 20.99
15:36:56.850 +49:52:01.56 AT 2026phf 2026-06-03.80 21.12
17:59:56.980 +54:59:32.40 AT 2026phe 2026-05-08.79 21.25
15:00:58.510 +55:15:48.71 AT 2026phd 2026-05-03.81 21.36
13:50:35.500 +00:18:35.99 AT 2026phc 2026-06-03.69 21.88
13:39:32.410 +05:32:10.98 AT 2026phb 2026-06-02.76 20.21
-rw-r--r-- 1 apache apache 30K Jun 24 04:19 tns_transients_list.txt
