This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.18 23:11:50.83 +56:02:36.8
109.29442 -4.16858 galactic Cas Second-epoch detections are separated by 3.6" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2008809839892102016 | 23:11:49.19 +56:02:21.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:11:50.83 +56:02:36.8: 14.47 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:11:50.83 +56:02:36.8: 14.40 +/- 0.20 detection
Forced photometry reference-image weighted average: 14.43 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 11 50.83 +56 02 36.8 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2008809839892102016,2461234.7877,11.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2008809839892102016 20260713.2877 11.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.59 00:02:20.47 +54:07:58.1
115.70510 -8.04860 galactic Cas Second-epoch detections are separated by 7.4" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420317426719370368 | 00:02:25.24 +54:08:06.4 (Gaia DR3) | DSCT/GDOR (local) | 0.373683000000 (local) | Gaia3var=VARIABLE SpType: A3 1927AnHar.100...33C HD 236281
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:02:20.47 +54:07:58.1: 14.51 +/- 0.16 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:02:20.47 +54:07:58.1: 14.78 +/- 0.22 detection
Forced photometry reference-image weighted average: 14.61 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 02 20.47 +54 07 58.1 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420317426719370368,2461234.7877,11.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420317426719370368 20260713.2877 11.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.88 23:34:47.85 +54:35:22.1
111.89419 -6.63153 galactic Cas Second-epoch detections are separated by 4.5" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:47.85 +54:35:22.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:34:47.85 +54:35:22.1: 15.31 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:34:47.85 +54:35:22.1: 15.24 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.24 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 34 47.85 +54 35 22.1 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
target,2461234.7877,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
target 20260713.2877 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 07 13.2877 2461234.7877 10.03 00:09:30.37 +51:35:57.4
116.32669 -10.73389 galactic Cas Second-epoch detections are separated by 7.5" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:30.37 +51:35:57.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:09:30.37 +51:35:57.4: 12.62 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:09:30.37 +51:35:57.4: 12.68 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.65 +/- 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 07 13.2877* 00 09 30.37 +51 35 57.4 10.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,2461234.7877,10.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 20260713.2877 10.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 23:19:08.06 +55:29:03.6
110.04892 -5.06163 galactic Cas Second-epoch detections are separated by 8.2" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.7876+55.4824 | 23:19:06.31 +55:29:15.0 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:19:08.06 +55:29:03.6: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:19:08.06 +55:29:03.6: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 19 08.06 +55 29 03.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J349.7876+55.4824,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J349.7876+55.4824 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.69 00:04:26.60 +58:12:16.8
116.75727 -4.10257 galactic Cas Second-epoch detections are separated by 5.6" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 422693810640834176 | 00:04:23.67 +58:12:08.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:04:26.60 +58:12:16.8: 13.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:04:26.60 +58:12:16.8: 13.34 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 04 26.60 +58 12 16.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 422693810640834176,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422693810640834176 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.62 23:36:22.71 +56:42:22.7
112.72688 -4.67089 galactic Cas Second-epoch detections are separated by 7.3" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:36:22.71 +56:42:22.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:36:22.71 +56:42:22.7: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:36:22.71 +56:42:22.7: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 36 22.71 +56 42 22.7 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 23:14:00.20 +53:48:48.2
108.74886 -6.35362 galactic Cas Second-epoch detections are separated by 7.2" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:14:00.20 +53:48:48.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:14:00.20 +53:48:48.2: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:14:00.20 +53:48:48.2: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 14 00.20 +53 48 48.2 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:00:21.12 +54:41:00.8
115.52685 -7.45203 galactic Cas Second-epoch detections are separated by 3.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:21.12 +54:41:00.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:00:21.12 +54:41:00.8: 13.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:00:21.12 +54:41:00.8: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 00 21.12 +54 41 00.8 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 23:21:55.10 +52:18:41.4
109.33035 -8.18019 galactic And Second-epoch detections are separated by 7.1" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:55.10 +52:18:41.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:21:55.10 +52:18:41.4: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:21:55.10 +52:18:41.4: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 21 55.10 +52 18 41.4 12.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:09:02.89 +54:34:36.0
116.75568 -7.78596 galactic Cas Second-epoch detections are separated by 4.8" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:02.89 +54:34:36.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:09:02.89 +54:34:36.0: 13.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:09:02.89 +54:34:36.0: 13.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 09 02.89 +54 34 36.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.86 00:14:03.80 +54:34:33.6
117.48022 -7.89965 galactic Cas Second-epoch detections are separated by 8.2" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:14:03.80 +54:34:33.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:14:03.80 +54:34:33.6: 13.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:14:03.80 +54:34:33.6: 13.58 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 14 03.80 +54 34 33.6 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:00:38.27 +54:12:08.1
115.47179 -7.93204 galactic Cas Second-epoch detections are separated by 4.7" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:38.27 +54:12:08.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:00:38.27 +54:12:08.1: 13.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:00:38.27 +54:12:08.1: 13.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 07 13.2877* 00 00 38.27 +54 12 08.1 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:05:47.78 +55:40:34.2
116.48384 -6.62312 galactic Cas Second-epoch detections are separated by 4.2" and 1.3 pix
The object was found in VSX15" Gaia DR3 420834403342447488
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.660 G 13.690 G A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:05:47.78 +55:40:34.2: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:05:47.78 +55:40:34.2: 13.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 07 13.2877* 00 05 47.78 +55 40 34.2 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 420834403342447488,2461234.7877,12.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420834403342447488 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.61 00:05:30.68 +57:48:28.6
116.82533 -4.51825 galactic Cas Second-epoch detections are separated by 2.4" and 1.2 pix
The object was found in VSX17" Gaia DR3 422656191030293120
Type: ROT
# Max. Min./Amp. JD0 Period
14.140 G 14.170 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:05:30.68 +57:48:28.6: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:05:30.68 +57:48:28.6: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 05 30.68 +57 48 28.6 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422656191030293120,2461234.7877,12.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 422656191030293120 20260713.2877 12.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:27:51.39 +55:18:50.6
119.55281 -7.40290 galactic Cas Second-epoch detections are separated by 2.6" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:27:51.39 +55:18:50.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:27:51.39 +55:18:50.6: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:27:51.39 +55:18:50.6: 13.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 07 13.2877* 00 27 51.39 +55 18 50.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.69 00:26:53.60 +56:55:17.2
119.57021 -5.79001 galactic Cas Second-epoch detections are separated by 7.0" and 1.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:26:53.60 +56:55:17.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:53.60 +56:55:17.2: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:53.60 +56:55:17.2: 13.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 07 13.2877* 00 26 53.60 +56 55 17.2 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.80 00:00:24.29 +51:44:10.1
114.94077 -10.34204 galactic Cas Second-epoch detections are separated by 6.0" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:24.29 +51:44:10.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:00:24.29 +51:44:10.1: 13.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:00:24.29 +51:44:10.1: 13.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 07 13.2877* 00 00 24.29 +51 44 10.1 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.63 00:22:53.92 +57:35:32.3
119.10014 -5.06696 galactic Cas Second-epoch detections are separated by 4.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:53.92 +57:35:32.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:53.92 +57:35:32.3: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:53.92 +57:35:32.3: 13.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 07 13.2877* 00 22 53.92 +57 35 32.3 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,2461234.7877,12.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 00:29:01.78 +57:02:14.0
119.87214 -5.70134 galactic Cas Second-epoch detections are separated by 5.0" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:29:01.78 +57:02:14.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:29:01.78 +57:02:14.0: 13.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:29:01.78 +57:02:14.0: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 29 01.78 +57 02 14.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.78 00:22:47.82 +52:41:21.7
118.53287 -9.93758 galactic Cas Second-epoch detections are separated by 8.3" and 2.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:47.82 +52:41:21.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:47.82 +52:41:21.7: 13.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:47.82 +52:41:21.7: 13.57 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 22 47.82 +52 41 21.7 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.44 23:58:32.99 +58:03:58.5
115.96535 -4.08834 galactic Cas Second-epoch detections are separated by 5.6" and 2.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 J359.6280+58.0548 | 23:58:32.99 +58:03:58.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input) J-Ks=0.861+/-0.035 (M)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:58:32.99 +58:03:58.5: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:58:32.99 +58:03:58.5: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 58 32.99 +58 03 58.5 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J359.6280+58.0548,2461234.7877,12.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.6280+58.0548 20260713.2877 12.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.72 23:55:08.32 +52:30:39.7
114.30339 -9.41498 galactic Cas Second-epoch detections are separated by 8.2" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:08.32 +52:30:39.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:55:08.32 +52:30:39.7: 13.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:55:08.32 +52:30:39.7: 13.64 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 55 08.32 +52 30 39.7 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.54 23:53:12.90 +54:00:38.0
114.35733 -7.88904 galactic Cas Second-epoch detections are separated by 8.4" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:53:12.90 +54:00:38.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:53:12.90 +54:00:38.0: 13.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:53:12.90 +54:00:38.0: 13.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 07 13.2877* 23 53 12.90 +54 00 38.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:31:21.39 +57:06:30.6
120.19474 -5.65649 galactic Cas Second-epoch detections are separated by 5.0" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:21.39 +57:06:30.6 (user input) | T | P | (position from user input) SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:21.39 +57:06:30.6: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:21.39 +57:06:30.6: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 21.39 +57 06 30.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.39 23:18:54.84 +53:01:44.0
109.15086 -7.34927 galactic And Second-epoch detections are separated by 7.0" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:18:54.84 +53:01:44.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:18:54.84 +53:01:44.0: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:18:54.84 +53:01:44.0: 13.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 07 13.2877* 23 18 54.84 +53 01 44.0 12.4 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,2461234.7877,12.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 20260713.2877 12.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.68 00:31:05.01 +55:56:06.4
120.06387 -6.82325 galactic Cas Second-epoch detections are separated by 4.4" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.7615+55.9315 | 00:31:05.01 +55:56:06.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:05.01 +55:56:06.4: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:05.01 +55:56:06.4: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 05.01 +55 56 06.4 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
ATO J007.7615+55.9315,2461234.7877,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.7615+55.9315 20260713.2877 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.52 00:26:37.65 +56:47:25.0
119.52117 -5.91708 galactic Cas Second-epoch detections are separated by 4.5" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.6452+56.7887 | 00:26:37.65 +56:47:25.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:37.65 +56:47:25.0: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:37.65 +56:47:25.0: 13.52 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 26 37.65 +56 47 25.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J006.6452+56.7887,2461234.7877,12.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J006.6452+56.7887 20260713.2877 12.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:17:32.43 +54:36:14.8
117.98776 -7.94191 galactic Cas Second-epoch detections are separated by 7.8" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 419791860161992960 | 00:17:32.17 +54:36:57.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:17:32.43 +54:36:14.8: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:17:32.43 +54:36:14.8: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 17 32.43 +54 36 14.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 419791860161992960,2461234.7877,12.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 419791860161992960 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.53 00:23:32.01 +57:49:18.3
119.21001 -4.84820 galactic Cas Second-epoch detections are separated by 5.0" and 1.0 pix
The object was found in VSX12" Gaia DR3 422087399924551040
Type: ROT
# Max. Min./Amp. JD0 Period
13.920 G 13.940 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:23:32.01 +57:49:18.3: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:23:32.01 +57:49:18.3: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 23 32.01 +57 49 18.3 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422087399924551040,2461234.7877,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422087399924551040 20260713.2877 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.54 00:22:07.15 +57:36:53.0
118.99852 -5.03294 galactic Cas Second-epoch detections are separated by 5.4" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:07.15 +57:36:53.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:07.15 +57:36:53.0: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:07.15 +57:36:53.0: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 22 07.15 +57 36 53.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.54 23:28:43.23 +54:29:16.1
111.01812 -6.45933 galactic Cas Second-epoch detections are separated by 5.8" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:43.23 +54:29:16.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:28:43.23 +54:29:16.1: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:28:43.23 +54:29:16.1: 13.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 07 13.2877* 23 28 43.23 +54 29 16.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.46 00:10:31.02 +57:26:23.1
117.42602 -4.99389 galactic Cas Second-epoch detections are separated by 3.8" and 1.2 pix
The object was found in VSX12" Gaia DR3 422438522089312384
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.170 G 14.240 G 0.037056500000 A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:10:31.02 +57:26:23.1: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:10:31.02 +57:26:23.1: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 10 31.02 +57 26 23.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422438522089312384,2461234.7877,12.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 422438522089312384 20260713.2877 12.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 07 13.2877 2461234.7877 12.52 00:31:51.93 +56:59:39.7
120.25522 -5.77563 galactic Cas Second-epoch detections are separated by 6.7" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:51.93 +56:59:39.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:51.93 +56:59:39.7: 13.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:51.93 +56:59:39.7: 13.34 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 51.93 +56 59 39.7 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.45 23:31:07.69 +53:45:00.8
111.12380 -7.27017 galactic Cas Second-epoch detections are separated by 6.7" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:07.69 +53:45:00.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:31:07.69 +53:45:00.8: 13.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:31:07.69 +53:45:00.8: 13.57 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 31 07.69 +53 45 00.8 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.44 00:29:46.24 +58:00:57.8
120.05599 -4.73465 galactic Cas Second-epoch detections are separated by 5.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:29:46.24 +58:00:57.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:29:46.24 +58:00:57.8: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:29:46.24 +58:00:57.8: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 29 46.24 +58 00 57.8 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 20260713.2877 12.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.46 00:15:00.86 +57:44:49.1
118.07018 -4.78054 galactic Cas Second-epoch detections are separated by 3.0" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:00.86 +57:44:49.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:15:00.86 +57:44:49.1: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:15:00.86 +57:44:49.1: 13.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 07 13.2877* 00 15 00.86 +57 44 49.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.32 23:28:10.65 +54:38:43.2
110.99330 -6.28497 galactic Cas Second-epoch detections are separated by 6.7" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:10.65 +54:38:43.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:28:10.65 +54:38:43.2: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:28:10.65 +54:38:43.2: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 28 10.65 +54 38 43.2 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.37 00:11:07.27 +54:58:20.4
117.11765 -7.44363 galactic Cas Second-epoch detections are separated by 6.1" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ASASSN-V J001111.87+545825.6 | 00:11:11.88 +54:58:25.4 (Gaia DR3) | L (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:11:07.27 +54:58:20.4: 13.51 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:11:07.27 +54:58:20.4: 13.56 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.51 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 11 07.27 +54 58 20.4 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J001111.87+545825.6,2461234.7877,12.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J001111.87+545825.6 20260713.2877 12.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.26 00:01:12.90 +55:16:19.1
115.76583 -6.89945 galactic Cas Second-epoch detections are separated by 6.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J000.3150+55.2734 | 00:01:12.90 +55:16:19.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input) SpType: G0 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:01:12.90 +55:16:19.1: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:01:12.90 +55:16:19.1: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 01 12.90 +55 16 19.1 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.3150+55.2734,2461234.7877,12.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.3150+55.2734 20260713.2877 12.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.46 00:30:00.15 +57:34:39.1
120.04996 -5.17422 galactic Cas Second-epoch detections are separated by 5.1" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421853994218224000 | 00:29:55.82 +57:34:19.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A1IV (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:00.15 +57:34:39.1: 13.65 +/- 0.36 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:00.15 +57:34:39.1: 13.37 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.65 +/- 0.36
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 00.15 +57 34 39.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421853994218224000,2461234.7877,12.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 421853994218224000 20260713.2877 12.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 07 13.2877 2461234.7877 12.52 00:01:49.79 +55:38:01.1
115.92246 -6.56151 galactic Cas Second-epoch detections are separated by 4.0" and 1.2 pix
The object was found in VSX19" ZTF J000148.68+553744.2
Type: BY
# Max. Min./Amp. JD0 Period
15.756 g Y 0.042 g 2458475.64270 8.646354800000
NOTE: the measured mag 12.52 is inconsistent with the record above (maximum 15.71), and the brighter VSX variable ZTF J000148.25+553822.1 at 25" may be the actual counterpart.
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:01:49.79 +55:38:01.1: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:01:49.79 +55:38:01.1: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 01 49.79 +55 38 01.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J000148.68+553744.2,2461234.7877,12.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J000148.68+553744.2 20260713.2877 12.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.46 00:26:08.70 +57:20:45.6
119.51007 -5.35761 galactic Cas Second-epoch detections are separated by 3.2" and 1.9 pix
The object was found in VSX12" Gaia DR3 421880760455425152
Type: ROT
# Max. Min./Amp. JD0 Period
14.140 G 14.180 G 4.676060000000 G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:08.70 +57:20:45.6: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:08.70 +57:20:45.6: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 26 08.70 +57 20 45.6 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421880760455425152,2461234.7877,12.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 421880760455425152 20260713.2877 12.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 07 13.2877 2461234.7877 12.42 23:38:26.34 +53:46:04.4
112.17029 -7.57162 galactic Cas Second-epoch detections are separated by 4.7" and 1.0 pix
The object was found in VSX 7" Gaia DR3 1994114802568115968
Type: ROT
# Max. Min./Amp. JD0 Period
15.190 G 15.250 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:38:26.34 +53:46:04.4: 13.72 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:38:26.34 +53:46:04.4: 13.39 +/- 0.30 detection
Forced photometry reference-image weighted average: 13.55 +/- 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 07 13.2877* 23 38 26.34 +53 46 04.4 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1994114802568115968,2461234.7877,12.42,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1994114802568115968 20260713.2877 12.42CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.39 00:15:59.17 +54:40:40.7
117.77293 -7.83827 galactic Cas Second-epoch detections are separated by 7.8" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J004.0038+54.6796 | 00:15:58.92 +54:40:55.0 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE SpType: K1 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:15:59.17 +54:40:40.7: 13.81 +/- 0.35 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:15:59.17 +54:40:40.7: 13.37 +/- 0.29 detection
Forced photometry reference-image weighted average: 13.55 +/- 0.23
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 15 59.17 +54 40 40.7 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J004.0038+54.6796,2461234.7877,12.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
ATO J004.0038+54.6796 20260713.2877 12.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.19 23:19:46.40 +53:15:48.8
109.35550 -7.17473 galactic Cas Second-epoch detections are separated by 8.5" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:46.40 +53:15:48.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:19:46.40 +53:15:48.8: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:19:46.40 +53:15:48.8: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 19 46.40 +53 15 48.8 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
target,2461234.7877,12.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 20260713.2877 12.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.19 23:29:01.15 +52:35:57.0
110.45806 -8.26500 galactic Cas Second-epoch detections are separated by 4.2" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:01.15 +52:35:57.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:29:01.15 +52:35:57.0: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:29:01.15 +52:35:57.0: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 29 01.15 +52 35 57.0 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
target,2461234.7877,12.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 20260713.2877 12.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.33 23:29:58.28 +51:51:22.8
110.36132 -9.01594 galactic Cas Second-epoch detections are separated by 2.8" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J352.5091+51.8527 | 23:29:58.28 +51:51:22.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:29:58.28 +51:51:22.8: 13.54 +/- 0.28 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:29:58.28 +51:51:22.8: 13.57 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.54 +/- 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 07 13.2877* 23 29 58.28 +51 51 22.8 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.5091+51.8527,2461234.7877,12.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J352.5091+51.8527 20260713.2877 12.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.00 23:22:20.89 +51:22:45.3
109.07100 -9.07894 galactic And Second-epoch detections are separated by 7.6" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:20.89 +51:22:45.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:22:20.89 +51:22:45.3: 13.35 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:22:20.89 +51:22:45.3: 13.40 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.35 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 22 20.89 +51 22 45.3 12.0 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,2461234.7877,12.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.31 23:43:39.45 +56:10:00.2
113.54986 -5.46538 galactic Cas Second-epoch detections are separated by 4.1" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:39.45 +56:10:00.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:43:39.45 +56:10:00.2: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:43:39.45 +56:10:00.2: 13.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 07 13.2877* 23 43 39.45 +56 10 00.2 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.21 00:32:20.47 +57:15:05.4
120.33938 -5.52409 galactic Cas Second-epoch detections are separated by 5.8" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:20.47 +57:15:05.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:20.47 +57:15:05.4: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:20.47 +57:15:05.4: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 20.47 +57 15 05.4 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
target,2461234.7877,12.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 20260713.2877 12.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.15 00:13:17.61 +57:35:53.8
117.82014 -4.89439 galactic Cas Second-epoch detections are separated by 4.6" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ZTF J001319.99+573519.2 | 00:13:18.10 +57:35:25.4 (Gaia DR3) | EW (local) | 0.359611400000 (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:13:17.61 +57:35:53.8: 13.64 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:13:17.61 +57:35:53.8: 13.49 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.64 +/- 0.31
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 13 17.61 +57 35 53.8 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
ZTF J001319.99+573519.2,2461234.7877,12.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
ZTF J001319.99+573519.2 20260713.2877 12.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.18 23:57:52.76 +56:48:31.4
115.61744 -5.30048 galactic Cas Second-epoch detections are separated by 4.9" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J359.4873+56.8095 | 23:57:52.76 +56:48:31.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:57:52.76 +56:48:31.4: 13.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:57:52.76 +56:48:31.4: 13.20 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 57 52.76 +56 48 31.4 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
ATO J359.4873+56.8095,2461234.7877,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.4873+56.8095 20260713.2877 12.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.07 23:40:14.57 +54:54:05.9
112.74185 -6.55536 galactic Cas Second-epoch detections are separated by 4.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:40:14.57 +54:54:05.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:40:14.57 +54:54:05.9: 13.28 +/- 0.22 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:40:14.57 +54:54:05.9: 12.93 +/- 0.21 detection
Forced photometry reference-image weighted average: 13.09 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 40 14.57 +54 54 05.9 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,2461234.7877,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
target 20260713.2877 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 07 13.2877 2461234.7877 12.06 23:24:52.43 +55:56:49.5
110.96980 -4.90112 galactic Cas Second-epoch detections are separated by 6.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:52.43 +55:56:49.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:24:52.43 +55:56:49.5: 12.98 +/- 0.17 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:24:52.43 +55:56:49.5: 12.93 +/- 0.21 detection
Forced photometry reference-image weighted average: 12.96 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 24 52.43 +55 56 49.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
target,2461234.7877,12.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.85 23:18:42.24 +52:03:01.6
108.77182 -8.25334 galactic And Second-epoch detections are separated by 5.9" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:18:42.24 +52:03:01.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:18:42.24 +52:03:01.6: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:18:42.24 +52:03:01.6: 13.28 +/- 0.30 detection
Forced photometry reference-image weighted average: 13.28 +/- 0.30
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 18 42.24 +52 03 01.6 11.8 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,2461234.7877,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 20260713.2877 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 07 13.2877 2461234.7877 12.21 00:17:55.23 +57:40:47.7
118.44691 -4.89966 galactic Cas Second-epoch detections are separated by 3.4" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:17:55.23 +57:40:47.7 (user input) | T | P | (position from user input) SpType: F2 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:17:55.23 +57:40:47.7: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:17:55.23 +57:40:47.7: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 17 55.23 +57 40 47.7 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
target,2461234.7877,12.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 20260713.2877 12.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.19 00:00:33.12 +54:57:57.6
115.61169 -7.18088 galactic Cas Second-epoch detections are separated by 5.2" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420381026595451264 | 00:00:30.33 +54:57:21.4 (Gaia DR3) | ROT (local) | (local) | Gaia3var=NOT_AVAILABLE SpType: G4 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:00:33.12 +54:57:57.6: 13.64 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:00:33.12 +54:57:57.6: 13.55 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.64 +/- 0.30
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 00 33.12 +54 57 57.6 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
Gaia DR3 420381026595451264,2461234.7877,12.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420381026595451264 20260713.2877 12.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.89 23:13:21.74 +54:10:57.7
108.79842 -5.97569 galactic Cas Second-epoch detections are separated by 4.8" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:13:21.74 +54:10:57.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:13:21.74 +54:10:57.7: 13.49 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:13:21.74 +54:10:57.7: 13.09 +/- 0.27 detection
Forced photometry reference-image weighted average: 13.27 +/- 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 07 13.2877* 23 13 21.74 +54 10 57.7 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
target,2461234.7877,11.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 20260713.2877 11.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.08 00:28:37.18 +57:13:22.8
119.83290 -5.51138 galactic Cas Second-epoch detections are separated by 4.0" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421822520696970496 | 00:28:33.81 +57:13:25.5 (Gaia DR3) | ROT (local) | 1.040080000000 (local) | Gaia3var=NOT_AVAILABLE SpType: F3 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:37.18 +57:13:22.8: 13.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:37.18 +57:13:22.8: 13.22 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 37.18 +57 13 22.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 421822520696970496,2461234.7877,12.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421822520696970496 20260713.2877 12.08CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.85 23:57:47.23 +56:40:16.1
115.57639 -5.43246 galactic Cas Second-epoch detections are separated by 3.5" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J359.4451+56.6691 | 23:57:43.94 +56:39:42.8 (Gaia DR3) | DBH (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE J-Ks=0.547+/- (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:57:47.23 +56:40:16.1: 12.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:57:47.23 +56:40:16.1: 12.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 07 13.2877* 23 57 47.23 +56 40 16.1 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
ATO J359.4451+56.6691,2461234.7877,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
ATO J359.4451+56.6691 20260713.2877 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 07 13.2877 2461234.7877 11.79 23:17:00.57 +56:24:22.1
110.09694 -4.09421 galactic Cas Second-epoch detections are separated by 7.5" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.2702+56.4129 | 23:17:00.57 +56:24:22.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:17:00.57 +56:24:22.1: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:17:00.57 +56:24:22.1: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 17 00.57 +56 24 22.1 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
ATO J349.2702+56.4129,2461234.7877,11.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
ATO J349.2702+56.4129 20260713.2877 11.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.91 00:25:01.23 +55:19:57.3
119.14984 -7.34505 galactic Cas Second-epoch detections are separated by 4.3" and 1.1 pix
The object was found in VSX17" WISE J002502.5+551944
Type: EA
# Max. Min./Amp. JD0 Period
11.557 W1 Y 0.489 W1 3.154151200000
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:01.23 +55:19:57.3: 13.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:01.23 +55:19:57.3: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 25 01.23 +55 19 57.3 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
WISE J002502.5+551944,2461234.7877,11.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
WISE J002502.5+551944 20260713.2877 11.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.71 23:59:05.82 +55:40:58.7
115.55201 -6.43700 galactic Cas Second-epoch detections are separated by 5.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J359.7614+55.6687 | 23:59:06.69 +55:40:35.6 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE SpType: G7 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:59:05.82 +55:40:58.7: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:59:05.82 +55:40:58.7: 13.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 07 13.2877* 23 59 05.82 +55 40 58.7 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
ATO J359.7614+55.6687,2461234.7877,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
ATO J359.7614+55.6687 20260713.2877 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 07 13.2877 2461234.7877 11.86 00:07:17.80 +57:21:38.6
116.98349 -5.00034 galactic Cas Second-epoch detections are separated by 3.7" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.8287+57.3578 | 00:07:17.80 +57:21:38.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:07:17.80 +57:21:38.6: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:07:17.80 +57:21:38.6: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 07 17.80 +57 21 38.6 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
ATO J001.8287+57.3578,2461234.7877,11.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
ATO J001.8287+57.3578 20260713.2877 11.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.76 00:31:12.47 +56:36:38.7
120.13505 -6.15110 galactic Cas Second-epoch detections are separated by 6.6" and 1.2 pix
The object was found in VSX15" ZTF J003111.04+563629.4
Type: RS
# Max. Min./Amp. JD0 Period
13.678 g Y 0.049 g 2458292.94960 2.269195400000
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:12.47 +56:36:38.7: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:12.47 +56:36:38.7: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 12.47 +56 36 38.7 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
ZTF J003111.04+563629.4,2461234.7877,11.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J003111.04+563629.4 20260713.2877 11.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.59 23:16:36.08 +54:03:16.7
109.19558 -6.26843 galactic Cas Second-epoch detections are separated by 5.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1995964593442556544 | 23:16:38.42 +54:03:51.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F0 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:16:36.08 +54:03:16.7: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:16:36.08 +54:03:16.7: 13.33 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 16 36.08 +54 03 16.7 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1995964593442556544,2461234.7877,11.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1995964593442556544 20260713.2877 11.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.73 00:18:42.96 +50:07:26.8
117.57220 -12.40680 galactic Cas Second-epoch detections are separated by 7.1" and 2.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:18:42.96 +50:07:26.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:18:42.96 +50:07:26.8: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:18:42.96 +50:07:26.8: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 18 42.96 +50 07 26.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
target,2461234.7877,11.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 20260713.2877 11.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.47 23:22:13.30 +55:55:53.3
110.61331 -4.79173 galactic Cas Second-epoch detections are separated by 3.4" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:13.30 +55:55:53.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:22:13.30 +55:55:53.3: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:22:13.30 +55:55:53.3: 13.33 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 22 13.30 +55 55 53.3 11.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,11.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 11.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.46 23:27:47.58 +56:18:34.6
111.47383 -4.68998 galactic Cas Second-epoch detections are separated by 1.4" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J351.9448+56.3109 | 23:27:47.58 +56:18:34.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:27:47.58 +56:18:34.6: 13.46 +/- 0.27 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:27:47.58 +56:18:34.6: 13.09 +/- 0.27 detection
Forced photometry reference-image weighted average: 13.27 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 27 47.58 +56 18 34.6 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
ATO J351.9448+56.3109,2461234.7877,11.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
ATO J351.9448+56.3109 20260713.2877 11.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 07 13.2877 2461234.7877 11.30 00:19:51.83 +49:58:27.3
117.73983 -12.57893 galactic Cas Second-epoch detections are separated by 8.1" and 1.8 pix
The object was found in VSX15" Gaia DR3 394496422632390016
Type: ROT
# Max. Min./Amp. JD0 Period
15.320 G 15.350 G F
ATTENTION: measured mag 11.30 is 4.0 mag brighter than the VSX record maximum brightness 15.32 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:19:51.83 +49:58:27.3: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:19:51.83 +49:58:27.3: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 19 51.83 +49 58 27.3 11.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 394496422632390016,2461234.7877,11.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 394496422632390016 20260713.2877 11.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.32 23:59:26.09 +55:57:58.4
115.65635 -6.16918 galactic Cas Second-epoch detections are separated by 6.0" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1994724271305275648 | 23:59:26.01 +55:58:10.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:59:26.09 +55:57:58.4: 13.32 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:59:26.09 +55:57:58.4: 13.36 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.32 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 59 26.09 +55 57 58.4 11.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1994724271305275648,2461234.7877,11.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
Gaia DR3 1994724271305275648 20260713.2877 11.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.17 00:22:59.37 +53:53:10.7
118.69777 -8.75140 galactic Cas Second-epoch detections are separated by 3.1" and 1.5 pix
The object was found in VSX13" Gaia DR3 419525331674251520
Type: ROT
# Max. Min./Amp. JD0 Period
12.300 G 12.350 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:59.37 +53:53:10.7: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:59.37 +53:53:10.7: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 22 59.37 +53 53 10.7 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 419525331674251520,2461234.7877,11.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 419525331674251520 20260713.2877 11.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.11 23:41:14.51 +55:32:48.9
113.05621 -5.97310 galactic Cas Second-epoch detections are separated by 5.4" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:14.51 +55:32:48.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:41:14.51 +55:32:48.9: 12.85 +/- 0.14 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:41:14.51 +55:32:48.9: 12.72 +/- 0.16 detection
Forced photometry reference-image weighted average: 12.79 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 41 14.51 +55 32 48.9 11.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,11.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 11.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.15 00:30:24.02 +55:49:16.9
119.95843 -6.92888 galactic Cas Second-epoch detections are separated by 3.9" and 1.4 pix
The object was found in VSX20" Gaia DR3 421273280280788608
Type: ROT
# Max. Min./Amp. JD0 Period
15.310 G 15.340 G G
ATTENTION: measured mag 11.15 is 4.2 mag brighter than the VSX record maximum brightness 15.31 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:24.02 +55:49:16.9: 12.62 +/- 0.13 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:24.02 +55:49:16.9: 12.53 +/- 0.15 detection
Forced photometry reference-image weighted average: 12.58 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 24.02 +55 49 16.9 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421273280280788608,2461234.7877,11.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
Gaia DR3 421273280280788608 20260713.2877 11.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.11 23:57:46.95 +52:11:14.0
114.63292 -9.81783 galactic Cas Second-epoch detections are separated by 8.6" and 1.2 pix
The object was found in VSX24" Gaia DR3 1944396776546493952
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.560 G 14.590 G A
ATTENTION: measured mag 11.11 is 3.5 mag brighter than the VSX record maximum brightness 14.56 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:57:46.95 +52:11:14.0: 12.77 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:57:46.95 +52:11:14.0: 12.18 +/- 0.09 detection
Forced photometry reference-image weighted average: 12.40 +/- 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 07 13.2877* 23 57 46.95 +52 11 14.0 11.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1944396776546493952,2461234.7877,11.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1944396776546493952 20260713.2877 11.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 9.50 00:20:13.54 +55:23:41.2
118.47442 -7.20660 galactic Cas Second-epoch detections are separated by 6.5" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421387079733503232 | 00:20:18.44 +55:23:28.3 (Gaia DR3) | DSCT/GDOR (local) | (local) | Gaia3var=VARIABLE SpType: OB- 1965ZA.....62....6B BD+54 38
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:20:13.54 +55:23:41.2: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:20:13.54 +55:23:41.2: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 20 13.54 +55 23 41.2 9.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 421387079733503232,2461234.7877,9.50,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 421387079733503232 20260713.2877 9.50CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 10.39 00:28:42.64 +57:00:57.4
119.82681 -5.71872 galactic Cas Second-epoch detections are separated by 4.7" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421813484080843904 | 00:28:44.40 +57:00:20.8 (Gaia DR3) | E (local) | 3.371510000000 (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:42.64 +57:00:57.4: 13.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:42.64 +57:00:57.4: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 42.64 +57 00 57.4 10.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421813484080843904,2461234.7877,10.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
Gaia DR3 421813484080843904 20260713.2877 10.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 10.76 00:25:19.81 +55:26:56.1
119.20596 -7.23384 galactic Cas Second-epoch detections are separated by 0.7" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421200575075765504 | 00:25:23.67 +55:26:52.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:19.81 +55:26:56.1: 12.91 +/- 0.16 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:19.81 +55:26:56.1: 12.49 +/- 0.15 detection
Forced photometry reference-image weighted average: 12.68 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 25 19.81 +55 26 56.1 10.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 421200575075765504,2461234.7877,10.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421200575075765504 20260713.2877 10.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 10.78 23:43:09.70 +50:24:26.4
111.94568 -11.00230 galactic Cas Second-epoch detections are separated by 7.6" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:09.70 +50:24:26.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:43:09.70 +50:24:26.4: 13.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:43:09.70 +50:24:26.4: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 43 09.70 +50 24 26.4 10.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,2461234.7877,10.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 10.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.01 00:13:40.53 +56:53:50.2
117.76775 -5.59535 galactic Cas Second-epoch detections are separated by 4.2" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.4030+56.9099 | 00:13:37.40 +56:53:50.8 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:13:40.53 +56:53:50.2: 13.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:13:40.53 +56:53:50.2: 13.27 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 13 40.53 +56 53 50.2 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
ATO J003.4030+56.9099,2461234.7877,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
ATO J003.4030+56.9099 20260713.2877 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 07 13.2877 2461234.7877 11.29 00:19:32.95 +57:40:58.1
118.66399 -4.92445 galactic Cas Second-epoch detections are separated by 2.2" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 422040911198672384 | 00:19:36.72 +57:40:36.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:19:32.95 +57:40:58.1: 13.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:19:32.95 +57:40:58.1: 13.32 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 19 32.95 +57 40 58.1 11.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422040911198672384,2461234.7877,11.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422040911198672384 20260713.2877 11.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.52 00:20:18.00 +57:39:19.3
118.76062 -4.96398 galactic Cas Second-epoch detections are separated by 3.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 422045755920643968 | 00:20:20.99 +57:39:04.3 (Gaia DR3) | ROT (local) | (local) | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:20:18.00 +57:39:19.3: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:20:18.00 +57:39:19.3: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 20 18.00 +57 39 19.3 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 422045755920643968,2461234.7877,11.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422045755920643968 20260713.2877 11.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.48 23:21:38.41 +50:06:37.2
108.52221 -10.23220 galactic And Second-epoch detections are separated by 6.7" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:38.41 +50:06:37.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:21:38.41 +50:06:37.2: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:21:38.41 +50:06:37.2: 13.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 07 13.2877* 23 21 38.41 +50 06 37.2 11.5 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,2461234.7877,11.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 20260713.2877 11.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 07 13.2877 2461234.7877 11.68 00:28:41.43 +55:35:45.4
119.69723 -7.13287 galactic Cas Second-epoch detections are separated by 3.1" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:41.43 +55:35:45.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:41.43 +55:35:45.4: 13.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:41.43 +55:35:45.4: 13.10 +/- 0.28 detection
Forced photometry reference-image weighted average: 13.10 +/- 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 07 13.2877* 00 28 41.43 +55 35 45.4 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
target,2461234.7877,11.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 20260713.2877 11.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.94 00:27:44.84 +55:38:34.8
119.56791 -7.07393 galactic Cas Second-epoch detections are separated by 3.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421258471227286272 | 00:27:48.99 +55:38:22.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:27:44.84 +55:38:34.8: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:27:44.84 +55:38:34.8: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 27 44.84 +55 38 34.8 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 421258471227286272,2461234.7877,11.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
Gaia DR3 421258471227286272 20260713.2877 11.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 07 13.2877 2461234.7877 12.00 00:31:00.14 +57:25:07.7
120.17139 -5.34337 galactic Cas Second-epoch detections are separated by 4.4" and 1.4 pix
The object was found in VSX 6" Gaia DR3 421839975445105536
Type: E
# Max. Min./Amp. JD0 Period
13.480 G 13.690 G 2.085110000000 F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:00.14 +57:25:07.7: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:00.14 +57:25:07.7: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 00.14 +57 25 07.7 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 421839975445105536,2461234.7877,12.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421839975445105536 20260713.2877 12.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.04 00:05:56.66 +51:24:26.8
115.73730 -10.82767 galactic Cas Second-epoch detections are separated by 7.1" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:56.66 +51:24:26.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:05:56.66 +51:24:26.8: 13.34 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:05:56.66 +51:24:26.8: 13.41 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.34 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 05 56.66 +51 24 26.8 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,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 20260713.2877 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 07 13.2877 2461234.7877 12.46 00:07:19.85 +51:17:57.1
115.93490 -10.97234 galactic Cas Second-epoch detections are separated by 2.4" and 1.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.8282+51.2976 | 00:07:19.85 +51:17:57.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:07:19.85 +51:17:57.1: 13.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:07:19.85 +51:17:57.1: 13.57 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 07 19.85 +51 17 57.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.8282+51.2976,2461234.7877,12.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
ATO J001.8282+51.2976 20260713.2877 12.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 07 13.2877 2461234.7877 12.32 00:14:08.80 +54:04:46.8
117.41926 -8.39245 galactic Cas Second-epoch detections are separated by 8.7" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.5612+54.0820 | 00:14:10.61 +54:04:35.9 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:14:08.80 +54:04:46.8: 13.61 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:14:08.80 +54:04:46.8: 13.49 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.61 +/- 0.29
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 14 08.80 +54 04 46.8 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J003.5612+54.0820,2461234.7877,12.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.5612+54.0820 20260713.2877 12.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.11 23:14:00.84 +55:30:36.4
109.37904 -4.77707 galactic Cas Second-epoch detections are separated by 7.9" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J348.5100+55.5121 | 23:14:00.84 +55:30:36.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:14:00.84 +55:30:36.4: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:14:00.84 +55:30:36.4: 13.43 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 14 00.84 +55 30 36.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
ATO J348.5100+55.5121,2461234.7877,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
ATO J348.5100+55.5121 20260713.2877 12.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.36 00:27:02.78 +57:52:22.5
119.68183 -4.84483 galactic Cas Second-epoch detections are separated by 4.6" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:27:02.78 +57:52:22.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:27:02.78 +57:52:22.5: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:27:02.78 +57:52:22.5: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 27 02.78 +57 52 22.5 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 20260713.2877 12.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.34 00:31:11.33 +55:35:46.7
120.05167 -7.16216 galactic Cas Second-epoch detections are separated by 5.0" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:11.33 +55:35:46.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:11.33 +55:35:46.7: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:11.33 +55:35:46.7: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 11.33 +55 35 46.7 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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
target 20260713.2877 12.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.46 00:31:08.55 +57:02:02.2
120.15971 -5.72852 galactic Cas Second-epoch detections are separated by 5.3" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:08.55 +57:02:02.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:08.55 +57:02:02.2: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:08.55 +57:02:02.2: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 08.55 +57 02 02.2 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.47 00:31:11.23 +56:01:48.7
120.08602 -6.72961 galactic Cas Second-epoch detections are separated by 8.7" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.7945+56.0280 | 00:31:11.23 +56:01:48.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:11.23 +56:01:48.7: 13.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:11.23 +56:01:48.7: 13.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 11.23 +56 01 48.7 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.7945+56.0280,2461234.7877,12.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
ATO J007.7945+56.0280 20260713.2877 12.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.44 23:43:23.05 +50:04:13.0
111.88930 -11.33669 galactic Cas Second-epoch detections are separated by 6.2" and 1.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 1943572658220070272 | 23:43:22.59 +50:04:20.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:43:23.05 +50:04:13.0: 13.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:43:23.05 +50:04:13.0: 13.34 +/- 0.30 detection
Forced photometry reference-image weighted average: 13.34 +/- 0.30
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 43 23.05 +50 04 13.0 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1943572658220070272,2461234.7877,12.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1943572658220070272 20260713.2877 12.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.62 00:31:10.04 +56:38:40.8
120.13216 -6.11685 galactic Cas Second-epoch detections are separated by 5.3" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:10.04 +56:38:40.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:10.04 +56:38:40.8: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:10.04 +56:38:40.8: 13.34 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 10.04 +56 38 40.8 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,2461234.7877,12.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 20260713.2877 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.29 00:10:47.84 +54:41:56.4
117.02770 -7.70619 galactic Cas Second-epoch detections are separated by 7.5" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.6866+54.6954 | 00:10:48.89 +54:41:23.6 (Gaia DR3) | SINE (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE SpType: F5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:10:47.84 +54:41:56.4: 13.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:10:47.84 +54:41:56.4: 13.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 07 13.2877* 00 10 47.84 +54 41 56.4 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.6866+54.6954,2461234.7877,12.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
ATO J002.6866+54.6954 20260713.2877 12.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 07 13.2877 2461234.7877 12.34 00:24:28.87 +56:46:03.4
119.22483 -5.90998 galactic Cas Second-epoch detections are separated by 8.2" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:24:28.87 +56:46:03.4 (user input) | T | P | (position from user input) J-Ks=0.337+/-0.047 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:24:28.87 +56:46:03.4: 13.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:24:28.87 +56:46:03.4: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 24 28.87 +56 46 03.4 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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
target 20260713.2877 12.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.51 00:22:11.90 +49:50:42.0
118.10625 -12.75258 galactic Cas Second-epoch detections are separated by 4.0" and 2.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J005.5391+49.8543 | 00:22:11.90 +49:50:42.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:11.90 +49:50:42.0: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:11.90 +49:50:42.0: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 22 11.90 +49 50 42.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J005.5391+49.8543,2461234.7877,12.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.5391+49.8543 20260713.2877 12.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.62 00:26:24.15 +57:51:06.7
119.59427 -4.85755 galactic Cas Second-epoch detections are separated by 4.2" and 1.1 pix
The object was found in VSX16" Gaia DR3 421923332171891968
Type: S
# Max. Min./Amp. JD0 Period
16.050 G 16.680 G K
ATTENTION: measured mag 12.62 is 3.4 mag brighter than the VSX record maximum brightness 16.05 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:24.15 +57:51:06.7: 13.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:24.15 +57:51:06.7: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 26 24.15 +57 51 06.7 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421923332171891968,2461234.7877,12.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
Gaia DR3 421923332171891968 20260713.2877 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.46 00:01:21.57 +54:49:13.8
115.69770 -7.34632 galactic Cas Second-epoch detections are separated by 3.9" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420375735195826048 | 00:01:18.83 +54:49:45.3 (Gaia DR3) | E (local) | 0.507400000000 (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:01:21.57 +54:49:13.8: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:01:21.57 +54:49:13.8: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 01 21.57 +54 49 13.8 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420375735195826048,2461234.7877,12.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 420375735195826048 20260713.2877 12.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 07 13.2877 2461234.7877 12.57 00:22:24.57 +50:05:47.1
118.17061 -12.50678 galactic Cas Second-epoch detections are separated by 5.9" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ASASSN-V J002224.11+500623.5 | 00:22:24.11 +50:06:23.5 (Gaia DR3) | SR (local) | 113.000000000000 (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:24.57 +50:05:47.1: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:24.57 +50:05:47.1: 13.32 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 22 24.57 +50 05 47.1 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
ASASSN-V J002224.11+500623.5,2461234.7877,12.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
ASASSN-V J002224.11+500623.5 20260713.2877 12.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.66 00:21:21.30 +50:04:52.2
117.99672 -12.50209 galactic Cas Second-epoch detections are separated by 4.0" and 1.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:21:21.30 +50:04:52.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:21:21.30 +50:04:52.2: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:21:21.30 +50:04:52.2: 13.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 07 13.2877* 00 21 21.30 +50 04 52.2 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.54 00:30:18.57 +56:07:46.1
119.97122 -6.62077 galactic Cas Second-epoch detections are separated by 6.3" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.5923+56.1336 | 00:30:18.57 +56:07:46.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:18.57 +56:07:46.1: 13.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:18.57 +56:07:46.1: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 18.57 +56 07 46.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.5923+56.1336,2461234.7877,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.5923+56.1336 20260713.2877 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.55 23:56:13.05 +54:27:18.9
114.88796 -7.55178 galactic Cas Second-epoch detections are separated by 5.6" and 1.2 pix
The object was found in VSX24" Gaia DR3 1993633074736513920
Type:
# Max. Min./Amp. JD0 Period
16.540 G 16.600 G K
ATTENTION: measured mag 12.55 is 4.0 mag brighter than the VSX record maximum brightness 16.54 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:56:13.05 +54:27:18.9: 13.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:56:13.05 +54:27:18.9: 13.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 07 13.2877* 23 56 13.05 +54 27 18.9 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993633074736513920,2461234.7877,12.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993633074736513920 20260713.2877 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.52 00:11:07.93 +57:36:57.4
117.53571 -4.83290 galactic Cas Second-epoch detections are separated by 7.4" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:07.93 +57:36:57.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:11:07.93 +57:36:57.4: 13.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:11:07.93 +57:36:57.4: 13.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 07 13.2877* 00 11 07.93 +57 36 57.4 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.59 00:25:49.93 +56:00:40.2
119.33397 -6.68160 galactic Cas Second-epoch detections are separated by 2.0" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:25:49.93 +56:00:40.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:49.93 +56:00:40.2: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:49.93 +56:00:40.2: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 25 49.93 +56 00 40.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,2461234.7877,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 20260713.2877 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.47 00:30:20.44 +57:32:49.5
120.09280 -5.20832 galactic Cas Second-epoch detections are separated by 5.1" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.5805+57.5475 | 00:30:20.44 +57:32:49.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:20.44 +57:32:49.5: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:20.44 +57:32:49.5: 13.34 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 20.44 +57 32 49.5 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.5805+57.5475,2461234.7877,12.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
ATO J007.5805+57.5475 20260713.2877 12.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.41 00:30:26.55 +55:57:32.5
119.97574 -6.79216 galactic Cas Second-epoch detections are separated by 6.1" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.6174+55.9537 | 00:30:26.55 +55:57:32.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:26.55 +55:57:32.5: 13.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:26.55 +55:57:32.5: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 26.55 +55 57 32.5 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.6174+55.9537,2461234.7877,12.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.6174+55.9537 20260713.2877 12.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.59 00:22:10.00 +57:53:34.2
119.03662 -4.75736 galactic Cas Second-epoch detections are separated by 4.5" and 0.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 | Gaia DR3 422099460189283968 | 00:22:06.58 +57:53:39.0 (Gaia DR3) | ROT (local) | (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:10.00 +57:53:34.2: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:10.00 +57:53:34.2: 13.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 07 13.2877* 00 22 10.00 +57 53 34.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
Gaia DR3 422099460189283968,2461234.7877,12.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422099460189283968 20260713.2877 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.51 00:25:17.32 +58:06:43.0
119.47284 -4.58407 galactic Cas Second-epoch detections are separated by 1.6" and 1.4 pix
The object was found in VSX11" Gaia DR3 421930753875214208
Type: E
# Max. Min./Amp. JD0 Period
15.020 G 15.460 G 0.214263000000 A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:17.32 +58:06:43.0: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:17.32 +58:06:43.0: 13.43 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 25 17.32 +58 06 43.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421930753875214208,2461234.7877,12.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421930753875214208 20260713.2877 12.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.39 00:27:47.19 +57:46:49.8
119.77162 -4.94605 galactic Cas Second-epoch detections are separated by 4.7" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421909691355874176 | 00:27:48.34 +57:46:20.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:27:47.19 +57:46:49.8: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:27:47.19 +57:46:49.8: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 27 47.19 +57 46 49.8 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421909691355874176,2461234.7877,12.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
Gaia DR3 421909691355874176 20260713.2877 12.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.36 23:19:09.41 +52:18:41.8
108.93059 -8.03351 galactic And Second-epoch detections are separated by 3.8" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:09.41 +52:18:41.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:19:09.41 +52:18:41.8: 13.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:19:09.41 +52:18:41.8: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 19 09.41 +52 18 41.8 12.4 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,2461234.7877,12.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 20260713.2877 12.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.48 23:45:22.71 +56:43:53.7
113.92652 -4.98071 galactic Cas Second-epoch detections are separated by 3.2" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J356.3388+56.7292 | 23:45:22.71 +56:43:53.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:45:22.71 +56:43:53.7: 13.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:45:22.71 +56:43:53.7: 13.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 07 13.2877* 23 45 22.71 +56 43 53.7 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J356.3388+56.7292,2461234.7877,12.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 J356.3388+56.7292 20260713.2877 12.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 07 13.2877 2461234.7877 12.45 00:03:27.43 +54:25:00.7
115.92079 -7.80043 galactic Cas Second-epoch detections are separated by 6.2" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420348522283353088 | 00:03:29.21 +54:25:15.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:03:27.43 +54:25:00.7: 13.52 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:03:27.43 +54:25:00.7: 13.52 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.52 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 03 27.43 +54 25 00.7 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420348522283353088,2461234.7877,12.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
Gaia DR3 420348522283353088 20260713.2877 12.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 07 13.2877 2461234.7877 12.61 00:13:38.45 +54:57:36.0
117.47622 -7.51087 galactic Cas Second-epoch detections are separated by 8.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420565057353289216 | 00:13:40.42 +54:57:29.7 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F4 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:13:38.45 +54:57:36.0: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:13:38.45 +54:57:36.0: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 13 38.45 +54 57 36.0 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420565057353289216,2461234.7877,12.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 420565057353289216 20260713.2877 12.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.79 00:21:55.69 +50:04:57.1
118.09041 -12.51161 galactic Cas Second-epoch detections are separated by 3.9" and 1.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:21:55.69 +50:04:57.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:21:55.69 +50:04:57.1: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:21:55.69 +50:04:57.1: 13.43 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 21 55.69 +50 04 57.1 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.53 00:30:02.64 +57:31:38.9
120.05134 -5.22457 galactic Cas Second-epoch detections are separated by 6.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.4908+57.5416 | 00:30:02.18 +57:32:19.3 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:02.64 +57:31:38.9: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:02.64 +57:31:38.9: 13.33 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 02.64 +57 31 38.9 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.4908+57.5416,2461234.7877,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.4908+57.5416 20260713.2877 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.55 00:28:04.93 +57:36:07.0
119.79472 -5.12747 galactic Cas Second-epoch detections are separated by 4.9" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:04.93 +57:36:07.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:04.93 +57:36:07.0: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:04.93 +57:36:07.0: 13.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 07 13.2877* 00 28 04.93 +57 36 07.0 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,2461234.7877,12.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 20260713.2877 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.51 23:20:10.87 +49:26:39.0
108.06166 -10.77461 galactic And Second-epoch detections are separated by 1.0" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:20:10.87 +49:26:39.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:20:10.87 +49:26:39.0: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:20:10.87 +49:26:39.0: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 20 10.87 +49 26 39.0 12.5 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,2461234.7877,12.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.57 00:28:55.36 +57:14:42.8
119.87590 -5.49287 galactic Cas Second-epoch detections are separated by 7.4" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.2292+57.2425 | 00:28:55.36 +57:14:42.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:55.36 +57:14:42.8: 13.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:55.36 +57:14:42.8: 13.34 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 55.36 +57 14 42.8 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
ATO J007.2292+57.2425,2461234.7877,12.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
ATO J007.2292+57.2425 20260713.2877 12.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 00:32:09.71 +56:46:40.1
120.27930 -5.99463 galactic Cas Second-epoch detections are separated by 3.2" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J008.0477+56.7845 | 00:32:09.71 +56:46:40.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:09.71 +56:46:40.1: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:09.71 +56:46:40.1: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 09.71 +56 46 40.1 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
ATO J008.0477+56.7845,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J008.0477+56.7845 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.49 23:18:53.75 +49:32:00.5
107.89508 -10.61727 galactic And Second-epoch detections are separated by 2.3" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1942737441699327872 | 23:18:50.46 +49:32:01.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A2IV (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:18:53.75 +49:32:00.5: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:18:53.75 +49:32:00.5: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 18 53.75 +49 32 00.5 12.5 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
Gaia DR3 1942737441699327872,2461234.7877,12.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1942737441699327872 20260713.2877 12.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.54 23:23:39.19 +49:26:39.7
108.60111 -10.96916 galactic And Second-epoch detections are separated by 4.4" and 1.7 pix
The object was found in VSX22" Gaia DR3 1943061454032400384
Type: ROT
# Max. Min./Amp. JD0 Period
13.960 G 14.010 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:23:39.19 +49:26:39.7: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:23:39.19 +49:26:39.7: 13.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 07 13.2877* 23 23 39.19 +49 26 39.7 12.5 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
Gaia DR3 1943061454032400384,2461234.7877,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1943061454032400384 20260713.2877 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.56 00:25:19.31 +57:25:11.4
119.40665 -5.27305 galactic Cas Second-epoch detections are separated by 4.1" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.3264+57.4197 | 00:25:19.31 +57:25:11.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:19.31 +57:25:11.4: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:19.31 +57:25:11.4: 13.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 07 13.2877* 00 25 19.31 +57 25 11.4 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J006.3264+57.4197,2461234.7877,12.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
ATO J006.3264+57.4197 20260713.2877 12.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 07 13.2877 2461234.7877 12.63 00:27:10.06 +57:15:39.2
119.63991 -5.45565 galactic Cas Second-epoch detections are separated by 3.3" and 1.5 pix
The object was found in VSX14" Gaia DR3 421867635035451776
Type: ROT
# Max. Min./Amp. JD0 Period
13.290 G 13.340 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:27:10.06 +57:15:39.2: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:27:10.06 +57:15:39.2: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 27 10.06 +57 15 39.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
Gaia DR3 421867635035451776,2461234.7877,12.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421867635035451776 20260713.2877 12.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.56 00:12:53.30 +57:15:11.9
117.71447 -5.22741 galactic Cas Second-epoch detections are separated by 7.4" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.2229+57.2652 | 00:12:53.30 +57:15:11.9 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:12:53.30 +57:15:11.9: 13.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:12:53.30 +57:15:11.9: 13.30 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 12 53.30 +57 15 11.9 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
ATO J003.2229+57.2652,2461234.7877,12.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
ATO J003.2229+57.2652 20260713.2877 12.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 07 13.2877 2461234.7877 12.62 00:22:17.80 +50:07:39.9
118.15591 -12.47357 galactic Cas Second-epoch detections are separated by 4.0" and 1.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:17.80 +50:07:39.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:17.80 +50:07:39.9: 13.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:17.80 +50:07:39.9: 13.31 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 22 17.80 +50 07 39.9 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,2461234.7877,12.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 20260713.2877 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.66 00:28:59.81 +56:53:49.0
119.85534 -5.84069 galactic Cas Second-epoch detections are separated by 7.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:59.81 +56:53:49.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:59.81 +56:53:49.0: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:59.81 +56:53:49.0: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 59.81 +56 53 49.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.60 00:24:14.22 +57:44:20.9
119.29470 -4.94039 galactic Cas Second-epoch detections are separated by 4.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:24:14.22 +57:44:20.9 (user input) | T | P | (position from user input) SpType: F0 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:24:14.22 +57:44:20.9: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:24:14.22 +57:44:20.9: 13.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 07 13.2877* 00 24 14.22 +57 44 20.9 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,2461234.7877,12.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 20260713.2877 12.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 23:50:04.62 +56:30:38.1
114.50117 -5.35343 galactic Cas Second-epoch detections are separated by 7.3" and 1.1 pix
The object was found in VSX12" Gaia DR3 1997954468973124224
Type: ROT
# Max. Min./Amp. JD0 Period
15.170 G 15.220 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:50:04.62 +56:30:38.1: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:50:04.62 +56:30:38.1: 13.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 07 13.2877* 23 50 04.62 +56 30 38.1 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997954468973124224,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997954468973124224 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 00:31:56.22 +56:45:35.0
120.24704 -6.01033 galactic Cas Second-epoch detections are separated by 3.7" and 1.3 pix
The object was found in VSX25" Gaia DR3 421792554705659648
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.430 G 13.470 G A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:56.22 +56:45:35.0: 13.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:56.22 +56:45:35.0: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 56.22 +56 45 35.0 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 421792554705659648,2461234.7877,12.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421792554705659648 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.59 23:39:20.01 +50:37:51.9
111.41197 -10.62084 galactic And Second-epoch detections are separated by 5.5" and 1.0 pix
The object was found in VSX22" Gaia DR3 1944481679458686464
Type: ROT
# Max. Min./Amp. JD0 Period
14.980 G 15.010 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:39:20.01 +50:37:51.9: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:39:20.01 +50:37:51.9: 13.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 07 13.2877* 23 39 20.01 +50 37 51.9 12.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
Gaia DR3 1944481679458686464,2461234.7877,12.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1944481679458686464 20260713.2877 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.57 00:17:13.35 +57:50:24.7
118.37545 -4.72854 galactic Cas Second-epoch detections are separated by 5.2" and 1.1 pix
The object was found in VSX 7" Gaia DR3 422061114723435008
Type: ROT
# Max. Min./Amp. JD0 Period
14.500 G 14.540 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:17:13.35 +57:50:24.7: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:17:13.35 +57:50:24.7: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 17 13.35 +57 50 24.7 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422061114723435008,2461234.7877,12.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
Gaia DR3 422061114723435008 20260713.2877 12.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.81 00:20:35.06 +49:54:17.7
117.84891 -12.66208 galactic Cas Second-epoch detections are separated by 5.0" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:20:35.06 +49:54:17.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:20:35.06 +49:54:17.7: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:20:35.06 +49:54:17.7: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 20 35.06 +49 54 17.7 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.57 00:32:22.39 +57:15:20.6
120.34403 -5.52020 galactic Cas Second-epoch detections are separated by 7.2" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:22.39 +57:15:20.6 (user input) | T | P | (position from user input) J-Ks=0.859+/-0.179 (M)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:22.39 +57:15:20.6: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:22.39 +57:15:20.6: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 22.39 +57 15 20.6 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,2461234.7877,12.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 20260713.2877 12.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.65 00:21:13.55 +49:53:59.8
117.95339 -12.67953 galactic Cas Second-epoch detections are separated by 4.8" and 1.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:21:13.55 +49:53:59.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:21:13.55 +49:53:59.8: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:21:13.55 +49:53:59.8: 13.55 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 21 13.55 +49 53 59.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
target,2461234.7877,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:32:12.23 +57:44:52.6
120.35812 -5.02765 galactic Cas Second-epoch detections are separated by 6.3" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:12.23 +57:44:52.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:12.23 +57:44:52.6: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:12.23 +57:44:52.6: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 12.23 +57 44 52.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.59 23:54:56.15 +56:31:20.2
115.15937 -5.49440 galactic Cas Second-epoch detections are separated by 4.3" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:54:56.15 +56:31:20.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:54:56.15 +56:31:20.2: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:54:56.15 +56:31:20.2: 13.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 07 13.2877* 23 54 56.15 +56 31 20.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,2461234.7877,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 20260713.2877 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:15:47.33 +49:47:37.5
117.04850 -12.67032 galactic Cas Second-epoch detections are separated by 6.9" and 2.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:47.33 +49:47:37.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:15:47.33 +49:47:37.5: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:15:47.33 +49:47:37.5: 13.52 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 15 47.33 +49 47 37.5 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.71 00:28:22.45 +55:50:25.0
119.67456 -6.88553 galactic Cas Second-epoch detections are separated by 3.8" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:22.45 +55:50:25.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:22.45 +55:50:25.0: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:22.45 +55:50:25.0: 13.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 07 13.2877* 00 28 22.45 +55 50 25.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.75 00:31:59.24 +56:28:35.2
120.23234 -6.29332 galactic Cas Second-epoch detections are separated by 8.7" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:59.24 +56:28:35.2 (user input) | T | P | (position from user input) SpType: F5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:59.24 +56:28:35.2: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:59.24 +56:28:35.2: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 59.24 +56 28 35.2 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 00:28:05.69 +55:16:33.2
119.58335 -7.44402 galactic Cas Second-epoch detections are separated by 3.7" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.0233+55.2856 | 00:28:05.69 +55:16:33.2 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:05.69 +55:16:33.2: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:05.69 +55:16:33.2: 13.31 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 05.69 +55 16 33.2 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
ATO J007.0233+55.2856,2461234.7877,12.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.0233+55.2856 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:29:41.61 +55:45:18.2
119.85310 -6.98665 galactic Cas Second-epoch detections are separated by 4.6" and 1.7 pix
The object was found in VSX 9" Gaia DR3 421270222264107264
Type: ROT
# Max. Min./Amp. JD0 Period
14.830 G 14.860 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:29:41.61 +55:45:18.2: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:29:41.61 +55:45:18.2: 13.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 07 13.2877* 00 29 41.61 +55 45 18.2 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 421270222264107264,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421270222264107264 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 00:21:15.31 +50:08:09.5
117.98715 -12.44577 galactic Cas Second-epoch detections are separated by 3.9" and 1.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 J005.3143+50.1474 | 00:21:15.31 +50:08:09.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:21:15.31 +50:08:09.5: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:21:15.31 +50:08:09.5: 13.43 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 21 15.31 +50 08 09.5 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
ATO J005.3143+50.1474,2461234.7877,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
ATO J005.3143+50.1474 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.60 00:06:08.52 +57:18:46.3
116.82114 -5.02049 galactic Cas Second-epoch detections are separated by 3.7" and 1.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 J001.5397+57.3164 | 00:06:07.58 +57:19:06.7 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:06:08.52 +57:18:46.3: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:06:08.52 +57:18:46.3: 13.52 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 06 08.52 +57 18 46.3 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
ATO J001.5397+57.3164,2461234.7877,12.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
ATO J001.5397+57.3164 20260713.2877 12.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:28:52.08 +55:13:09.8
119.68891 -7.51018 galactic Cas Second-epoch detections are separated by 4.9" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:52.08 +55:13:09.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:52.08 +55:13:09.8: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:52.08 +55:13:09.8: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 52.08 +55 13 09.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
target,2461234.7877,12.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 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 00:25:45.26 +57:53:59.7
119.51297 -4.80124 galactic Cas Second-epoch detections are separated by 5.9" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.4356+57.8955 | 00:25:45.26 +57:53:59.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:45.26 +57:53:59.7: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:45.26 +57:53:59.7: 13.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 07 13.2877* 00 25 45.26 +57 53 59.7 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J006.4356+57.8955,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J006.4356+57.8955 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.60 23:41:05.62 +55:10:27.1
112.93454 -6.32627 galactic Cas Second-epoch detections are separated by 5.6" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:05.62 +55:10:27.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:41:05.62 +55:10:27.1: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:41:05.62 +55:10:27.1: 13.43 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 41 05.62 +55 10 27.1 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,2461234.7877,12.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 20260713.2877 12.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 00:25:26.17 +55:26:22.6
119.22008 -7.24463 galactic Cas Second-epoch detections are separated by 3.6" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421200575075768832 | 00:25:26.59 +55:26:36.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:26.17 +55:26:22.6: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:26.17 +55:26:22.6: 13.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 07 13.2877* 00 25 26.17 +55 26 22.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421200575075768832,2461234.7877,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 421200575075768832 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.56 00:18:22.84 +58:14:37.4
118.58072 -4.34847 galactic Cas Second-epoch detections are separated by 3.5" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 422169755911210240 | 00:18:18.53 +58:15:01.7 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE J-Ks=1.801+/- (Very red!)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:18:22.84 +58:14:37.4: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:18:22.84 +58:14:37.4: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 18 22.84 +58 14 37.4 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422169755911210240,2461234.7877,12.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
Gaia DR3 422169755911210240 20260713.2877 12.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 07 13.2877 2461234.7877 12.76 00:03:35.83 +54:50:49.9
116.02177 -7.38141 galactic Cas Second-epoch detections are separated by 3.3" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J000.9144+54.8476 | 00:03:35.83 +54:50:49.9 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:03:35.83 +54:50:49.9: 13.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:03:35.83 +54:50:49.9: 13.58 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 03 35.83 +54 50 49.9 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.9144+54.8476,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.9144+54.8476 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.68 00:30:32.75 +57:57:03.5
120.15332 -4.80802 galactic Cas Second-epoch detections are separated by 6.5" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.6335+57.9311 | 00:30:29.89 +57:56:28.3 (Gaia DR3) | MSINE (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:32.75 +57:57:03.5: 13.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:32.75 +57:57:03.5: 13.29 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 32.75 +57 57 03.5 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
ATO J007.6335+57.9311,2461234.7877,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.6335+57.9311 20260713.2877 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.65 00:28:45.07 +55:16:11.1
119.67668 -7.45854 galactic Cas Second-epoch detections are separated by 6.0" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421150955312416768 | 00:28:42.64 +55:16:37.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:45.07 +55:16:11.1: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:45.07 +55:16:11.1: 13.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 07 13.2877* 00 28 45.07 +55 16 11.1 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 421150955312416768,2461234.7877,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421150955312416768 20260713.2877 12.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.79 00:30:33.32 +55:55:11.0
119.98836 -6.83263 galactic Cas Second-epoch detections are separated by 6.9" and 2.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:30:33.32 +55:55:11.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:33.32 +55:55:11.0: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:33.32 +55:55:11.0: 13.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 07 13.2877* 00 30 33.32 +55 55 11.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:15:12.38 +57:40:46.9
118.08613 -4.85076 galactic Cas Second-epoch detections are separated by 0.5" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:12.38 +57:40:46.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:15:12.38 +57:40:46.9: 13.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:15:12.38 +57:40:46.9: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 15 12.38 +57 40 46.9 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.86 00:14:44.14 +51:17:38.0
117.09847 -11.16168 galactic Cas Second-epoch detections are separated by 7.8" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:14:44.14 +51:17:38.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:14:44.14 +51:17:38.0: 13.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:14:44.14 +51:17:38.0: 13.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 14 44.14 +51 17 38.0 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.80 00:30:33.32 +56:42:28.5
120.05301 -6.04706 galactic Cas Second-epoch detections are separated by 5.0" and 1.7 pix
The object was found in VSX10" Gaia DR3 421701230821623808
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.730 G 14.760 G A
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:33.32 +56:42:28.5: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:33.32 +56:42:28.5: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 33.32 +56 42 28.5 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 421701230821623808,2461234.7877,12.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421701230821623808 20260713.2877 12.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.69 00:16:26.35 +57:19:36.6
118.20178 -5.22313 galactic Cas Second-epoch detections are separated by 2.4" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J004.0981+57.3272 | 00:16:26.35 +57:19:36.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:16:26.35 +57:19:36.6: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:16:26.35 +57:19:36.6: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 16 26.35 +57 19 36.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J004.0981+57.3272,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J004.0981+57.3272 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:22:29.90 +53:32:20.2
118.58512 -9.08838 galactic Cas Second-epoch detections are separated by 2.0" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:29.90 +53:32:20.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:22:29.90 +53:32:20.2: 13.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:22:29.90 +53:32:20.2: 13.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 07 13.2877* 00 22 29.90 +53 32 20.2 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 00:21:32.33 +50:03:51.2
118.02465 -12.52243 galactic Cas Second-epoch detections are separated by 5.9" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:21:32.33 +50:03:51.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:21:32.33 +50:03:51.2: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:21:32.33 +50:03:51.2: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 21 32.33 +50 03 51.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,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 00:32:02.72 +57:43:28.3
120.33518 -5.04941 galactic Cas Second-epoch detections are separated by 5.6" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.9868+57.7272 | 00:31:59.43 +57:43:23.8 (Gaia DR3) | DBH (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:02.72 +57:43:28.3: 13.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:02.72 +57:43:28.3: 13.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 02.72 +57 43 28.3 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
ATO J007.9868+57.7272,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.9868+57.7272 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.89 00:15:38.11 +50:00:41.8
117.05500 -12.45115 galactic Cas Second-epoch detections are separated by 3.5" and 2.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 J003.9095+50.0120 | 00:15:38.11 +50:00:41.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input) J-Ks=1.501+/- (Very red! L if it's a dwarf)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:15:38.11 +50:00:41.8: 13.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:15:38.11 +50:00:41.8: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 15 38.11 +50 00 41.8 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J003.9095+50.0120,2461234.7877,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.9095+50.0120 20260713.2877 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.63 00:05:21.25 +57:19:54.3
116.71944 -4.98308 galactic Cas Second-epoch detections are separated by 4.8" and 1.0 pix
The object was found in VSX11" Gaia DR3 422548267092445568
Type: ROT
# Max. Min./Amp. JD0 Period
14.300 G 14.340 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:05:21.25 +57:19:54.3: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:05:21.25 +57:19:54.3: 13.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 05 21.25 +57 19 54.3 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422548267092445568,2461234.7877,12.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422548267092445568 20260713.2877 12.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:32:45.43 +57:53:35.0
120.44262 -4.88837 galactic Cas Second-epoch detections are separated by 6.9" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:45.43 +57:53:35.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:45.43 +57:53:35.0: 13.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:45.43 +57:53:35.0: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 45.43 +57 53 35.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:14:09.48 +57:57:45.3
117.98799 -4.55086 galactic Cas Second-epoch detections are separated by 3.9" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:14:09.48 +57:57:45.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:14:09.48 +57:57:45.3: 13.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:14:09.48 +57:57:45.3: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 14 09.48 +57 57 45.3 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.65 23:10:24.22 +56:05:45.2
109.12731 -4.04395 galactic Cas Second-epoch detections are separated by 6.8" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:10:24.22 +56:05:45.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:10:24.22 +56:05:45.2: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:10:24.22 +56:05:45.2: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 10 24.22 +56 05 45.2 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.80 00:29:55.35 +56:47:04.5
119.97245 -5.96348 galactic Cas Second-epoch detections are separated by 6.0" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:29:55.35 +56:47:04.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:29:55.35 +56:47:04.5: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:29:55.35 +56:47:04.5: 13.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 07 13.2877* 00 29 55.35 +56 47 04.5 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.66 23:59:07.59 +54:15:14.3
115.26381 -7.83710 galactic Cas Second-epoch detections are separated by 1.1" and 1.2 pix
The object was found in VSX 8" ZTF J235906.97+541507.9
Type: BY
# Max. Min./Amp. JD0 Period
19.185 g Y 0.159 g 2458379.88360 0.769554300000
ATTENTION: measured mag 12.66 is 6.4 mag brighter than the VSX record maximum brightness 19.03 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:59:07.59 +54:15:14.3: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:59:07.59 +54:15:14.3: 13.53 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 59 07.59 +54 15 14.3 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J235906.97+541507.9,2461234.7877,12.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
ZTF J235906.97+541507.9 20260713.2877 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.72 23:56:47.04 +56:56:43.7
115.49921 -5.13547 galactic Cas Second-epoch detections are separated by 6.3" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:56:47.04 +56:56:43.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:56:47.04 +56:56:43.7: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:56:47.04 +56:56:43.7: 13.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 07 13.2877* 23 56 47.04 +56 56 43.7 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:18:35.84 +55:14:04.4
118.22253 -7.33662 galactic Cas Second-epoch detections are separated by 7.6" and 1.4 pix
The object was found in VSX23" Gaia DR3 419927237531033600
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.920 G 14.960 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:18:35.84 +55:14:04.4: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:18:35.84 +55:14:04.4: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 18 35.84 +55 14 04.4 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 419927237531033600,2461234.7877,12.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 419927237531033600 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.77 00:30:44.47 +57:01:09.8
120.10383 -5.73867 galactic Cas Second-epoch detections are separated by 4.8" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.6878+57.0257 | 00:30:44.47 +57:01:09.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:44.47 +57:01:09.8: 13.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:44.47 +57:01:09.8: 13.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 07 13.2877* 00 30 44.47 +57 01 09.8 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
ATO J007.6878+57.0257,2461234.7877,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.6878+57.0257 20260713.2877 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.53 23:55:56.02 +56:02:00.6
115.18896 -6.00157 galactic Cas Second-epoch detections are separated by 5.8" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J358.9667+56.0264 | 23:55:52.01 +56:01:35.4 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:55:56.02 +56:02:00.6: 13.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:55:56.02 +56:02:00.6: 13.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 07 13.2877* 23 55 56.02 +56 02 00.6 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J358.9667+56.0264,2461234.7877,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J358.9667+56.0264 20260713.2877 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 00:24:54.75 +57:42:12.7
119.38099 -4.98522 galactic Cas Second-epoch detections are separated by 4.5" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.2455+57.6987 | 00:24:54.75 +57:42:12.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:24:54.75 +57:42:12.7: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:24:54.75 +57:42:12.7: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 24 54.75 +57 42 12.7 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
ATO J006.2455+57.6987,2461234.7877,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
ATO J006.2455+57.6987 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.69 00:16:50.24 +57:27:20.1
118.27262 -5.10281 galactic Cas Second-epoch detections are separated by 3.7" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J004.2104+57.4674 | 00:16:50.24 +57:27:20.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:16:50.24 +57:27:20.1: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:16:50.24 +57:27:20.1: 13.52 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 16 50.24 +57 27 20.1 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
ATO J004.2104+57.4674,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J004.2104+57.4674 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.56 23:23:00.23 +49:26:18.5
108.49796 -10.93881 galactic And Second-epoch detections are separated by 6.4" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:00.23 +49:26:18.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:23:00.23 +49:26:18.5: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:23:00.23 +49:26:18.5: 13.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 07 13.2877* 23 23 00.23 +49 26 18.5 12.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,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.69 00:17:18.59 +57:02:32.6
118.28082 -5.52084 galactic Cas Second-epoch detections are separated by 8.5" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:17:18.59 +57:02:32.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:17:18.59 +57:02:32.6: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:17:18.59 +57:02:32.6: 13.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 07 13.2877* 00 17 18.59 +57 02 32.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.81 00:25:11.31 +57:49:40.2
119.43054 -4.86535 galactic Cas Second-epoch detections are separated by 5.2" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:25:11.31 +57:49:40.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:11.31 +57:49:40.2: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:11.31 +57:49:40.2: 13.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 07 13.2877* 00 25 11.31 +57 49 40.2 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:26:30.98 +57:24:48.4
119.56671 -5.29538 galactic Cas Second-epoch detections are separated by 6.4" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:26:30.98 +57:24:48.4 (user input) | T | P | (position from user input) J-Ks=0.325+/-0.087 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:30.98 +57:24:48.4: 13.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:30.98 +57:24:48.4: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 26 30.98 +57 24 48.4 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.61 23:15:09.54 +54:02:34.3
108.99282 -6.20265 galactic Cas Second-epoch detections are separated by 3.0" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:15:09.54 +54:02:34.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:15:09.54 +54:02:34.3: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:15:09.54 +54:02:34.3: 13.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 07 13.2877* 23 15 09.54 +54 02 34.3 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,2461234.7877,12.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 20260713.2877 12.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.62 23:28:20.04 +54:25:58.1
110.94696 -6.49369 galactic Cas Second-epoch detections are separated by 5.8" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J352.0763+54.4326 | 23:28:20.04 +54:25:58.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:28:20.04 +54:25:58.1: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:28:20.04 +54:25:58.1: 13.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 07 13.2877* 23 28 20.04 +54 25 58.1 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
ATO J352.0763+54.4326,2461234.7877,12.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
ATO J352.0763+54.4326 20260713.2877 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 00:26:14.97 +55:30:01.5
119.34181 -7.19565 galactic Cas Second-epoch detections are separated by 2.5" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:26:14.97 +55:30:01.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:14.97 +55:30:01.5: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:14.97 +55:30:01.5: 13.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 07 13.2877* 00 26 14.97 +55 30 01.5 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.71 00:26:53.02 +57:56:54.5
119.66747 -4.76756 galactic Cas Second-epoch detections are separated by 5.8" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.7328+57.9490 | 00:26:53.02 +57:56:54.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:53.02 +57:56:54.5: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:53.02 +57:56:54.5: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 26 53.02 +57 56 54.5 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
ATO J006.7328+57.9490,2461234.7877,12.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
ATO J006.7328+57.9490 20260713.2877 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.68 00:12:50.82 +56:38:48.9
117.61763 -5.82612 galactic Cas Second-epoch detections are separated by 4.0" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.2378+56.6346 | 00:12:54.68 +56:38:24.4 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE SpType: F5 (LAMOST DR5) J-Ks=0.338+/-0.062 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:12:50.82 +56:38:48.9: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:12:50.82 +56:38:48.9: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 12 50.82 +56 38 48.9 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
ATO J003.2378+56.6346,2461234.7877,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.2378+56.6346 20260713.2877 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.88 00:32:59.93 +58:00:39.4
120.48326 -4.77311 galactic Cas Second-epoch detections are separated by 6.1" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:59.93 +58:00:39.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:59.93 +58:00:39.4: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:59.93 +58:00:39.4: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 59.93 +58 00 39.4 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.84 00:12:02.99 +54:10:31.6
117.12681 -8.25175 galactic Cas Second-epoch detections are separated by 4.7" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:02.99 +54:10:31.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:12:02.99 +54:10:31.6: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:12:02.99 +54:10:31.6: 13.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 07 13.2877* 00 12 02.99 +54 10 31.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.63 23:44:56.35 +55:59:43.5
113.67897 -5.67705 galactic Cas Second-epoch detections are separated by 4.9" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J356.2458+56.0037 | 23:44:58.32 +56:00:01.2 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:44:56.35 +55:59:43.5: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:44:56.35 +55:59:43.5: 13.57 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 44 56.35 +55 59 43.5 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J356.2458+56.0037,2461234.7877,12.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J356.2458+56.0037 20260713.2877 12.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:30:30.82 +55:12:25.4
119.92376 -7.54243 galactic Cas Second-epoch detections are separated by 4.7" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:30:30.82 +55:12:25.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:30.82 +55:12:25.4: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:30.82 +55:12:25.4: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 30.82 +55 12 25.4 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 00:11:28.05 +57:42:56.6
117.59573 -4.74131 galactic Cas Second-epoch detections are separated by 4.0" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:28.05 +57:42:56.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:11:28.05 +57:42:56.6: 13.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:11:28.05 +57:42:56.6: 13.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 07 13.2877* 00 11 28.05 +57 42 56.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.77 00:32:13.19 +56:54:47.6
120.29747 -5.86019 galactic Cas Second-epoch detections are separated by 8.4" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J008.0681+56.9062 | 00:32:13.19 +56:54:47.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:13.19 +56:54:47.6: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:13.19 +56:54:47.6: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 13.19 +56 54 47.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.0681+56.9062,2461234.7877,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J008.0681+56.9062 20260713.2877 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.84 00:30:33.85 +57:25:25.8
120.11275 -5.33361 galactic Cas Second-epoch detections are separated by 4.9" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:30:33.85 +57:25:25.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:33.85 +57:25:25.8: 13.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:33.85 +57:25:25.8: 13.33 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 33.85 +57 25 25.8 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 00:03:09.19 +54:08:20.2
115.82422 -8.06511 galactic Cas Second-epoch detections are separated by 6.1" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420315949250636288 | 00:03:11.07 +54:08:16.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:03:09.19 +54:08:20.2: 13.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:03:09.19 +54:08:20.2: 13.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 03 09.19 +54 08 20.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
Gaia DR3 420315949250636288,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420315949250636288 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.65 00:28:23.34 +57:29:17.3
119.82557 -5.24453 galactic Cas Second-epoch detections are separated by 4.4" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421896669015171072 | 00:28:20.98 +57:29:42.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:23.34 +57:29:17.3: 13.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:23.34 +57:29:17.3: 13.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 23.34 +57 29 17.3 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421896669015171072,2461234.7877,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421896669015171072 20260713.2877 12.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.77 00:30:45.49 +57:52:17.3
120.17508 -4.88954 galactic Cas Second-epoch detections are separated by 6.0" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.6910+57.8689 | 00:30:45.49 +57:52:17.3 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:30:45.49 +57:52:17.3: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:30:45.49 +57:52:17.3: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 30 45.49 +57 52 17.3 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
ATO J007.6910+57.8689,2461234.7877,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.6910+57.8689 20260713.2877 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.70 00:28:50.08 +55:17:34.8
119.69070 -7.43644 galactic Cas Second-epoch detections are separated by 3.7" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:50.08 +55:17:34.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:50.08 +55:17:34.8: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:50.08 +55:17:34.8: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 50.08 +55 17 34.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
target,2461234.7877,12.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 20260713.2877 12.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.54 00:24:17.66 +58:04:19.1
119.33758 -4.61022 galactic Cas Second-epoch detections are separated by 4.0" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Large-amplitude variable Gaia DR2 422117224170256384 | 00:24:14.02 +58:04:09.2 (Gaia DR3) | 2021A&A...648A..44M | | Gaia3var=NOT_AVAILABLE (the VSX policy as of May 2022 seems to be NOT to regard variables from 2021A&A...648A..44M as 'known' for the lack of classification)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:24:17.66 +58:04:19.1: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:24:17.66 +58:04:19.1: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 24 17.66 +58 04 19.1 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Large-amplitude variable Gaia DR2 422117224170256384,2461234.7877,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Large-amplitude variable Gaia DR2 422117224170256384 20260713.2877 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.66 00:03:31.55 +54:11:52.4
115.88947 -8.01742 galactic Cas Second-epoch detections are separated by 5.4" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:03:31.55 +54:11:52.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:03:31.55 +54:11:52.4: 13.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:03:31.55 +54:11:52.4: 13.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 07 13.2877* 00 03 31.55 +54 11 52.4 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:10:57.35 +57:27:23.7
117.48720 -4.98658 galactic Cas Second-epoch detections are separated by 4.4" and 1.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.7456+57.4559 | 00:10:57.35 +57:27:23.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:10:57.35 +57:27:23.7: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:10:57.35 +57:27:23.7: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 10 57.35 +57 27 23.7 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
ATO J002.7456+57.4559,2461234.7877,12.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.7456+57.4559 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.69 23:54:19.31 +58:16:05.0
115.46214 -3.77291 galactic Cas Second-epoch detections are separated by 6.0" and 0.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:54:19.31 +58:16:05.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:54:19.31 +58:16:05.0: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:54:19.31 +58:16:05.0: 13.55 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 54 19.31 +58 16 05.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.71 23:30:10.47 +55:15:36.5
111.46134 -5.79147 galactic Cas Second-epoch detections are separated by 3.4" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J352.5506+55.2613 | 23:30:10.47 +55:15:36.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:30:10.47 +55:15:36.5: 13.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:30:10.47 +55:15:36.5: 13.23 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 30 10.47 +55 15 36.5 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
ATO J352.5506+55.2613,2461234.7877,12.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
ATO J352.5506+55.2613 20260713.2877 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 00:03:49.14 +57:30:53.4
116.54880 -4.76556 galactic Cas Second-epoch detections are separated by 4.0" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J000.9392+57.5190 | 00:03:49.14 +57:30:53.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:03:49.14 +57:30:53.4: 13.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:03:49.14 +57:30:53.4: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 03 49.14 +57 30 53.4 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
ATO J000.9392+57.5190,2461234.7877,12.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.9392+57.5190 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.71 00:32:11.71 +57:56:04.3
120.37099 -4.84151 galactic Cas Second-epoch detections are separated by 5.4" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J008.0464+57.9319 | 00:32:11.71 +57:56:04.3 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:11.71 +57:56:04.3: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:11.71 +57:56:04.3: 13.38 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 11.71 +57 56 04.3 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J008.0464+57.9319,2461234.7877,12.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
ATO J008.0464+57.9319 20260713.2877 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.83 00:28:11.01 +56:33:57.5
119.71399 -6.16041 galactic Cas Second-epoch detections are separated by 7.1" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.0374+56.5678 | 00:28:11.48 +56:34:23.9 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:11.01 +56:33:57.5: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:11.01 +56:33:57.5: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 28 11.01 +56 33 57.5 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
ATO J007.0374+56.5678,2461234.7877,12.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.0374+56.5678 20260713.2877 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.75 00:28:23.84 +56:43:03.0
119.75718 -6.01216 galactic Cas Second-epoch detections are separated by 6.6" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:23.84 +56:43:03.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:28:23.84 +56:43:03.0: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:28:23.84 +56:43:03.0: 13.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 07 13.2877* 00 28 23.84 +56 43 03.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 00:31:19.40 +58:00:05.0
120.26046 -4.76599 galactic Cas Second-epoch detections are separated by 5.4" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:19.40 +58:00:05.0 (user input) | T | P | (position from user input) SpType: G1 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:31:19.40 +58:00:05.0: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:31:19.40 +58:00:05.0: 13.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 31 19.40 +58 00 05.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.85 00:32:14.25 +58:03:27.9
120.38586 -4.71905 galactic Cas Second-epoch detections are separated by 7.3" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:14.25 +58:03:27.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:32:14.25 +58:03:27.9: 13.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:32:14.25 +58:03:27.9: 13.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 32 14.25 +58 03 27.9 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.71 00:26:06.73 +56:48:59.2
119.45317 -5.88415 galactic Cas Second-epoch detections are separated by 5.9" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 421749162657219072 | 00:26:02.33 +56:49:18.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:26:06.73 +56:48:59.2: 13.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:26:06.73 +56:48:59.2: 13.33 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 26 06.73 +56 48 59.2 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 421749162657219072,2461234.7877,12.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 421749162657219072 20260713.2877 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.67 23:31:53.26 +53:31:50.7
111.16397 -7.51359 galactic Cas Second-epoch detections are separated by 6.6" and 0.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J352.9708+53.5398 | 23:31:53.26 +53:31:50.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:31:53.26 +53:31:50.7: 13.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:31:53.26 +53:31:50.7: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 31 53.26 +53 31 50.7 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
ATO J352.9708+53.5398,2461234.7877,12.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J352.9708+53.5398 20260713.2877 12.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.48 23:18:20.75 +53:43:58.6
109.32159 -6.66068 galactic Cas Second-epoch detections are separated by 4.6" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:18:20.75 +53:43:58.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:18:20.75 +53:43:58.6: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:18:20.75 +53:43:58.6: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 18 20.75 +53 43 58.6 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.83 00:08:00.46 +54:42:27.5
116.62801 -7.63166 galactic Cas Second-epoch detections are separated by 7.6" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:08:00.46 +54:42:27.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:08:00.46 +54:42:27.5: 13.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:08:00.46 +54:42:27.5: 13.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 07 13.2877* 00 08 00.46 +54 42 27.5 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.53 23:24:01.31 +54:17:19.4
110.30204 -6.42541 galactic Cas Second-epoch detections are separated by 6.0" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:01.31 +54:17:19.4 (user input) | T | P | (position from user input) J-Ks=0.268+/-0.044 (F)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:24:01.31 +54:17:19.4: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:24:01.31 +54:17:19.4: 13.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 07 13.2877* 23 24 01.31 +54 17 19.4 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.66 23:22:05.00 +53:41:32.2
109.82957 -6.89091 galactic Cas Second-epoch detections are separated by 4.5" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J350.5332+53.6952 | 23:22:07.98 +53:41:42.9 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:22:05.00 +53:41:32.2: 13.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:22:05.00 +53:41:32.2: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 22 05.00 +53 41 32.2 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
ATO J350.5332+53.6952,2461234.7877,12.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
ATO J350.5332+53.6952 20260713.2877 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.83 00:10:32.74 +56:27:15.1
117.27273 -5.96757 galactic Cas Second-epoch detections are separated by 5.0" and 1.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:32.74 +56:27:15.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:10:32.74 +56:27:15.1: 13.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:10:32.74 +56:27:15.1: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 10 32.74 +56 27 15.1 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:25:34.97 +58:03:22.1
119.50598 -4.64352 galactic Cas Second-epoch detections are separated by 5.7" and 1.1 pix
The object was found in VSX 1" Gaia DR3 421929306463080064
Type: RS
# Max. Min./Amp. JD0 Period
17.390 G 17.550 G F
ATTENTION: measured mag 12.73 is 4.7 mag brighter than the VSX record maximum brightness 17.39 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:25:34.97 +58:03:22.1: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:25:34.97 +58:03:22.1: 13.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 07 13.2877* 00 25 34.97 +58 03 22.1 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 421929306463080064,2461234.7877,12.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421929306463080064 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.68 00:04:33.76 +55:40:27.1
116.31126 -6.59383 galactic Cas Second-epoch detections are separated by 5.9" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420836739804625792 | 00:04:35.69 +55:40:53.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A7V (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:04:33.76 +55:40:27.1: 13.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:04:33.76 +55:40:27.1: 13.53 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 04 33.76 +55 40 27.1 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 420836739804625792,2461234.7877,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420836739804625792 20260713.2877 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.84 23:29:53.81 +51:18:40.8
110.17680 -9.52974 galactic Cas Second-epoch detections are separated by 5.8" and 0.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:53.81 +51:18:40.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:29:53.81 +51:18:40.8: 13.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:29:53.81 +51:18:40.8: 13.22 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 29 53.81 +51 18 40.8 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:18:10.98 +58:04:54.5
118.53389 -4.50569 galactic Cas Second-epoch detections are separated by 4.2" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:18:10.98 +58:04:54.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:18:10.98 +58:04:54.5: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:18:10.98 +58:04:54.5: 13.39 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 18 10.98 +58 04 54.5 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.73 00:09:52.05 +57:38:56.6
117.37328 -4.77335 galactic Cas Second-epoch detections are separated by 5.4" and 0.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:52.05 +57:38:56.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:09:52.05 +57:38:56.6: 13.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:09:52.05 +57:38:56.6: 13.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 07 13.2877* 00 09 52.05 +57 38 56.6 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.68 23:20:55.75 +49:40:47.1
108.26116 -10.59634 galactic And Second-epoch detections are separated by 6.5" and 1.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:20:55.75 +49:40:47.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:20:55.75 +49:40:47.1: 13.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:20:55.75 +49:40:47.1: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 20 55.75 +49 40 47.1 12.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 00:08:36.81 +56:47:35.8
117.06456 -5.58982 galactic Cas Second-epoch detections are separated by 4.2" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.1498+56.7934 | 00:08:36.81 +56:47:35.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:08:36.81 +56:47:35.8: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:08:36.81 +56:47:35.8: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 08 36.81 +56 47 35.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
ATO J002.1498+56.7934,2461234.7877,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
ATO J002.1498+56.7934 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 00:09:45.88 +57:34:08.0
117.34666 -4.85024 galactic Cas Second-epoch detections are separated by 4.6" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:45.88 +57:34:08.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:09:45.88 +57:34:08.0: 13.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:09:45.88 +57:34:08.0: 13.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 09 45.88 +57 34 08.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 23:33:01.14 +54:05:03.0
111.49353 -7.03684 galactic Cas Second-epoch detections are separated by 7.7" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:01.14 +54:05:03.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:33:01.14 +54:05:03.0: 13.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:33:01.14 +54:05:03.0: 13.34 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 33 01.14 +54 05 03.0 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.75 23:26:48.98 +50:31:18.7
109.45337 -10.12209 galactic And Second-epoch detections are separated by 7.6" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:26:48.98 +50:31:18.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:26:48.98 +50:31:18.7: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:26:48.98 +50:31:18.7: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 26 48.98 +50 31 18.7 12.8 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,2461234.7877,12.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 20260713.2877 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.80 00:01:36.47 +56:39:02.0
116.08895 -5.55769 galactic Cas Second-epoch detections are separated by 1.9" and 1.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:36.47 +56:39:02.0 (user input) | T | P | (position from user input) SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:01:36.47 +56:39:02.0: 13.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:01:36.47 +56:39:02.0: 13.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 00 01 36.47 +56 39 02.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.89 23:55:07.55 +57:18:21.1
115.35606 -4.73526 galactic Cas Second-epoch detections are separated by 1.0" and 1.3 pix
The object was found in VSX23" Gaia DR3 1998084314423556224
Type: S
# Max. Min./Amp. JD0 Period
17.470 G 17.740 G
ATTENTION: measured mag 12.89 is 4.6 mag brighter than the VSX record maximum brightness 17.47 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:55:07.55 +57:18:21.1: 13.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:55:07.55 +57:18:21.1: 13.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 55 07.55 +57 18 21.1 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998084314423556224,2461234.7877,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1998084314423556224 20260713.2877 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.64 23:18:49.44 +52:54:36.8
109.09587 -7.45553 galactic And Second-epoch detections are separated by 6.0" and 1.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 J349.7202+52.9032 | 23:18:49.44 +52:54:36.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:18:49.44 +52:54:36.8: 13.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:18:49.44 +52:54:36.8: 13.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 18 49.44 +52 54 36.8 12.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
ATO J349.7202+52.9032,2461234.7877,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J349.7202+52.9032 20260713.2877 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.69 23:57:42.81 +56:07:21.5
115.45193 -5.96689 galactic Cas Second-epoch detections are separated by 4.1" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:42.81 +56:07:21.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:57:42.81 +56:07:21.5: 13.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:57:42.81 +56:07:21.5: 13.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 57 42.81 +56 07 21.5 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.62 23:22:14.91 +54:54:43.9
110.26973 -5.75189 galactic Cas Second-epoch detections are separated by 8.3" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:14.91 +54:54:43.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:22:14.91 +54:54:43.9: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:22:14.91 +54:54:43.9: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 22 14.91 +54 54 43.9 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,2461234.7877,12.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 20260713.2877 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.72 23:41:30.57 +54:11:00.8
112.72341 -7.29634 galactic Cas Second-epoch detections are separated by 5.8" and 1.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1994162287727136128 | 23:41:33.53 +54:11:04.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:41:30.57 +54:11:00.8: 13.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:41:30.57 +54:11:00.8: 13.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 41 30.57 +54 11 00.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 1994162287727136128,2461234.7877,12.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
Gaia DR3 1994162287727136128 20260713.2877 12.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.79 23:18:57.52 +50:32:10.2
108.26642 -9.68352 galactic And Second-epoch detections are separated by 6.9" and 0.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:18:57.52 +50:32:10.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:18:57.52 +50:32:10.2: 13.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:18:57.52 +50:32:10.2: 13.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 18 57.52 +50 32 10.2 12.8 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,2461234.7877,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.74 23:45:24.27 +54:41:14.8
113.40733 -6.95856 galactic Cas Second-epoch detections are separated by 4.2" and 1.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:45:24.27 +54:41:14.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:45:24.27 +54:41:14.8: 13.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:45:24.27 +54:41:14.8: 13.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 45 24.27 +54 41 14.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
target,2461234.7877,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.76 23:26:15.13 +50:32:28.6
109.37377 -10.07440 galactic And Second-epoch detections are separated by 6.0" and 1.3 pix
The object was found in VSX16" ZTF J232616.57+503220.3
Type: EW
# Max. Min./Amp. JD0 Period
17.153 r Y 0.144 r 2458361.80420 0.249264600000
ATTENTION: measured mag 12.76 is 4.2 mag brighter than the VSX record maximum brightness 17.01 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:26:15.13 +50:32:28.6: 13.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:26:15.13 +50:32:28.6: 13.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 26 15.13 +50 32 28.6 12.8 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 J232616.57+503220.3,2461234.7877,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J232616.57+503220.3 20260713.2877 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.89 23:23:06.62 +51:44:21.7
109.30773 -8.78058 galactic And Second-epoch detections are separated by 6.0" and 0.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J350.7665+51.7439 | 23:23:06.62 +51:44:21.7 (user input) | DBF (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:23:06.62 +51:44:21.7: 13.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:23:06.62 +51:44:21.7: 13.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 23 06.62 +51 44 21.7 12.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J350.7665+51.7439,2461234.7877,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J350.7665+51.7439 20260713.2877 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.72 23:14:28.99 +56:13:52.5
109.70613 -4.13052 galactic Cas Second-epoch detections are separated by 8.3" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:14:28.99 +56:13:52.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:14:28.99 +56:13:52.5: 13.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:14:28.99 +56:13:52.5: 13.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 07 13.2877* 23 14 28.99 +56 13 52.5 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.83 23:23:09.93 +54:20:50.5
110.20340 -6.32834 galactic Cas Second-epoch detections are separated by 7.2" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:09.93 +54:20:50.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:23:09.93 +54:20:50.5: 13.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:23:09.93 +54:20:50.5: 13.27 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 23 09.93 +54 20 50.5 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 12.85 23:35:20.92 +56:14:00.8
112.45302 -5.08230 galactic Cas Second-epoch detections are separated by 4.5" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:35:20.92 +56:14:00.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:35:20.92 +56:14:00.8: 13.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:35:20.92 +56:14:00.8: 13.55 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 35 20.92 +56 14 00.8 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.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 07 13.2877 2461234.7877 12.72 23:21:19.26 +52:54:32.6
109.45139 -7.58781 galactic And Second-epoch detections are separated by 6.5" and 1.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:19.26 +52:54:32.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:21:19.26 +52:54:32.6: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:21:19.26 +52:54:32.6: 13.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 21 19.26 +52 54 32.6 12.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461234.7877,12.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 20260713.2877 12.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 13.2877 2461234.7877 11.76 23:29:09.54 +54:20:30.1
111.03264 -6.61810 galactic Cas Second-epoch detections are separated by 3.0" and 1.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:09.54 +54:20:30.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:29:09.54 +54:20:30.1: 13.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:29:09.54 +54:20:30.1: 13.38 +/- 0.35 detection
Forced photometry reference-image weighted average: 13.38 +/- 0.35
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 13.2877* 23 29 09.54 +54 20 30.1 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,2461234.7877,11.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260713.2877 11.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461206.83945590 15.06.2026 08:08:38.990 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
First image: 2461206.83945590 15.06.2026 08:08:38.990 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
Last image: 2461234.78791078 13.07.2026 06:54:25.491 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 40
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.79
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: 13 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): 20762
Objects passed selection criteria: 20749
Measurements per detected object (mean, median, min, max): 3.7 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.7 4.0 2 4
Average stars detected per image: 19789.5
Average stars matched: 18555.5 (93.7644 %)
Memory usage VmPeak: 129708 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Sat Jul 11 21:08:03 CDT 2026
VaST build number 1.0rc89-146-gb95cfcf3
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-07-11)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Mon Jul 13 02:04:02 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: 2461206.83945590 15.06.2026 08:08:38.990 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
First image: 2461206.83945590 15.06.2026 08:08:38.990 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
Last image: 2461234.78791078 13.07.2026 06:54:25.491 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 1237
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.45
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: 329 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): 161659
Objects passed selection criteria: 161176
Measurements per detected object (mean, median, min, max): 3.6 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.6 4.0 2 4
Average stars detected per image: 152737
Average stars matched: 142541 (93.3246 %)
Memory usage VmPeak: 1986012 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Sat Jul 11 21:08:03 CDT 2026
VaST build number 1.0rc89-146-gb95cfcf3
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-07-11)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Mon Jul 13 02:23:28 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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.cat to cache
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
Checking WCS cache directory local_wcs_cache
Checking 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: 2461234.78742690
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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits exists and is non-empty
Saving wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits'
wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits exists and is non-empty
Saving wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits'
wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits'
wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits (1st reference image)
verification OK: wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
Image size: 927.0'x616.4' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 00:00:01.466 +54:00:23.28 J2000 4789.000 3195.000
###################################
The image scale is 5.81"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.8" and 8.7"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
Image size: 927.2'x616.6' 15.5(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:51.671 +54:03:06.89 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 00:00:01.466 +54:00:23.28
Second-epoch image center 23:59:51.671 +54:03:06.89
Angular distance between the image centers 0.0514 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
Image size: 927.2'x616.5' 15.5(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:50.924 +54:03:03.23 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 00:00:01.466 +54:00:23.28
Second-epoch image center 23:59:50.924 +54:03:03.23
Angular distance between the image centers 0.0514 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:51.671 +54:03:06.89
Second-epoch second image center 23:59:50.924 +54:03:03.23
Angular distance between the image centers 0.00209 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for a parallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits &> /tmp/tmp.753MhYQVNI
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits &> /tmp/tmp.EIjJX10kVv
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits &> /tmp/tmp.NqeUpQtecn
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits &> /tmp/tmp.IC7UZIONyZ
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat
Found non-empty wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat
The reference image (wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits) and catalog (wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat) found
'wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat' -> 'wcsmag.cat'
Read 23386 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0031 to 359.9999 deg, Dec +48.2162 to +59.2586 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.0031 to 359.9999 deg, Dec 48.2162 to 59.2586 deg
Loaded 153985 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): 53 out of 58 total matches.
Matched with Tycho-2 58 out of 23386 detected stars.
ERROR: only 53 of 23386 stars detected on the reference image matched the Tycho-2 photometric calibration catalog (0.23%) - the reference image plate solution is likely broken and the magnitude calibration is unreliable
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.473500
a=0.000000 b=1.000000 c=22.473500
From vast_summary.log: estimated ref. image limiting mag.: -7.79
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.68
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.68
Lightcurve magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 23386 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0031 to 359.9999 deg, Dec +48.2162 to +59.2586 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.0031 to 359.9999 deg, Dec 48.2162 to 59.2586 deg
Loaded 153985 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): 53 out of 58 total matches.
Matched with Tycho-2 58 out of 23386 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits:
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits (aperture=6.2)
Read 23366 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0031 to 360.0000 deg, Dec +48.2161 to +59.2689 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.0031 to 360.0000 deg, Dec 48.2161 to 59.2689 deg
Loaded 154106 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): 50 out of 55 total matches.
Matched with Tycho-2 55 out of 23366 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits:
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits (aperture=6.3)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 33 candidate transients before the final filtering. (Hard limit: 10000)
Median FWHM seeing for isolated stars:
2.3 pix Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
2.4 pix Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
2.5 pix fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
2.5 pix fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
2.3 pix wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
2.4 pix wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
Limiting magnitude estimates:
14.7 mag. Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
14.7 mag. Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
14.9 mag. fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
14.8 mag. fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
All-image limiting magnitude estimate: 14.8 (SNR ) 11.8 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.5 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.753MhYQVNI (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits' -> 'wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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-06-15_03-08-38_20.00sec_4.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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=1910, bad_region=5051, passed=23386
Got 23386 stars (including 16726 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat
util/solve_plate_with_UCAC5 got 23386 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.0'
Seting catalog search parameters based on the expected field of view 927.0 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012875 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010300 (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.9996 through 0 to 14.8812, gap 14.8812 to 344.9996
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 325 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 241 matched stars entering correct_measured_positions(), 168 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.53"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 233 matched stars entering correct_measured_positions(), 4908 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.09"
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.9814 through 0 to 14.9033, gap 14.9033 to 344.9814
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 397 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(), 4961 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.99"
Accuracy estimation diagnostic: 325 matched stars entering correct_measured_positions(), 6645 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.24"
Excluding outliers - 325 stars left (next iteration limit 256)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits N_match=325 sigma_overall_arcsec=11.131 sigma_q1_arcsec=25.602 sigma_q2_arcsec=32.104 sigma_q3_arcsec=8.250 sigma_q4_arcsec=9.745 n_q1=41 n_q2=23 n_q3=116 n_q4=145 worst_quadrant_to_overall_ratio=2.884
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits -region wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.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.EIjJX10kVv (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.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-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits' -> 'wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.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-06-15_03-09-29_20.00sec_5.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-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.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=1872, bad_region=4985, passed=23366
Got 23366 stars (including 16797 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits.wcscat
util/solve_plate_with_UCAC5 got 23366 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.1'
Seting catalog search parameters based on the expected field of view 927.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012876 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010301 (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.0112 through 0 to 14.8810, gap 14.8810 to 345.0112
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 331 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 239 matched stars entering correct_measured_positions(), 165 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.65"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 231 matched stars entering correct_measured_positions(), 4693 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.88"
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.9936 through 0 to 14.9023, gap 14.9023 to 344.9936
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 397 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 321 matched stars entering correct_measured_positions(), 4741 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.79"
Accuracy estimation diagnostic: 315 matched stars entering correct_measured_positions(), 6313 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.43"
Excluding outliers - 315 stars left (next iteration limit 254)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits N_match=315 sigma_overall_arcsec=10.449 sigma_q1_arcsec=28.329 sigma_q2_arcsec=30.359 sigma_q3_arcsec=8.438 sigma_q4_arcsec=7.803 n_q1=34 n_q2=19 n_q3=120 n_q4=142 worst_quadrant_to_overall_ratio=2.905
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.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-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits -region wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.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.NqeUpQtecn (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.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=2628, bad_region=6063, passed=27526
Got 27526 stars (including 19264 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat
util/solve_plate_with_UCAC5 got 27526 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.2'
Seting catalog search parameters based on the expected field of view 927.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012878 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010302 (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.9609 through 0 to 14.9338, gap 14.9338 to 344.9609
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 313 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 223 matched stars entering correct_measured_positions(), 145 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.78"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 213 matched stars entering correct_measured_positions(), 4920 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.93"
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.9523 through 0 to 14.9564, gap 14.9564 to 344.9523
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 386 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 313 matched stars entering correct_measured_positions(), 4981 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.81"
Accuracy estimation diagnostic: 307 matched stars entering correct_measured_positions(), 7376 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.84"
Excluding outliers - 307 stars left (next iteration limit 234)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits N_match=307 sigma_overall_arcsec=10.952 sigma_q1_arcsec=30.063 sigma_q2_arcsec=25.182 sigma_q3_arcsec=8.244 sigma_q4_arcsec=11.272 n_q1=35 n_q2=21 n_q3=124 n_q4=127 worst_quadrant_to_overall_ratio=2.745
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits -region wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.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.IC7UZIONyZ (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.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=2632, bad_region=6037, passed=27466
Got 27466 stars (including 19234 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat
util/solve_plate_with_UCAC5 got 27466 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 927.2'
Seting catalog search parameters based on the expected field of view 927.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012878 (46.4 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010302 (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.9611 through 0 to 14.8810, gap 14.8810 to 344.9611
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 318 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 225 matched stars entering correct_measured_positions(), 148 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.21"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 216 matched stars entering correct_measured_positions(), 4861 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.96"
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.9572 through 0 to 14.9074, gap 14.9074 to 344.9572
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 374 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 310 matched stars entering correct_measured_positions(), 4903 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.87"
Accuracy estimation diagnostic: 309 matched stars entering correct_measured_positions(), 6945 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.46"
Excluding outliers - 309 stars left (next iteration limit 237)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits N_match=309 sigma_overall_arcsec=10.917 sigma_q1_arcsec=31.865 sigma_q2_arcsec=28.052 sigma_q3_arcsec=9.192 sigma_q4_arcsec=9.806 n_q1=33 n_q2=18 n_q3=127 n_q4=131 worst_quadrant_to_overall_ratio=2.919
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits -region wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits sigma_overall=11.131 worst_q_ratio=2.884
ref2=Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits sigma_overall=10.449 worst_q_ratio=2.905
new1=fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits sigma_overall=10.952 worst_q_ratio=2.745
new2=fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits sigma_overall=10.917 worst_q_ratio=2.919
reference average sigma_overall=10.79 worst_q_ratio=2.8945
warn-on-ratio threshold: 2.0x reference
###################################
Astrometric residual vector field (catalog-matched stars):
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006_astrometric_residuals.png (325 matched stars from wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.67 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007_astrometric_residuals.png (315 matched stars from wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.55 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074_astrometric_residuals.png (307 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.96 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075_astrometric_residuals.png (309 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.34 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-53-43_20.00sec_5.00C_LIGHT_0074.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-04-Q2b1x1_015803_TTUQ2b1x1_1643025_V0JaaTYt/wcs_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075.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-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:11:50.83 +56:02:36.8: 14.47 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:58:40.78 +53:23:43.4: 11.30 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:02:20.47 +54:07:58.1: 14.51 +/- 0.16 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:11:50.83 +56:02:36.8: 14.40 +/- 0.20 detection
Forced photometry reference-image weighted average: 14.43 +/- 0.15
Forced photometry filter KEPT candidate at 23:11:50.83 +56:02:36.8: ref_mag=14.43 +/- 0.15 new_mean_mag=11.1794 delta=3.25 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:58:40.78 +53:23:43.4: 11.28 +/- 0.01 detection
Forced photometry reference-image weighted average: 11.29 +/- 0.01
Forced photometry filter REJECTED candidate at 23:58:40.78 +53:23:43.4: ref_mag=11.29 +/- 0.01 new_mean_mag=11.2962 delta=-0.00 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:02:20.47 +54:07:58.1: 14.78 +/- 0.22 detection
Forced photometry reference-image weighted average: 14.61 +/- 0.13
Forced photometry filter KEPT candidate at 00:02:20.47 +54:07:58.1: ref_mag=14.61 +/- 0.13 new_mean_mag=11.5921 delta=3.01 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 23:34:47.85 +54:35:22.1: 15.31 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-08-38_20.00sec_4.90C_LIGHT_0006.fits at 00:09:30.37 +51:35:57.4: 12.62 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 00:09:30.37 +51:35:57.4: 12.68 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.65 +/- 0.02
Forced photometry filter KEPT candidate at 00:09:30.37 +51:35:57.4: ref_mag=12.65 +/- 0.02 new_mean_mag=10.0231 delta=2.63 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-06-15_03-09-29_20.00sec_5.00C_LIGHT_0007.fits at 23:34:47.85 +54:35:22.1: 15.24 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.24 +/- 0.34
Forced photometry filter KEPT candidate at 23:34:47.85 +54:35:22.1: ref_mag=15.24 +/- 0.34 new_mean_mag=11.8789 delta=3.36 (need > 0.90)
Adding exclusion_list_local.txt__out05724.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31307.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31333.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31376.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 29s
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: 4s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31255_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31255_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31259_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31259_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31263_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31263_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31264_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31264_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31265_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31265_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31307_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 31307_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31315_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31315_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31329_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31329_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31330_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31330_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31333_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 31333_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31341_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31341_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31344_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31344_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31346_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31346_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31347_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31347_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31349_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31349_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31350_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31350_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31352_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31352_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31353_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31353_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31354_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31354_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31355_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31355_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31357_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31357_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31359_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31359_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (44.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31360_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31360_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31362_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31362_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31364_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31364_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31368_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31368_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31370_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31370_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31372_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31372_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31374_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31374_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31375_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 31375_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31376_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 31376_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 05724_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 05724_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 17508_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 17508_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190892_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190892_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190905_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190905_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190921_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 190921_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190949_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190949_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190950_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 190950_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190954_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190954_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190955_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190955_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (27.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190965_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190965_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190974_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 190974_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190979_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 190979_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190982_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 190982_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190983_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190983_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190986_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190986_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190995_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190995_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (28.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190997_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 190997_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (27.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191003_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191003_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191006_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191006_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191008_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191008_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191017_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191017_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191025_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191025_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191031_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191031_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191035_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191035_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191038_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191038_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191040_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191040_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191043_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191043_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191046_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191046_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191048_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191048_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191052_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191052_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191059_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191059_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (38.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191061_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191061_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191063_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191063_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191064_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191064_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191066_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191066_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191074_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191074_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191076_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191076_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191078_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191078_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191082_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191082_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191083_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191083_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191087_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191087_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191091_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191091_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (26.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191093_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191093_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191101_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191101_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191107_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191107_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191110_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191110_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191111_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191111_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191112_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191112_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191113_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191113_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191119_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191119_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191121_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191121_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191124_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191124_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191127_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191127_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191129_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191129_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191133_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191133_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191134_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191134_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191136_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191136_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191139_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191139_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191144_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191144_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191146_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191146_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191148_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191148_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191151_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191151_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191156_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191156_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191158_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191158_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191159_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191159_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191161_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191161_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191163_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191163_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191165_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191165_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191166_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191166_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191170_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191170_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191171_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191171_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191176_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191176_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191177_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191177_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (35.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191179_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191179_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191181_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191181_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191189_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191189_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191192_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191192_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191196_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191196_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191199_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191199_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191204_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191204_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191205_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191205_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191206_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191206_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191208_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191208_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191209_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191209_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (29.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191211_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191211_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191218_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191218_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191221_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191221_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191222_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191222_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (27.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191225_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191225_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191227_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191227_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191231_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191231_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191233_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191233_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (36.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191235_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191235_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191236_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191236_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191242_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191242_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191247_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191247_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191248_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191248_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191258_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191258_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (30.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191259_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191259_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191261_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191261_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191264_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191264_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191269_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191269_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191270_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191270_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191271_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191271_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191273_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191273_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (26.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191275_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191275_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191282_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191282_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191283_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191283_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191286_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191286_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191287_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191287_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191288_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191288_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (35.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191289_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191289_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191290_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191290_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191291_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191291_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191292_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191292_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191298_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191298_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191306_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191306_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191307_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191307_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191310_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191310_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191311_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191311_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191316_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191316_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191318_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191318_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191320_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191320_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191322_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191322_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191323_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191323_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191326_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191326_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191327_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191327_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191329_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191329_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191332_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191332_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191333_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191333_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191336_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191336_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191339_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191339_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191342_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191342_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (29.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191344_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191344_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191345_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191345_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191349_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191349_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191350_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191350_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (33.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191351_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191351_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191355_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191355_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191367_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191367_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191368_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191368_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191370_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191370_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191371_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191371_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191372_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191372_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191373_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191373_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191375_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191375_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191376_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191376_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191378_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191378_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191380_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191380_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191382_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191382_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191384_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191384_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (38.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191388_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191388_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191392_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191392_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191393_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191393_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (36.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191396_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191396_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191397_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191397_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191400_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191400_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191401_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191401_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (59.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191403_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191403_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191408_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191408_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191409_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191409_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (8.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191410_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191410_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191412_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191412_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (35.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191414_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191414_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191415_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191415_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191417_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191417_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191418_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191418_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191420_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191420_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191421_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191421_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191422_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191422_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191424_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191424_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191425_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191425_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (31.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191426_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191426_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (30.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191428_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191428_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191430_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191430_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191433_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191433_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191434_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191434_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (40.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191436_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191436_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191445_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191445_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191447_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191447_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191452_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191452_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191454_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191454_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191455_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191455_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191456_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191456_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191457_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191457_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191459_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191459_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191460_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191460_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191461_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191461_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191464_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191464_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191465_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191465_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191470_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191470_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191471_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191471_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191472_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191472_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191478_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191478_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191479_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191479_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191480_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191480_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191484_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191484_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191486_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191486_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191491_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191491_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191497_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191497_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191498_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191498_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191500_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191500_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191502_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191502_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191503_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191503_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191504_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191504_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191506_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191506_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191507_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191507_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191508_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191508_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191509_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191509_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191515_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191515_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191517_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191517_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191520_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191520_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191522_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191522_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191527_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191527_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191529_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191529_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191540_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191540_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191541_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191541_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191542_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191542_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191546_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191546_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191547_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191547_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191550_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191550_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191555_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191555_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191556_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191556_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191559_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191559_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191565_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191565_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (41.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191566_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191566_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191569_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191569_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (23.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191573_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191573_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191575_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191575_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191579_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191579_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191580_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191580_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191584_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191584_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191586_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191586_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191589_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191589_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191590_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191590_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191594_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191594_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191595_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191595_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191598_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191598_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191600_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191600_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191606_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191606_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191607_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191607_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191608_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191608_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 00:28:10.72 +56:29:48.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191611_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191611_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191612_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191612_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191613_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191613_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191616_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191616_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191650_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191650_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191663_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191663_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191667_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191667_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191680_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191680_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191688_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191688_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191692_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191692_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191697_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191697_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191709_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191709_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (23.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191712_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191712_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191730_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191730_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191741_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191741_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191743_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191743_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191745_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191745_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191768_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191768_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (33.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191801_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191801_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191806_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191806_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191808_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191808_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191813_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191813_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191827_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191827_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191830_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191830_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191843_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191843_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191846_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191846_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191848_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191848_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191850_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191850_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191853_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191853_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191865_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191865_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191869_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191869_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191876_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191876_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191887_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191887_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191888_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191888_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (40.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191889_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191889_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191891_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191891_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191894_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191894_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191896_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191896_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191915_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191915_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191920_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191920_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191922_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191922_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191923_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191923_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (30.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191925_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191925_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191926_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191926_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191931_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191931_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (43.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191933_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191933_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191937_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191937_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191938_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191938_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191943_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191943_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (33.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191945_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191945_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191948_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191948_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191950_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191950_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191954_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191954_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191966_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191966_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (53.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191968_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191968_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191969_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191969_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191971_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191971_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191973_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191973_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191974_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191974_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191977_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191977_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191980_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191980_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191986_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 191986_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191989_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191989_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191996_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191996_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (29.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191999_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 191999_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192000_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192000_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192006_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192006_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192011_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192011_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192028_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192028_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192040_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192040_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192044_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192044_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192046_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192046_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192050_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192050_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192052_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192052_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192053_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192053_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192059_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192059_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192060_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192060_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192062_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192062_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192067_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192067_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192068_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192068_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192073_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192073_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192075_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192075_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192076_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192076_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192081_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192081_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192084_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192084_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192086_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192086_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192091_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192091_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192093_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192093_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192099_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192099_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192106_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192106_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192107_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192107_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192110_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192110_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192112_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192112_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192113_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192113_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (38.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192117_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192117_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (42.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192126_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192126_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192127_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192127_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192130_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192130_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 00:08:14.15 +55:11:26.0 in APASS (TIMEOUTCOMMAND_GAIA_VIZIER=#timeout 40 #, MAG_MEAN=12.04, MAG_FAINT_SEARCH_LIMIT=13.02)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192137_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192137_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192138_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192138_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192146_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192146_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192156_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192156_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192159_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192159_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192161_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192161_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192170_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192170_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192175_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192175_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (40.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192179_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192179_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192184_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192184_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192185_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192185_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192188_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192188_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192189_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192189_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192194_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192194_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192202_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192202_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192204_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192204_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192209_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192209_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192213_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192213_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192217_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192217_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192219_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192219_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192224_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192224_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192226_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192226_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192230_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192230_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192236_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192236_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192237_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192237_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192240_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192240_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (33.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192247_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192247_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192249_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192249_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (30.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192253_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192253_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192264_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192264_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192274_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192274_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192276_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192276_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192277_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192277_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192285_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192285_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192287_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192287_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192292_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192292_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192293_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192293_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (33.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192303_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192303_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192309_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192309_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192311_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192311_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192313_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192313_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192314_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192314_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192315_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192315_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192317_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192317_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192319_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192319_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (37.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192321_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192321_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192333_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192333_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192334_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192334_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192337_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192337_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192341_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192341_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192343_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192343_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192345_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192345_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192347_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192347_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192349_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192349_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192350_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192350_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192353_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192353_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192357_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192357_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192358_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192358_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192359_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192359_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192361_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192361_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192362_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192362_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192366_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192366_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192373_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192373_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192374_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192374_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192376_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192376_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192380_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192380_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192381_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192381_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192389_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192389_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192397_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192397_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192398_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192398_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192400_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192400_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192401_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192401_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192403_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192403_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192407_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192407_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192408_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192408_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192409_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192409_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (38.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192411_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192411_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192412_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192412_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192415_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192415_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192416_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192416_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192417_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192417_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192419_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192419_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192422_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192422_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192423_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192423_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192426_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192426_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192429_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192429_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192431_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192431_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192433_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192433_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192434_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192434_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192435_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192435_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192436_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192436_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192438_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192438_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192439_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192439_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192441_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192441_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192443_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192443_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192447_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192447_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192448_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192448_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192451_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192451_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192452_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192452_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192453_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192453_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192454_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192454_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192460_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192460_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192462_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192462_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192464_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192464_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192468_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192468_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192469_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192469_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192474_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192474_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192479_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192479_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192482_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192482_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192484_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192484_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192488_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192488_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192491_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192491_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192492_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192492_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192493_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192493_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192494_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192494_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192495_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192495_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192497_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192497_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192498_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192498_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192502_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192502_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192508_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192508_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192512_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192512_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192515_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192515_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192521_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192521_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192528_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192528_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192530_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192530_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192532_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192532_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192533_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192533_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192538_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192538_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 00:10:18.58 +57:08:35.4 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192542_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192542_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192543_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192543_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192546_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192546_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192552_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192552_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192556_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192556_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (51.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192557_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192557_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192558_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192558_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192559_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192559_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192561_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192561_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192562_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192562_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192565_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192565_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192569_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192569_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192570_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192570_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192571_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192571_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192575_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192575_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192580_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192580_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192582_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192582_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192583_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192583_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192584_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192584_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192585_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192585_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192586_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192586_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192587_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192587_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192588_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192588_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (40.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192589_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192589_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192594_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192594_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192595_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192595_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192597_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192597_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192598_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192598_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192599_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192599_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192604_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192604_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192605_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192605_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192606_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192606_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192607_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192607_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192608_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192608_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192609_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192609_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192612_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192612_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192617_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192617_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192621_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192621_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192622_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192622_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192625_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192625_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192628_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192628_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192629_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192629_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192631_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192631_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192633_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192633_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192637_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192637_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192639_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192639_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (39.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192642_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192642_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192645_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192645_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192646_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192646_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (26.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192649_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192649_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192653_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192653_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192656_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192656_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192657_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192657_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192658_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192658_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192660_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192660_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192662_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192662_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192664_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192664_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192665_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192665_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192667_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192667_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192670_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192670_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192672_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192672_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192673_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192673_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192674_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192674_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192675_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192675_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192677_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192677_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192679_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192679_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192683_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192683_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192686_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192686_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192687_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192687_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192688_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192688_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (38.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192691_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192691_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (37.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192692_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192692_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192694_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192694_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192697_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192697_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192698_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192698_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192699_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192699_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192701_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192701_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192702_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192702_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192703_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192703_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.2 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192708_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192708_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192713_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192713_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (25.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192714_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192714_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192715_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192715_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192722_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192722_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192726_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192726_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192728_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192728_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192729_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192729_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192730_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192730_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192731_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192731_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192732_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192732_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192735_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192735_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192739_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192739_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192741_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192741_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192742_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192742_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192743_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192743_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192751_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192751_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192752_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192752_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192754_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192754_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192755_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192755_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192757_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192757_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192762_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192762_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192763_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192763_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (39.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192766_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192766_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192770_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192770_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192772_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192772_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192774_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192774_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192783_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192783_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192784_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192784_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192787_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192787_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192789_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192789_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192792_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192792_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192794_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192794_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192795_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192795_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192796_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192796_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192798_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192798_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192800_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192800_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192803_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192803_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (33.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192804_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192804_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192805_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192805_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192806_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192806_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192808_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192808_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192810_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192810_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192811_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192811_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192812_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192812_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192814_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192814_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192815_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192815_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192816_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192816_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192817_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192817_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192822_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192822_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192823_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192823_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192826_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192826_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192829_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192829_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192832_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192832_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192837_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192837_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192838_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192838_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192839_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192839_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192841_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192841_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192843_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192843_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192846_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192846_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192853_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192853_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (32.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192854_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192854_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192855_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192855_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192868_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192868_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192869_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192869_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192871_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192871_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192872_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192872_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192873_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192873_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192877_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192877_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192878_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192878_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192879_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192879_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192880_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192880_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192883_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192883_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192884_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192884_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192885_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192885_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (26.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192888_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192888_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192889_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192889_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192890_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192890_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192891_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192891_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192896_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192896_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192897_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192897_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192899_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192899_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192901_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192901_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192902_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192902_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192903_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192903_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192905_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192905_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192912_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192912_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192915_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192915_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192917_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192917_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192920_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192920_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192923_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192923_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192929_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192929_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192931_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192931_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192933_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192933_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192934_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192934_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192936_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192936_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192937_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192937_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192940_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192940_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192943_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192943_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192944_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192944_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192945_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192945_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192947_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192947_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192948_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192948_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192950_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192950_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192956_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192956_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192960_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192960_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192961_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192961_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192965_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192965_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192969_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192969_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (40.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192972_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192972_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192974_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192974_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192976_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192976_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192979_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192979_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192980_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192980_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192982_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192982_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192984_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192984_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192985_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192985_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192986_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192986_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192987_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192987_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192988_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192988_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192990_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192990_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192991_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192991_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192993_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 192993_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192994_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192994_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192996_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 192996_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193003_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193003_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193005_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193005_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 00:10:22.52 +54:46:32.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.71, MAG_FAINT_SEARCH_LIMIT=13.69)GAIADR2_OUTPUT=# 3.522 420222525123066880 002.59396418234 +54.77480228816 11.5173 10.7049 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.522#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193007_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193007_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193008_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193008_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193011_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193011_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193012_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193012_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193014_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193014_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193016_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193016_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193019_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193019_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193021_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193021_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193024_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193024_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193026_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193026_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (30.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193030_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193030_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (24.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193031_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193031_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193033_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193033_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193037_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193037_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193043_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193043_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193045_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193045_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193049_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193049_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193050_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193050_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193054_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193054_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (27.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193055_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193055_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193057_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193057_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193058_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193058_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193063_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193063_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193065_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193065_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193066_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193066_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193067_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193067_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193068_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193068_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193077_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193077_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193078_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193078_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193079_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193079_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193080_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193080_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193082_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193082_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (36.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193084_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193084_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (39.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193086_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193086_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (28.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193088_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193088_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193093_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193093_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (39.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193096_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193096_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193098_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193098_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193100_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193100_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193104_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193104_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193105_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193105_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193109_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193109_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193110_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193110_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193115_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193115_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 23:20:44.58 +50:00:39.4 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.64, MAG_FAINT_SEARCH_LIMIT=13.62)GAIADR2_OUTPUT=# 3.290 1991162064090339968 350.18636747956 +50.01176774834 12.2818 11.9920 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.290#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.8#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193116_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193116_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193120_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193120_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193122_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193122_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193124_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193124_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (28.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193129_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193129_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193132_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193132_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193134_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193134_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193135_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193135_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193136_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193136_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193138_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193138_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193139_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193139_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193145_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193145_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193148_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193148_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (28.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193150_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193150_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193152_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193152_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (31.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193155_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193155_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193156_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193156_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (36.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193161_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193161_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193163_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193163_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193165_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193165_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193168_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193168_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193169_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193169_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193175_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193175_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193176_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193176_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193181_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193181_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193186_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193186_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (38.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193189_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193189_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193190_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193190_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193192_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193192_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193197_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193197_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193199_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193199_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193200_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193200_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193202_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193202_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193211_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193211_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193215_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193215_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193224_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193224_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193233_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193233_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (8.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193240_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193240_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193244_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193244_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193249_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193249_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193253_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193253_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193255_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193255_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193260_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193260_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193262_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193262_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193266_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193266_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (35.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193268_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193268_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193269_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193269_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193270_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193270_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193272_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193272_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193274_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193274_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193283_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193283_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193284_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193284_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193285_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193285_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193289_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193289_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193290_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193290_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193291_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193291_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193296_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193296_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193297_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193297_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193300_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193300_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193301_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193301_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193304_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193304_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193306_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193306_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193309_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193309_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193319_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193319_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193321_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193321_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193329_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193329_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193332_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193332_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193336_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193336_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193340_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193340_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193342_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193342_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193343_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193343_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193354_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193354_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193357_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193357_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193358_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193358_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193371_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193371_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193385_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193385_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (34.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193386_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193386_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193397_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193397_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193398_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193398_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193403_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193403_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193409_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193409_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193419_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193419_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193421_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193421_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193443_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193443_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193450_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193450_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193455_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193455_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193460_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193460_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193482_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193482_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193495_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193495_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193503_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193503_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193513_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193513_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193519_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193519_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193523_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193523_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193527_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193527_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193531_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193531_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193546_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193546_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193571_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193571_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193573_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193573_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193575_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193575_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193607_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193607_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193618_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193618_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193650_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193650_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193676_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193676_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193678_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193678_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193687_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193687_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193696_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193696_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193718_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193718_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193737_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193737_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193744_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193744_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193820_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193820_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193838_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193838_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193859_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193859_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193877_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193877_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193879_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193879_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193932_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 193932_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193933_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193933_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193975_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 193975_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194002_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 194002_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194029_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 194029_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194035_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 194035_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194166_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 194166_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 87727_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
Preparing report for the candidate 87727_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 139426_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 139426_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 23:11:50.86 +56:02:41.5 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140320_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 140320_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
**** FOUND 23:44:32.22 +56:34:51.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 134452_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 134452_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186502_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 186502_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.1 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35911_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 35911_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75760_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 75760_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 14767_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075
The candidate 14767_fd_Cas-04-Q2b1x1_2026-07-13_01-54-25_20.00sec_4.90C_LIGHT_0075 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 37s
make_report_in_HTML.sh TOTAL: 695s
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 ####
00:09:30.37 +51:35:57.4
23:11:50.83 +56:02:36.8
00:02:20.47 +54:07:58.1
23:34:47.85 +54:35:22.1
23:19:08.06 +55:29:03.6
00:04:26.60 +58:12:16.8
23:36:22.71 +56:42:22.7
23:14:00.20 +53:48:48.2
00:00:21.12 +54:41:00.8
23:21:55.10 +52:18:41.4
00:09:02.89 +54:34:36.0
00:14:03.80 +54:34:33.6
00:00:38.27 +54:12:08.1
00:05:47.78 +55:40:34.2
00:05:30.68 +57:48:28.6
00:27:51.39 +55:18:50.6
00:26:53.60 +56:55:17.2
00:00:24.29 +51:44:10.1
00:22:53.92 +57:35:32.3
00:29:01.78 +57:02:14.0
00:22:47.82 +52:41:21.7
23:58:32.99 +58:03:58.5
23:55:08.32 +52:30:39.7
23:53:12.90 +54:00:38.0
00:31:21.39 +57:06:30.6
23:18:54.84 +53:01:44.0
00:31:05.01 +55:56:06.4
00:26:37.65 +56:47:25.0
00:17:32.43 +54:36:14.8
00:23:32.01 +57:49:18.3
00:22:07.15 +57:36:53.0
23:28:43.23 +54:29:16.1
00:10:31.02 +57:26:23.1
00:31:51.93 +56:59:39.7
23:31:07.69 +53:45:00.8
00:29:46.24 +58:00:57.8
00:15:00.86 +57:44:49.1
23:28:10.65 +54:38:43.2
00:11:07.27 +54:58:20.4
00:01:12.90 +55:16:19.1
00:30:00.15 +57:34:39.1
00:01:49.79 +55:38:01.1
00:26:08.70 +57:20:45.6
23:38:26.34 +53:46:04.4
00:15:59.17 +54:40:40.7
23:19:46.40 +53:15:48.8
23:29:01.15 +52:35:57.0
23:29:58.28 +51:51:22.8
23:22:20.89 +51:22:45.3
23:43:39.45 +56:10:00.2
00:32:20.47 +57:15:05.4
00:13:17.61 +57:35:53.8
23:57:52.76 +56:48:31.4
23:40:14.57 +54:54:05.9
23:24:52.43 +55:56:49.5
23:18:42.24 +52:03:01.6
00:17:55.23 +57:40:47.7
00:00:33.12 +54:57:57.6
23:13:21.74 +54:10:57.7
00:28:37.18 +57:13:22.8
23:57:47.23 +56:40:16.1
23:17:00.57 +56:24:22.1
00:25:01.23 +55:19:57.3
23:59:05.82 +55:40:58.7
00:07:17.80 +57:21:38.6
00:31:12.47 +56:36:38.7
23:16:36.08 +54:03:16.7
00:18:42.96 +50:07:26.8
23:22:13.30 +55:55:53.3
23:27:47.58 +56:18:34.6
00:19:51.83 +49:58:27.3
23:59:26.09 +55:57:58.4
00:22:59.37 +53:53:10.7
23:41:14.51 +55:32:48.9
00:30:24.02 +55:49:16.9
23:57:46.95 +52:11:14.0
00:20:13.54 +55:23:41.2
00:28:42.64 +57:00:57.4
00:25:19.81 +55:26:56.1
23:43:09.70 +50:24:26.4
00:13:40.53 +56:53:50.2
00:19:32.95 +57:40:58.1
00:20:18.00 +57:39:19.3
23:21:38.41 +50:06:37.2
00:28:41.43 +55:35:45.4
00:27:44.84 +55:38:34.8
00:31:00.14 +57:25:07.7
00:05:56.66 +51:24:26.8
00:07:19.85 +51:17:57.1
00:14:08.80 +54:04:46.8
23:14:00.84 +55:30:36.4
00:27:02.78 +57:52:22.5
00:31:11.33 +55:35:46.7
00:31:08.55 +57:02:02.2
00:31:11.23 +56:01:48.7
23:43:23.05 +50:04:13.0
00:31:10.04 +56:38:40.8
00:10:47.84 +54:41:56.4
00:24:28.87 +56:46:03.4
00:22:11.90 +49:50:42.0
00:26:24.15 +57:51:06.7
00:01:21.57 +54:49:13.8
00:22:24.57 +50:05:47.1
00:21:21.30 +50:04:52.2
00:30:18.57 +56:07:46.1
23:56:13.05 +54:27:18.9
00:11:07.93 +57:36:57.4
00:25:49.93 +56:00:40.2
00:30:20.44 +57:32:49.5
00:30:26.55 +55:57:32.5
00:22:10.00 +57:53:34.2
00:25:17.32 +58:06:43.0
00:27:47.19 +57:46:49.8
23:19:09.41 +52:18:41.8
23:45:22.71 +56:43:53.7
00:03:27.43 +54:25:00.7
00:13:38.45 +54:57:36.0
00:21:55.69 +50:04:57.1
00:30:02.64 +57:31:38.9
00:28:04.93 +57:36:07.0
23:20:10.87 +49:26:39.0
00:28:55.36 +57:14:42.8
00:32:09.71 +56:46:40.1
23:18:53.75 +49:32:00.5
23:23:39.19 +49:26:39.7
00:25:19.31 +57:25:11.4
00:27:10.06 +57:15:39.2
00:12:53.30 +57:15:11.9
00:22:17.80 +50:07:39.9
00:28:59.81 +56:53:49.0
00:24:14.22 +57:44:20.9
23:50:04.62 +56:30:38.1
00:31:56.22 +56:45:35.0
23:39:20.01 +50:37:51.9
00:17:13.35 +57:50:24.7
00:20:35.06 +49:54:17.7
00:32:22.39 +57:15:20.6
00:21:13.55 +49:53:59.8
00:32:12.23 +57:44:52.6
23:54:56.15 +56:31:20.2
00:15:47.33 +49:47:37.5
00:28:22.45 +55:50:25.0
00:31:59.24 +56:28:35.2
00:28:05.69 +55:16:33.2
00:29:41.61 +55:45:18.2
00:21:15.31 +50:08:09.5
00:06:08.52 +57:18:46.3
00:28:52.08 +55:13:09.8
00:25:45.26 +57:53:59.7
23:41:05.62 +55:10:27.1
00:25:26.17 +55:26:22.6
00:18:22.84 +58:14:37.4
00:03:35.83 +54:50:49.9
00:30:32.75 +57:57:03.5
00:28:45.07 +55:16:11.1
00:30:33.32 +55:55:11.0
00:15:12.38 +57:40:46.9
00:14:44.14 +51:17:38.0
00:30:33.32 +56:42:28.5
00:16:26.35 +57:19:36.6
00:22:29.90 +53:32:20.2
00:21:32.33 +50:03:51.2
00:32:02.72 +57:43:28.3
00:15:38.11 +50:00:41.8
00:05:21.25 +57:19:54.3
00:32:45.43 +57:53:35.0
00:14:09.48 +57:57:45.3
23:10:24.22 +56:05:45.2
00:29:55.35 +56:47:04.5
23:59:07.59 +54:15:14.3
23:56:47.04 +56:56:43.7
00:18:35.84 +55:14:04.4
00:30:44.47 +57:01:09.8
23:55:56.02 +56:02:00.6
00:24:54.75 +57:42:12.7
00:16:50.24 +57:27:20.1
23:23:00.23 +49:26:18.5
00:17:18.59 +57:02:32.6
00:25:11.31 +57:49:40.2
00:26:30.98 +57:24:48.4
23:15:09.54 +54:02:34.3
23:28:20.04 +54:25:58.1
00:26:14.97 +55:30:01.5
00:26:53.02 +57:56:54.5
00:12:50.82 +56:38:48.9
00:32:59.93 +58:00:39.4
00:12:02.99 +54:10:31.6
23:44:56.35 +55:59:43.5
00:30:30.82 +55:12:25.4
00:11:28.05 +57:42:56.6
00:32:13.19 +56:54:47.6
00:30:33.85 +57:25:25.8
00:03:09.19 +54:08:20.2
00:28:23.34 +57:29:17.3
00:30:45.49 +57:52:17.3
00:28:50.08 +55:17:34.8
00:24:17.66 +58:04:19.1
00:03:31.55 +54:11:52.4
00:10:57.35 +57:27:23.7
23:54:19.31 +58:16:05.0
23:30:10.47 +55:15:36.5
00:03:49.14 +57:30:53.4
00:32:11.71 +57:56:04.3
00:28:11.01 +56:33:57.5
00:28:23.84 +56:43:03.0
00:31:19.40 +58:00:05.0
00:32:14.25 +58:03:27.9
00:26:06.73 +56:48:59.2
23:31:53.26 +53:31:50.7
23:18:20.75 +53:43:58.6
00:08:00.46 +54:42:27.5
23:24:01.31 +54:17:19.4
23:22:05.00 +53:41:32.2
00:10:32.74 +56:27:15.1
00:25:34.97 +58:03:22.1
00:04:33.76 +55:40:27.1
23:29:53.81 +51:18:40.8
00:18:10.98 +58:04:54.5
00:09:52.05 +57:38:56.6
23:20:55.75 +49:40:47.1
00:08:36.81 +56:47:35.8
00:09:45.88 +57:34:08.0
23:33:01.14 +54:05:03.0
23:26:48.98 +50:31:18.7
00:01:36.47 +56:39:02.0
23:55:07.55 +57:18:21.1
23:18:49.44 +52:54:36.8
23:57:42.81 +56:07:21.5
23:22:14.91 +54:54:43.9
23:41:30.57 +54:11:00.8
23:18:57.52 +50:32:10.2
23:45:24.27 +54:41:14.8
23:26:15.13 +50:32:28.6
23:23:06.62 +51:44:21.7
23:14:28.99 +56:13:52.5
23:23:09.93 +54:20:50.5
23:35:20.92 +56:14:00.8
23:21:19.26 +52:54:32.6
23:29:09.54 +54:20:30.1
########### Completed Cas-04-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
23:11:50.83 +56:02:36.8
00:02:20.47 +54:07:58.1
23:34:47.85 +54:35:22.1
00:09:30.37 +51:35:57.4
23:19:08.06 +55:29:03.6
00:04:26.60 +58:12:16.8
23:36:22.71 +56:42:22.7
23:14:00.20 +53:48:48.2
00:00:21.12 +54:41:00.8
23:21:55.10 +52:18:41.4
00:09:02.89 +54:34:36.0
00:14:03.80 +54:34:33.6
00:00:38.27 +54:12:08.1
00:05:47.78 +55:40:34.2
00:05:30.68 +57:48:28.6
00:27:51.39 +55:18:50.6
00:26:53.60 +56:55:17.2
00:00:24.29 +51:44:10.1
00:22:53.92 +57:35:32.3
00:29:01.78 +57:02:14.0
00:22:47.82 +52:41:21.7
23:58:32.99 +58:03:58.5
23:55:08.32 +52:30:39.7
23:53:12.90 +54:00:38.0
00:31:21.39 +57:06:30.6
23:18:54.84 +53:01:44.0
00:31:05.01 +55:56:06.4
00:26:37.65 +56:47:25.0
00:17:32.43 +54:36:14.8
00:23:32.01 +57:49:18.3
00:22:07.15 +57:36:53.0
23:28:43.23 +54:29:16.1
00:10:31.02 +57:26:23.1
00:31:51.93 +56:59:39.7
23:31:07.69 +53:45:00.8
00:29:46.24 +58:00:57.8
00:15:00.86 +57:44:49.1
23:28:10.65 +54:38:43.2
00:11:07.27 +54:58:20.4
00:01:12.90 +55:16:19.1
00:30:00.15 +57:34:39.1
00:01:49.79 +55:38:01.1
00:26:08.70 +57:20:45.6
23:38:26.34 +53:46:04.4
00:15:59.17 +54:40:40.7
23:19:46.40 +53:15:48.8
23:29:01.15 +52:35:57.0
23:29:58.28 +51:51:22.8
23:22:20.89 +51:22:45.3
23:43:39.45 +56:10:00.2
00:32:20.47 +57:15:05.4
00:13:17.61 +57:35:53.8
23:57:52.76 +56:48:31.4
23:40:14.57 +54:54:05.9
23:24:52.43 +55:56:49.5
23:18:42.24 +52:03:01.6
00:17:55.23 +57:40:47.7
00:00:33.12 +54:57:57.6
23:13:21.74 +54:10:57.7
00:28:37.18 +57:13:22.8
23:57:47.23 +56:40:16.1
23:17:00.57 +56:24:22.1
00:25:01.23 +55:19:57.3
23:59:05.82 +55:40:58.7
00:07:17.80 +57:21:38.6
00:31:12.47 +56:36:38.7
23:16:36.08 +54:03:16.7
00:18:42.96 +50:07:26.8
23:22:13.30 +55:55:53.3
23:27:47.58 +56:18:34.6
00:19:51.83 +49:58:27.3
23:59:26.09 +55:57:58.4
00:22:59.37 +53:53:10.7
23:41:14.51 +55:32:48.9
00:30:24.02 +55:49:16.9
23:57:46.95 +52:11:14.0
00:20:13.54 +55:23:41.2
00:28:42.64 +57:00:57.4
00:25:19.81 +55:26:56.1
23:43:09.70 +50:24:26.4
00:13:40.53 +56:53:50.2
00:19:32.95 +57:40:58.1
00:20:18.00 +57:39:19.3
23:21:38.41 +50:06:37.2
00:28:41.43 +55:35:45.4
00:27:44.84 +55:38:34.8
00:31:00.14 +57:25:07.7
00:05:56.66 +51:24:26.8
00:07:19.85 +51:17:57.1
00:14:08.80 +54:04:46.8
23:14:00.84 +55:30:36.4
00:27:02.78 +57:52:22.5
00:31:11.33 +55:35:46.7
00:31:08.55 +57:02:02.2
00:31:11.23 +56:01:48.7
23:43:23.05 +50:04:13.0
00:31:10.04 +56:38:40.8
00:10:47.84 +54:41:56.4
00:24:28.87 +56:46:03.4
00:22:11.90 +49:50:42.0
00:26:24.15 +57:51:06.7
00:01:21.57 +54:49:13.8
00:22:24.57 +50:05:47.1
00:21:21.30 +50:04:52.2
00:30:18.57 +56:07:46.1
23:56:13.05 +54:27:18.9
00:11:07.93 +57:36:57.4
00:25:49.93 +56:00:40.2
00:30:20.44 +57:32:49.5
00:30:26.55 +55:57:32.5
00:22:10.00 +57:53:34.2
00:25:17.32 +58:06:43.0
00:27:47.19 +57:46:49.8
23:19:09.41 +52:18:41.8
23:45:22.71 +56:43:53.7
00:03:27.43 +54:25:00.7
00:13:38.45 +54:57:36.0
00:21:55.69 +50:04:57.1
00:30:02.64 +57:31:38.9
00:28:04.93 +57:36:07.0
23:20:10.87 +49:26:39.0
00:28:55.36 +57:14:42.8
00:32:09.71 +56:46:40.1
23:18:53.75 +49:32:00.5
23:23:39.19 +49:26:39.7
00:25:19.31 +57:25:11.4
00:27:10.06 +57:15:39.2
00:12:53.30 +57:15:11.9
00:22:17.80 +50:07:39.9
00:28:59.81 +56:53:49.0
00:24:14.22 +57:44:20.9
23:50:04.62 +56:30:38.1
00:31:56.22 +56:45:35.0
23:39:20.01 +50:37:51.9
00:17:13.35 +57:50:24.7
00:20:35.06 +49:54:17.7
00:32:22.39 +57:15:20.6
00:21:13.55 +49:53:59.8
00:32:12.23 +57:44:52.6
23:54:56.15 +56:31:20.2
00:15:47.33 +49:47:37.5
00:28:22.45 +55:50:25.0
00:31:59.24 +56:28:35.2
00:28:05.69 +55:16:33.2
00:29:41.61 +55:45:18.2
00:21:15.31 +50:08:09.5
00:06:08.52 +57:18:46.3
00:28:52.08 +55:13:09.8
00:25:45.26 +57:53:59.7
23:41:05.62 +55:10:27.1
00:25:26.17 +55:26:22.6
00:18:22.84 +58:14:37.4
00:03:35.83 +54:50:49.9
00:30:32.75 +57:57:03.5
00:28:45.07 +55:16:11.1
00:30:33.32 +55:55:11.0
00:15:12.38 +57:40:46.9
00:14:44.14 +51:17:38.0
00:30:33.32 +56:42:28.5
00:16:26.35 +57:19:36.6
00:22:29.90 +53:32:20.2
00:21:32.33 +50:03:51.2
00:32:02.72 +57:43:28.3
00:15:38.11 +50:00:41.8
00:05:21.25 +57:19:54.3
00:32:45.43 +57:53:35.0
00:14:09.48 +57:57:45.3
23:10:24.22 +56:05:45.2
00:29:55.35 +56:47:04.5
23:59:07.59 +54:15:14.3
23:56:47.04 +56:56:43.7
00:18:35.84 +55:14:04.4
00:30:44.47 +57:01:09.8
23:55:56.02 +56:02:00.6
00:24:54.75 +57:42:12.7
00:16:50.24 +57:27:20.1
23:23:00.23 +49:26:18.5
00:17:18.59 +57:02:32.6
00:25:11.31 +57:49:40.2
00:26:30.98 +57:24:48.4
23:15:09.54 +54:02:34.3
23:28:20.04 +54:25:58.1
00:26:14.97 +55:30:01.5
00:26:53.02 +57:56:54.5
00:12:50.82 +56:38:48.9
00:32:59.93 +58:00:39.4
00:12:02.99 +54:10:31.6
23:44:56.35 +55:59:43.5
00:30:30.82 +55:12:25.4
00:11:28.05 +57:42:56.6
00:32:13.19 +56:54:47.6
00:30:33.85 +57:25:25.8
00:03:09.19 +54:08:20.2
00:28:23.34 +57:29:17.3
00:30:45.49 +57:52:17.3
00:28:50.08 +55:17:34.8
00:24:17.66 +58:04:19.1
00:03:31.55 +54:11:52.4
00:10:57.35 +57:27:23.7
23:54:19.31 +58:16:05.0
23:30:10.47 +55:15:36.5
00:03:49.14 +57:30:53.4
00:32:11.71 +57:56:04.3
00:28:11.01 +56:33:57.5
00:28:23.84 +56:43:03.0
00:31:19.40 +58:00:05.0
00:32:14.25 +58:03:27.9
00:26:06.73 +56:48:59.2
23:31:53.26 +53:31:50.7
23:18:20.75 +53:43:58.6
00:08:00.46 +54:42:27.5
23:24:01.31 +54:17:19.4
23:22:05.00 +53:41:32.2
00:10:32.74 +56:27:15.1
00:25:34.97 +58:03:22.1
00:04:33.76 +55:40:27.1
23:29:53.81 +51:18:40.8
00:18:10.98 +58:04:54.5
00:09:52.05 +57:38:56.6
23:20:55.75 +49:40:47.1
00:08:36.81 +56:47:35.8
00:09:45.88 +57:34:08.0
23:33:01.14 +54:05:03.0
23:26:48.98 +50:31:18.7
00:01:36.47 +56:39:02.0
23:55:07.55 +57:18:21.1
23:18:49.44 +52:54:36.8
23:57:42.81 +56:07:21.5
23:22:14.91 +54:54:43.9
23:41:30.57 +54:11:00.8
23:18:57.52 +50:32:10.2
23:45:24.27 +54:41:14.8
23:26:15.13 +50:32:28.6
23:23:06.62 +51:44:21.7
23:14:28.99 +56:13:52.5
23:23:09.93 +54:20:50.5
23:35:20.92 +56:14:00.8
23:21:19.26 +52:54:32.6
23:29:09.54 +54:20:30.1
###################################################################################
23:11:50.83 +56:02:36.8 -- not an asteroid (will add it to exclusion list)
00:02:20.47 +54:07:58.1 -- not an asteroid (will add it to exclusion list)
23:34:47.85 +54:35:22.1 -- not an asteroid (will add it to exclusion list)
00:09:30.37 +51:35:57.4 -- not an asteroid (will add it to exclusion list)
23:19:08.06 +55:29:03.6 -- not an asteroid (will add it to exclusion list)
00:04:26.60 +58:12:16.8 -- not an asteroid (will add it to exclusion list)
23:36:22.71 +56:42:22.7 -- not an asteroid (will add it to exclusion list)
23:14:00.20 +53:48:48.2 -- not an asteroid (will add it to exclusion list)
00:00:21.12 +54:41:00.8 -- not an asteroid (will add it to exclusion list)
23:21:55.10 +52:18:41.4 -- not an asteroid (will add it to exclusion list)
00:09:02.89 +54:34:36.0 -- not an asteroid (will add it to exclusion list)
00:14:03.80 +54:34:33.6 -- not an asteroid (will add it to exclusion list)
00:00:38.27 +54:12:08.1 -- not an asteroid (will add it to exclusion list)
00:05:47.78 +55:40:34.2 -- not an asteroid (will add it to exclusion list)
00:05:30.68 +57:48:28.6 -- not an asteroid (will add it to exclusion list)
00:27:51.39 +55:18:50.6 -- not an asteroid (will add it to exclusion list)
00:26:53.60 +56:55:17.2 -- not an asteroid (will add it to exclusion list)
00:00:24.29 +51:44:10.1 -- not an asteroid (will add it to exclusion list)
00:22:53.92 +57:35:32.3 -- not an asteroid (will add it to exclusion list)
00:29:01.78 +57:02:14.0 -- not an asteroid (will add it to exclusion list)
00:22:47.82 +52:41:21.7 -- not an asteroid (will add it to exclusion list)
23:58:32.99 +58:03:58.5 -- not an asteroid (will add it to exclusion list)
23:55:08.32 +52:30:39.7 -- not an asteroid (will add it to exclusion list)
23:53:12.90 +54:00:38.0 -- not an asteroid (will add it to exclusion list)
00:31:21.39 +57:06:30.6 -- not an asteroid (will add it to exclusion list)
23:18:54.84 +53:01:44.0 -- not an asteroid (will add it to exclusion list)
00:31:05.01 +55:56:06.4 -- not an asteroid (will add it to exclusion list)
00:26:37.65 +56:47:25.0 -- not an asteroid (will add it to exclusion list)
00:17:32.43 +54:36:14.8 -- not an asteroid (will add it to exclusion list)
00:23:32.01 +57:49:18.3 -- not an asteroid (will add it to exclusion list)
00:22:07.15 +57:36:53.0 -- not an asteroid (will add it to exclusion list)
23:28:43.23 +54:29:16.1 -- not an asteroid (will add it to exclusion list)
00:10:31.02 +57:26:23.1 -- not an asteroid (will add it to exclusion list)
00:31:51.93 +56:59:39.7 -- not an asteroid (will add it to exclusion list)
23:31:07.69 +53:45:00.8 -- not an asteroid (will add it to exclusion list)
00:29:46.24 +58:00:57.8 -- not an asteroid (will add it to exclusion list)
00:15:00.86 +57:44:49.1 -- not an asteroid (will add it to exclusion list)
23:28:10.65 +54:38:43.2 -- not an asteroid (will add it to exclusion list)
00:11:07.27 +54:58:20.4 -- not an asteroid (will add it to exclusion list)
00:01:12.90 +55:16:19.1 -- not an asteroid (will add it to exclusion list)
00:30:00.15 +57:34:39.1 -- not an asteroid (will add it to exclusion list)
00:01:49.79 +55:38:01.1 -- not an asteroid (will add it to exclusion list)
00:26:08.70 +57:20:45.6 -- not an asteroid (will add it to exclusion list)
23:38:26.34 +53:46:04.4 -- not an asteroid (will add it to exclusion list)
00:15:59.17 +54:40:40.7 -- not an asteroid (will add it to exclusion list)
23:19:46.40 +53:15:48.8 -- not an asteroid (will add it to exclusion list)
23:29:01.15 +52:35:57.0 -- not an asteroid (will add it to exclusion list)
23:29:58.28 +51:51:22.8 -- not an asteroid (will add it to exclusion list)
23:22:20.89 +51:22:45.3 -- not an asteroid (will add it to exclusion list)
23:43:39.45 +56:10:00.2 -- not an asteroid (will add it to exclusion list)
00:32:20.47 +57:15:05.4 -- not an asteroid (will add it to exclusion list)
00:13:17.61 +57:35:53.8 -- not an asteroid (will add it to exclusion list)
23:57:52.76 +56:48:31.4 -- not an asteroid (will add it to exclusion list)
23:40:14.57 +54:54:05.9 -- not an asteroid (will add it to exclusion list)
23:24:52.43 +55:56:49.5 -- not an asteroid (will add it to exclusion list)
23:18:42.24 +52:03:01.6 -- not an asteroid (will add it to exclusion list)
00:17:55.23 +57:40:47.7 -- not an asteroid (will add it to exclusion list)
00:00:33.12 +54:57:57.6 -- not an asteroid (will add it to exclusion list)
23:13:21.74 +54:10:57.7 -- not an asteroid (will add it to exclusion list)
00:28:37.18 +57:13:22.8 -- not an asteroid (will add it to exclusion list)
23:57:47.23 +56:40:16.1 -- not an asteroid (will add it to exclusion list)
23:17:00.57 +56:24:22.1 -- not an asteroid (will add it to exclusion list)
00:25:01.23 +55:19:57.3 -- not an asteroid (will add it to exclusion list)
23:59:05.82 +55:40:58.7 -- not an asteroid (will add it to exclusion list)
00:07:17.80 +57:21:38.6 -- not an asteroid (will add it to exclusion list)
00:31:12.47 +56:36:38.7 -- not an asteroid (will add it to exclusion list)
23:16:36.08 +54:03:16.7 -- not an asteroid (will add it to exclusion list)
00:18:42.96 +50:07:26.8 -- not an asteroid (will add it to exclusion list)
23:22:13.30 +55:55:53.3 -- not an asteroid (will add it to exclusion list)
23:27:47.58 +56:18:34.6 -- not an asteroid (will add it to exclusion list)
00:19:51.83 +49:58:27.3 -- not an asteroid (will add it to exclusion list)
23:59:26.09 +55:57:58.4 -- not an asteroid (will add it to exclusion list)
00:22:59.37 +53:53:10.7 -- not an asteroid (will add it to exclusion list)
23:41:14.51 +55:32:48.9 -- not an asteroid (will add it to exclusion list)
00:30:24.02 +55:49:16.9 -- not an asteroid (will add it to exclusion list)
23:57:46.95 +52:11:14.0 -- not an asteroid (will add it to exclusion list)
00:20:13.54 +55:23:41.2 -- not an asteroid (will add it to exclusion list)
00:28:42.64 +57:00:57.4 -- not an asteroid (will add it to exclusion list)
00:25:19.81 +55:26:56.1 -- not an asteroid (will add it to exclusion list)
23:43:09.70 +50:24:26.4 -- not an asteroid (will add it to exclusion list)
00:13:40.53 +56:53:50.2 -- not an asteroid (will add it to exclusion list)
00:19:32.95 +57:40:58.1 -- not an asteroid (will add it to exclusion list)
00:20:18.00 +57:39:19.3 -- not an asteroid (will add it to exclusion list)
23:21:38.41 +50:06:37.2 -- not an asteroid (will add it to exclusion list)
00:28:41.43 +55:35:45.4 -- not an asteroid (will add it to exclusion list)
00:27:44.84 +55:38:34.8 -- not an asteroid (will add it to exclusion list)
00:31:00.14 +57:25:07.7 -- not an asteroid (will add it to exclusion list)
00:05:56.66 +51:24:26.8 -- not an asteroid (will add it to exclusion list)
00:07:19.85 +51:17:57.1 -- not an asteroid (will add it to exclusion list)
00:14:08.80 +54:04:46.8 -- not an asteroid (will add it to exclusion list)
23:14:00.84 +55:30:36.4 -- not an asteroid (will add it to exclusion list)
00:27:02.78 +57:52:22.5 -- not an asteroid (will add it to exclusion list)
00:31:11.33 +55:35:46.7 -- not an asteroid (will add it to exclusion list)
00:31:08.55 +57:02:02.2 -- not an asteroid (will add it to exclusion list)
00:31:11.23 +56:01:48.7 -- not an asteroid (will add it to exclusion list)
23:43:23.05 +50:04:13.0 -- not an asteroid (will add it to exclusion list)
00:31:10.04 +56:38:40.8 -- not an asteroid (will add it to exclusion list)
00:10:47.84 +54:41:56.4 -- not an asteroid (will add it to exclusion list)
00:24:28.87 +56:46:03.4 -- not an asteroid (will add it to exclusion list)
00:22:11.90 +49:50:42.0 -- not an asteroid (will add it to exclusion list)
00:26:24.15 +57:51:06.7 -- not an asteroid (will add it to exclusion list)
00:01:21.57 +54:49:13.8 -- not an asteroid (will add it to exclusion list)
00:22:24.57 +50:05:47.1 -- not an asteroid (will add it to exclusion list)
00:21:21.30 +50:04:52.2 -- not an asteroid (will add it to exclusion list)
00:30:18.57 +56:07:46.1 -- not an asteroid (will add it to exclusion list)
23:56:13.05 +54:27:18.9 -- not an asteroid (will add it to exclusion list)
00:11:07.93 +57:36:57.4 -- not an asteroid (will add it to exclusion list)
00:25:49.93 +56:00:40.2 -- not an asteroid (will add it to exclusion list)
00:30:20.44 +57:32:49.5 -- not an asteroid (will add it to exclusion list)
00:30:26.55 +55:57:32.5 -- not an asteroid (will add it to exclusion list)
00:22:10.00 +57:53:34.2 -- not an asteroid (will add it to exclusion list)
00:25:17.32 +58:06:43.0 -- not an asteroid (will add it to exclusion list)
00:27:47.19 +57:46:49.8 -- not an asteroid (will add it to exclusion list)
23:19:09.41 +52:18:41.8 -- not an asteroid (will add it to exclusion list)
23:45:22.71 +56:43:53.7 -- not an asteroid (will add it to exclusion list)
00:03:27.43 +54:25:00.7 -- not an asteroid (will add it to exclusion list)
00:13:38.45 +54:57:36.0 -- not an asteroid (will add it to exclusion list)
00:21:55.69 +50:04:57.1 -- not an asteroid (will add it to exclusion list)
00:30:02.64 +57:31:38.9 -- not an asteroid (will add it to exclusion list)
00:28:04.93 +57:36:07.0 -- not an asteroid (will add it to exclusion list)
23:20:10.87 +49:26:39.0 -- not an asteroid (will add it to exclusion list)
00:28:55.36 +57:14:42.8 -- not an asteroid (will add it to exclusion list)
00:32:09.71 +56:46:40.1 -- not an asteroid (will add it to exclusion list)
23:18:53.75 +49:32:00.5 -- not an asteroid (will add it to exclusion list)
23:23:39.19 +49:26:39.7 -- not an asteroid (will add it to exclusion list)
00:25:19.31 +57:25:11.4 -- not an asteroid (will add it to exclusion list)
00:27:10.06 +57:15:39.2 -- not an asteroid (will add it to exclusion list)
00:12:53.30 +57:15:11.9 -- not an asteroid (will add it to exclusion list)
00:22:17.80 +50:07:39.9 -- not an asteroid (will add it to exclusion list)
00:28:59.81 +56:53:49.0 -- not an asteroid (will add it to exclusion list)
00:24:14.22 +57:44:20.9 -- not an asteroid (will add it to exclusion list)
23:50:04.62 +56:30:38.1 -- not an asteroid (will add it to exclusion list)
00:31:56.22 +56:45:35.0 -- not an asteroid (will add it to exclusion list)
23:39:20.01 +50:37:51.9 -- not an asteroid (will add it to exclusion list)
00:17:13.35 +57:50:24.7 -- not an asteroid (will add it to exclusion list)
00:20:35.06 +49:54:17.7 -- not an asteroid (will add it to exclusion list)
00:32:22.39 +57:15:20.6 -- not an asteroid (will add it to exclusion list)
00:21:13.55 +49:53:59.8 -- not an asteroid (will add it to exclusion list)
00:32:12.23 +57:44:52.6 -- not an asteroid (will add it to exclusion list)
23:54:56.15 +56:31:20.2 -- not an asteroid (will add it to exclusion list)
00:15:47.33 +49:47:37.5 -- not an asteroid (will add it to exclusion list)
00:28:22.45 +55:50:25.0 -- not an asteroid (will add it to exclusion list)
00:31:59.24 +56:28:35.2 -- not an asteroid (will add it to exclusion list)
00:28:05.69 +55:16:33.2 -- not an asteroid (will add it to exclusion list)
00:29:41.61 +55:45:18.2 -- not an asteroid (will add it to exclusion list)
00:21:15.31 +50:08:09.5 -- not an asteroid (will add it to exclusion list)
00:06:08.52 +57:18:46.3 -- not an asteroid (will add it to exclusion list)
00:28:52.08 +55:13:09.8 -- not an asteroid (will add it to exclusion list)
00:25:45.26 +57:53:59.7 -- not an asteroid (will add it to exclusion list)
23:41:05.62 +55:10:27.1 -- not an asteroid (will add it to exclusion list)
00:25:26.17 +55:26:22.6 -- not an asteroid (will add it to exclusion list)
00:18:22.84 +58:14:37.4 -- not an asteroid (will add it to exclusion list)
00:03:35.83 +54:50:49.9 -- not an asteroid (will add it to exclusion list)
00:30:32.75 +57:57:03.5 -- not an asteroid (will add it to exclusion list)
00:28:45.07 +55:16:11.1 -- not an asteroid (will add it to exclusion list)
00:30:33.32 +55:55:11.0 -- not an asteroid (will add it to exclusion list)
00:15:12.38 +57:40:46.9 -- not an asteroid (will add it to exclusion list)
00:14:44.14 +51:17:38.0 -- not an asteroid (will add it to exclusion list)
00:30:33.32 +56:42:28.5 -- not an asteroid (will add it to exclusion list)
00:16:26.35 +57:19:36.6 -- not an asteroid (will add it to exclusion list)
00:22:29.90 +53:32:20.2 -- not an asteroid (will add it to exclusion list)
00:21:32.33 +50:03:51.2 -- not an asteroid (will add it to exclusion list)
00:32:02.72 +57:43:28.3 -- not an asteroid (will add it to exclusion list)
00:15:38.11 +50:00:41.8 -- not an asteroid (will add it to exclusion list)
00:05:21.25 +57:19:54.3 -- not an asteroid (will add it to exclusion list)
00:32:45.43 +57:53:35.0 -- not an asteroid (will add it to exclusion list)
00:14:09.48 +57:57:45.3 -- not an asteroid (will add it to exclusion list)
23:10:24.22 +56:05:45.2 -- not an asteroid (will add it to exclusion list)
00:29:55.35 +56:47:04.5 -- not an asteroid (will add it to exclusion list)
23:59:07.59 +54:15:14.3 -- not an asteroid (will add it to exclusion list)
23:56:47.04 +56:56:43.7 -- not an asteroid (will add it to exclusion list)
00:18:35.84 +55:14:04.4 -- not an asteroid (will add it to exclusion list)
00:30:44.47 +57:01:09.8 -- not an asteroid (will add it to exclusion list)
23:55:56.02 +56:02:00.6 -- not an asteroid (will add it to exclusion list)
00:24:54.75 +57:42:12.7 -- not an asteroid (will add it to exclusion list)
00:16:50.24 +57:27:20.1 -- not an asteroid (will add it to exclusion list)
23:23:00.23 +49:26:18.5 -- not an asteroid (will add it to exclusion list)
00:17:18.59 +57:02:32.6 -- not an asteroid (will add it to exclusion list)
00:25:11.31 +57:49:40.2 -- not an asteroid (will add it to exclusion list)
00:26:30.98 +57:24:48.4 -- not an asteroid (will add it to exclusion list)
23:15:09.54 +54:02:34.3 -- not an asteroid (will add it to exclusion list)
23:28:20.04 +54:25:58.1 -- not an asteroid (will add it to exclusion list)
00:26:14.97 +55:30:01.5 -- not an asteroid (will add it to exclusion list)
00:26:53.02 +57:56:54.5 -- not an asteroid (will add it to exclusion list)
00:12:50.82 +56:38:48.9 -- not an asteroid (will add it to exclusion list)
00:32:59.93 +58:00:39.4 -- not an asteroid (will add it to exclusion list)
00:12:02.99 +54:10:31.6 -- not an asteroid (will add it to exclusion list)
23:44:56.35 +55:59:43.5 -- not an asteroid (will add it to exclusion list)
00:30:30.82 +55:12:25.4 -- not an asteroid (will add it to exclusion list)
00:11:28.05 +57:42:56.6 -- not an asteroid (will add it to exclusion list)
00:32:13.19 +56:54:47.6 -- not an asteroid (will add it to exclusion list)
00:30:33.85 +57:25:25.8 -- not an asteroid (will add it to exclusion list)
00:03:09.19 +54:08:20.2 -- not an asteroid (will add it to exclusion list)
00:28:23.34 +57:29:17.3 -- not an asteroid (will add it to exclusion list)
00:30:45.49 +57:52:17.3 -- not an asteroid (will add it to exclusion list)
00:28:50.08 +55:17:34.8 -- not an asteroid (will add it to exclusion list)
00:24:17.66 +58:04:19.1 -- not an asteroid (will add it to exclusion list)
00:03:31.55 +54:11:52.4 -- not an asteroid (will add it to exclusion list)
00:10:57.35 +57:27:23.7 -- not an asteroid (will add it to exclusion list)
23:54:19.31 +58:16:05.0 -- not an asteroid (will add it to exclusion list)
23:30:10.47 +55:15:36.5 -- not an asteroid (will add it to exclusion list)
00:03:49.14 +57:30:53.4 -- not an asteroid (will add it to exclusion list)
00:32:11.71 +57:56:04.3 -- not an asteroid (will add it to exclusion list)
00:28:11.01 +56:33:57.5 -- not an asteroid (will add it to exclusion list)
00:28:23.84 +56:43:03.0 -- not an asteroid (will add it to exclusion list)
00:31:19.40 +58:00:05.0 -- not an asteroid (will add it to exclusion list)
00:32:14.25 +58:03:27.9 -- not an asteroid (will add it to exclusion list)
00:26:06.73 +56:48:59.2 -- not an asteroid (will add it to exclusion list)
23:31:53.26 +53:31:50.7 -- not an asteroid (will add it to exclusion list)
23:18:20.75 +53:43:58.6 -- not an asteroid (will add it to exclusion list)
00:08:00.46 +54:42:27.5 -- not an asteroid (will add it to exclusion list)
23:24:01.31 +54:17:19.4 -- not an asteroid (will add it to exclusion list)
23:22:05.00 +53:41:32.2 -- not an asteroid (will add it to exclusion list)
00:10:32.74 +56:27:15.1 -- not an asteroid (will add it to exclusion list)
00:25:34.97 +58:03:22.1 -- not an asteroid (will add it to exclusion list)
00:04:33.76 +55:40:27.1 -- not an asteroid (will add it to exclusion list)
23:29:53.81 +51:18:40.8 -- not an asteroid (will add it to exclusion list)
00:18:10.98 +58:04:54.5 -- not an asteroid (will add it to exclusion list)
00:09:52.05 +57:38:56.6 -- not an asteroid (will add it to exclusion list)
23:20:55.75 +49:40:47.1 -- not an asteroid (will add it to exclusion list)
00:08:36.81 +56:47:35.8 -- not an asteroid (will add it to exclusion list)
00:09:45.88 +57:34:08.0 -- not an asteroid (will add it to exclusion list)
23:33:01.14 +54:05:03.0 -- not an asteroid (will add it to exclusion list)
23:26:48.98 +50:31:18.7 -- not an asteroid (will add it to exclusion list)
00:01:36.47 +56:39:02.0 -- not an asteroid (will add it to exclusion list)
23:55:07.55 +57:18:21.1 -- not an asteroid (will add it to exclusion list)
23:18:49.44 +52:54:36.8 -- not an asteroid (will add it to exclusion list)
23:57:42.81 +56:07:21.5 -- not an asteroid (will add it to exclusion list)
23:22:14.91 +54:54:43.9 -- not an asteroid (will add it to exclusion list)
23:41:30.57 +54:11:00.8 -- not an asteroid (will add it to exclusion list)
23:18:57.52 +50:32:10.2 -- not an asteroid (will add it to exclusion list)
23:45:24.27 +54:41:14.8 -- not an asteroid (will add it to exclusion list)
23:26:15.13 +50:32:28.6 -- not an asteroid (will add it to exclusion list)
23:23:06.62 +51:44:21.7 -- not an asteroid (will add it to exclusion list)
23:14:28.99 +56:13:52.5 -- not an asteroid (will add it to exclusion list)
23:23:09.93 +54:20:50.5 -- not an asteroid (will add it to exclusion list)
23:35:20.92 +56:14:00.8 -- not an asteroid (will add it to exclusion list)
23:21:19.26 +52:54:32.6 -- not an asteroid (will add it to exclusion list)
23:29:09.54 +54:20:30.1 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:21.12 +54:41:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:24.29 +51:44:10.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:33.12 +54:57:57.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:38.27 +54:12:08.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:12.90 +55:16:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:21.57 +54:49:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:36.47 +56:39:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:49.79 +55:38:01.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:20.47 +54:07:58.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:09.19 +54:08:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:27.43 +54:25:00.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:31.55 +54:11:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:35.83 +54:50:49.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:49.14 +57:30:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:26.60 +58:12:16.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:33.76 +55:40:27.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:21.25 +57:19:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:30.68 +57:48:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:47.78 +55:40:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:56.66 +51:24:26.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:08.52 +57:18:46.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:17.80 +57:21:38.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:19.85 +51:17:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:00.46 +54:42:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:36.81 +56:47:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:02.89 +54:34:36.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:30.37 +51:35:57.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:45.88 +57:34:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:52.05 +57:38:56.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:31.02 +57:26:23.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:32.74 +56:27:15.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:47.84 +54:41:56.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:57.35 +57:27:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:07.27 +54:58:20.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:07.93 +57:36:57.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:28.05 +57:42:56.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:02.99 +54:10:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:50.82 +56:38:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:53.30 +57:15:11.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:17.61 +57:35:53.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:38.45 +54:57:36.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:40.53 +56:53:50.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:03.80 +54:34:33.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:08.80 +54:04:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:09.48 +57:57:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:44.14 +51:17:38.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:00.86 +57:44:49.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:12.38 +57:40:46.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:38.11 +50:00:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:47.33 +49:47:37.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:59.17 +54:40:40.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:26.35 +57:19:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:50.24 +57:27:20.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:13.35 +57:50:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:18.59 +57:02:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:32.43 +54:36:14.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:55.23 +57:40:47.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:10.98 +58:04:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:22.84 +58:14:37.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:35.84 +55:14:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:42.96 +50:07:26.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:32.95 +57:40:58.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:51.83 +49:58:27.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:13.54 +55:23:41.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:18.00 +57:39:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:35.06 +49:54:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:13.55 +49:53:59.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:15.31 +50:08:09.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:21.30 +50:04:52.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:32.33 +50:03:51.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:55.69 +50:04:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:07.15 +57:36:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:10.00 +57:53:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:11.90 +49:50:42.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:17.80 +50:07:39.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:24.57 +50:05:47.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:29.90 +53:32:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:47.82 +52:41:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:53.92 +57:35:32.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:59.37 +53:53:10.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:32.01 +57:49:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:14.22 +57:44:20.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:17.66 +58:04:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:28.87 +56:46:03.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:54.75 +57:42:12.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:01.23 +55:19:57.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:11.31 +57:49:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:17.32 +58:06:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:19.31 +57:25:11.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:19.81 +55:26:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:26.17 +55:26:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:34.97 +58:03:22.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:45.26 +57:53:59.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:49.93 +56:00:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:06.73 +56:48:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:08.70 +57:20:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:14.97 +55:30:01.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:24.15 +57:51:06.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:30.98 +57:24:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:37.65 +56:47:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:53.02 +57:56:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:53.60 +56:55:17.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:02.78 +57:52:22.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:10.06 +57:15:39.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:44.84 +55:38:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:47.19 +57:46:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:51.39 +55:18:50.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:04.93 +57:36:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:05.69 +55:16:33.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:11.01 +56:33:57.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:22.45 +55:50:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:23.34 +57:29:17.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:23.84 +56:43:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:37.18 +57:13:22.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:41.43 +55:35:45.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:42.64 +57:00:57.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:45.07 +55:16:11.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:50.08 +55:17:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:52.08 +55:13:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:55.36 +57:14:42.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:59.81 +56:53:49.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:01.78 +57:02:14.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:41.61 +55:45:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:46.24 +58:00:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:55.35 +56:47:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:00.15 +57:34:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:02.64 +57:31:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:18.57 +56:07:46.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:20.44 +57:32:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:24.02 +55:49:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:26.55 +55:57:32.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:30.82 +55:12:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:32.75 +57:57:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:33.32 +55:55:11.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:33.32 +56:42:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:33.85 +57:25:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:44.47 +57:01:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:45.49 +57:52:17.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:00.14 +57:25:07.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:05.01 +55:56:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:08.55 +57:02:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:10.04 +56:38:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:11.23 +56:01:48.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:11.33 +55:35:46.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:12.47 +56:36:38.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:19.40 +58:00:05.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:21.39 +57:06:30.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:51.93 +56:59:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:56.22 +56:45:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:59.24 +56:28:35.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:02.72 +57:43:28.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:09.71 +56:46:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:11.71 +57:56:04.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:12.23 +57:44:52.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:13.19 +56:54:47.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:14.25 +58:03:27.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:20.47 +57:15:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:22.39 +57:15:20.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:45.43 +57:53:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:59.93 +58:00:39.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:24.22 +56:05:45.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:50.83 +56:02:36.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:21.74 +54:10:57.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:00.20 +53:48:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:00.84 +55:30:36.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:28.99 +56:13:52.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:09.54 +54:02:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:36.08 +54:03:16.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:00.57 +56:24:22.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:20.75 +53:43:58.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:42.24 +52:03:01.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:49.44 +52:54:36.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:53.75 +49:32:00.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:54.84 +53:01:44.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:57.52 +50:32:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:08.06 +55:29:03.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:09.41 +52:18:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:46.40 +53:15:48.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:10.87 +49:26:39.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:55.75 +49:40:47.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:19.26 +52:54:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:38.41 +50:06:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:55.10 +52:18:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:05.00 +53:41:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:13.30 +55:55:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:14.91 +54:54:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:20.89 +51:22:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:00.23 +49:26:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:06.62 +51:44:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:09.93 +54:20:50.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:39.19 +49:26:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:01.31 +54:17:19.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:52.43 +55:56:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:15.13 +50:32:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:48.98 +50:31:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:47.58 +56:18:34.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:10.65 +54:38:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:20.04 +54:25:58.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:43.23 +54:29:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:01.15 +52:35:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:09.54 +54:20:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:53.81 +51:18:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:58.28 +51:51:22.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:10.47 +55:15:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:07.69 +53:45:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:53.26 +53:31:50.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:01.14 +54:05:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:47.85 +54:35:22.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:20.92 +56:14:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:22.71 +56:42:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:26.34 +53:46:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:20.01 +50:37:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:14.57 +54:54:05.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:05.62 +55:10:27.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:14.51 +55:32:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:30.57 +54:11:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:09.70 +50:24:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:23.05 +50:04:13.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:39.45 +56:10:00.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:56.35 +55:59:43.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:22.71 +56:43:53.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:24.27 +54:41:14.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:04.62 +56:30:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:12.90 +54:00:38.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:19.31 +58:16:05.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:56.15 +56:31:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:07.55 +57:18:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:08.32 +52:30:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:56.02 +56:02:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:13.05 +54:27:18.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:47.04 +56:56:43.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:42.81 +56:07:21.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:46.95 +52:11:14.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:47.23 +56:40:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:52.76 +56:48:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:32.99 +58:03:58.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:05.82 +55:40:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:07.59 +54:15:14.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:26.09 +55:57:58.4 -- 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:21.12 +54:41:00.8 -- not a known variable star
00:00:24.29 +51:44:10.1 -- not a known variable star
00:00:33.12 +54:57:57.6 -- not a known variable star
00:00:38.27 +54:12:08.1 -- not a known variable star
00:01:12.90 +55:16:19.1 -- not a known variable star
00:01:21.57 +54:49:13.8 -- not a known variable star
00:01:36.47 +56:39:02.0 -- not a known variable star
00:01:49.79 +55:38:01.1 -- a known variable star
00:02:20.47 +54:07:58.1 -- not a known variable star
00:03:09.19 +54:08:20.2 -- not a known variable star
00:03:27.43 +54:25:00.7 -- not a known variable star
00:03:31.55 +54:11:52.4 -- not a known variable star
00:03:35.83 +54:50:49.9 -- not a known variable star
00:03:49.14 +57:30:53.4 -- not a known variable star
00:04:26.60 +58:12:16.8 -- not a known variable star
00:04:33.76 +55:40:27.1 -- not a known variable star
00:05:21.25 +57:19:54.3 -- a known variable star
00:05:30.68 +57:48:28.6 -- a known variable star
00:05:47.78 +55:40:34.2 -- a known variable star
00:05:56.66 +51:24:26.8 -- not a known variable star
00:06:08.52 +57:18:46.3 -- not a known variable star
00:07:17.80 +57:21:38.6 -- not a known variable star
00:07:19.85 +51:17:57.1 -- not a known variable star
00:08:00.46 +54:42:27.5 -- not a known variable star
00:08:36.81 +56:47:35.8 -- not a known variable star
00:09:02.89 +54:34:36.0 -- not a known variable star
00:09:30.37 +51:35:57.4 -- not a known variable star
00:09:45.88 +57:34:08.0 -- not a known variable star
00:09:52.05 +57:38:56.6 -- not a known variable star
00:10:31.02 +57:26:23.1 -- a known variable star
00:10:32.74 +56:27:15.1 -- not a known variable star
00:10:47.84 +54:41:56.4 -- not a known variable star
00:10:57.35 +57:27:23.7 -- not a known variable star
00:11:07.27 +54:58:20.4 -- not a known variable star
00:11:07.93 +57:36:57.4 -- not a known variable star
00:11:28.05 +57:42:56.6 -- not a known variable star
00:12:02.99 +54:10:31.6 -- not a known variable star
00:12:50.82 +56:38:48.9 -- not a known variable star
00:12:53.30 +57:15:11.9 -- not a known variable star
00:13:17.61 +57:35:53.8 -- not a known variable star
00:13:38.45 +54:57:36.0 -- not a known variable star
00:13:40.53 +56:53:50.2 -- not a known variable star
00:14:03.80 +54:34:33.6 -- not a known variable star
00:14:08.80 +54:04:46.8 -- not a known variable star
00:14:09.48 +57:57:45.3 -- not a known variable star
00:14:44.14 +51:17:38.0 -- not a known variable star
00:15:00.86 +57:44:49.1 -- not a known variable star
00:15:12.38 +57:40:46.9 -- not a known variable star
00:15:38.11 +50:00:41.8 -- not a known variable star
00:15:47.33 +49:47:37.5 -- not a known variable star
00:15:59.17 +54:40:40.7 -- not a known variable star
00:16:26.35 +57:19:36.6 -- not a known variable star
00:16:50.24 +57:27:20.1 -- not a known variable star
00:17:13.35 +57:50:24.7 -- a known variable star
00:17:18.59 +57:02:32.6 -- not a known variable star
00:17:32.43 +54:36:14.8 -- not a known variable star
00:17:55.23 +57:40:47.7 -- not a known variable star
00:18:10.98 +58:04:54.5 -- not a known variable star
00:18:22.84 +58:14:37.4 -- not a known variable star
00:18:35.84 +55:14:04.4 -- a known variable star
00:18:42.96 +50:07:26.8 -- not a known variable star
00:19:32.95 +57:40:58.1 -- not a known variable star
00:19:51.83 +49:58:27.3 -- a known variable star
00:20:13.54 +55:23:41.2 -- not a known variable star
00:20:18.00 +57:39:19.3 -- not a known variable star
00:20:35.06 +49:54:17.7 -- not a known variable star
00:21:13.55 +49:53:59.8 -- not a known variable star
00:21:15.31 +50:08:09.5 -- not a known variable star
00:21:21.30 +50:04:52.2 -- not a known variable star
00:21:32.33 +50:03:51.2 -- not a known variable star
00:21:55.69 +50:04:57.1 -- not a known variable star
00:22:07.15 +57:36:53.0 -- not a known variable star
00:22:10.00 +57:53:34.2 -- not a known variable star
00:22:11.90 +49:50:42.0 -- not a known variable star
00:22:17.80 +50:07:39.9 -- not a known variable star
00:22:24.57 +50:05:47.1 -- not a known variable star
00:22:29.90 +53:32:20.2 -- not a known variable star
00:22:47.82 +52:41:21.7 -- not a known variable star
00:22:53.92 +57:35:32.3 -- not a known variable star
00:22:59.37 +53:53:10.7 -- a known variable star
00:23:32.01 +57:49:18.3 -- a known variable star
00:24:14.22 +57:44:20.9 -- not a known variable star
00:24:17.66 +58:04:19.1 -- not a known variable star
00:24:28.87 +56:46:03.4 -- not a known variable star
00:24:54.75 +57:42:12.7 -- not a known variable star
00:25:01.23 +55:19:57.3 -- a known variable star
00:25:11.31 +57:49:40.2 -- not a known variable star
00:25:17.32 +58:06:43.0 -- a known variable star
00:25:19.31 +57:25:11.4 -- not a known variable star
00:25:19.81 +55:26:56.1 -- not a known variable star
00:25:26.17 +55:26:22.6 -- not a known variable star
00:25:34.97 +58:03:22.1 -- a known variable star
00:25:45.26 +57:53:59.7 -- not a known variable star
00:25:49.93 +56:00:40.2 -- not a known variable star
00:26:06.73 +56:48:59.2 -- not a known variable star
00:26:08.70 +57:20:45.6 -- a known variable star
00:26:14.97 +55:30:01.5 -- not a known variable star
00:26:24.15 +57:51:06.7 -- a known variable star
00:26:30.98 +57:24:48.4 -- not a known variable star
00:26:37.65 +56:47:25.0 -- not a known variable star
00:26:53.02 +57:56:54.5 -- not a known variable star
00:26:53.60 +56:55:17.2 -- not a known variable star
00:27:02.78 +57:52:22.5 -- not a known variable star
00:27:10.06 +57:15:39.2 -- a known variable star
00:27:44.84 +55:38:34.8 -- not a known variable star
00:27:47.19 +57:46:49.8 -- not a known variable star
00:27:51.39 +55:18:50.6 -- not a known variable star
00:28:04.93 +57:36:07.0 -- not a known variable star
00:28:05.69 +55:16:33.2 -- not a known variable star
00:28:11.01 +56:33:57.5 -- not a known variable star
00:28:22.45 +55:50:25.0 -- not a known variable star
00:28:23.34 +57:29:17.3 -- not a known variable star
00:28:23.84 +56:43:03.0 -- not a known variable star
00:28:37.18 +57:13:22.8 -- not a known variable star
00:28:41.43 +55:35:45.4 -- not a known variable star
00:28:42.64 +57:00:57.4 -- not a known variable star
00:28:45.07 +55:16:11.1 -- not a known variable star
00:28:50.08 +55:17:34.8 -- not a known variable star
00:28:52.08 +55:13:09.8 -- not a known variable star
00:28:55.36 +57:14:42.8 -- not a known variable star
00:28:59.81 +56:53:49.0 -- not a known variable star
00:29:01.78 +57:02:14.0 -- not a known variable star
00:29:41.61 +55:45:18.2 -- a known variable star
00:29:46.24 +58:00:57.8 -- not a known variable star
00:29:55.35 +56:47:04.5 -- not a known variable star
00:30:00.15 +57:34:39.1 -- not a known variable star
00:30:02.64 +57:31:38.9 -- not a known variable star
00:30:18.57 +56:07:46.1 -- not a known variable star
00:30:20.44 +57:32:49.5 -- not a known variable star
00:30:24.02 +55:49:16.9 -- a known variable star
00:30:26.55 +55:57:32.5 -- not a known variable star
00:30:30.82 +55:12:25.4 -- not a known variable star
00:30:32.75 +57:57:03.5 -- not a known variable star
00:30:33.32 +55:55:11.0 -- not a known variable star
00:30:33.32 +56:42:28.5 -- a known variable star
00:30:33.85 +57:25:25.8 -- not a known variable star
00:30:44.47 +57:01:09.8 -- not a known variable star
00:30:45.49 +57:52:17.3 -- not a known variable star
00:31:00.14 +57:25:07.7 -- a known variable star
00:31:05.01 +55:56:06.4 -- not a known variable star
00:31:08.55 +57:02:02.2 -- not a known variable star
00:31:10.04 +56:38:40.8 -- not a known variable star
00:31:11.23 +56:01:48.7 -- not a known variable star
00:31:11.33 +55:35:46.7 -- not a known variable star
00:31:12.47 +56:36:38.7 -- a known variable star
00:31:19.40 +58:00:05.0 -- not a known variable star
00:31:21.39 +57:06:30.6 -- not a known variable star
00:31:51.93 +56:59:39.7 -- not a known variable star
00:31:56.22 +56:45:35.0 -- a known variable star
00:31:59.24 +56:28:35.2 -- not a known variable star
00:32:02.72 +57:43:28.3 -- not a known variable star
00:32:09.71 +56:46:40.1 -- not a known variable star
00:32:11.71 +57:56:04.3 -- not a known variable star
00:32:12.23 +57:44:52.6 -- not a known variable star
00:32:13.19 +56:54:47.6 -- not a known variable star
00:32:14.25 +58:03:27.9 -- not a known variable star
00:32:20.47 +57:15:05.4 -- not a known variable star
00:32:22.39 +57:15:20.6 -- not a known variable star
00:32:45.43 +57:53:35.0 -- not a known variable star
00:32:59.93 +58:00:39.4 -- not a known variable star
23:10:24.22 +56:05:45.2 -- not a known variable star
23:11:50.83 +56:02:36.8 -- not a known variable star
23:13:21.74 +54:10:57.7 -- not a known variable star
23:14:00.20 +53:48:48.2 -- not a known variable star
23:14:00.84 +55:30:36.4 -- not a known variable star
23:14:28.99 +56:13:52.5 -- not a known variable star
23:15:09.54 +54:02:34.3 -- not a known variable star
23:16:36.08 +54:03:16.7 -- not a known variable star
23:17:00.57 +56:24:22.1 -- not a known variable star
23:18:20.75 +53:43:58.6 -- not a known variable star
23:18:42.24 +52:03:01.6 -- not a known variable star
23:18:49.44 +52:54:36.8 -- not a known variable star
23:18:53.75 +49:32:00.5 -- not a known variable star
23:18:54.84 +53:01:44.0 -- not a known variable star
23:18:57.52 +50:32:10.2 -- not a known variable star
23:19:08.06 +55:29:03.6 -- not a known variable star
23:19:09.41 +52:18:41.8 -- not a known variable star
23:19:46.40 +53:15:48.8 -- not a known variable star
23:20:10.87 +49:26:39.0 -- not a known variable star
23:20:55.75 +49:40:47.1 -- not a known variable star
23:21:19.26 +52:54:32.6 -- not a known variable star
23:21:38.41 +50:06:37.2 -- not a known variable star
23:21:55.10 +52:18:41.4 -- not a known variable star
23:22:05.00 +53:41:32.2 -- not a known variable star
23:22:13.30 +55:55:53.3 -- not a known variable star
23:22:14.91 +54:54:43.9 -- not a known variable star
23:22:20.89 +51:22:45.3 -- not a known variable star
23:23:00.23 +49:26:18.5 -- not a known variable star
23:23:06.62 +51:44:21.7 -- not a known variable star
23:23:09.93 +54:20:50.5 -- not a known variable star
23:23:39.19 +49:26:39.7 -- a known variable star
23:24:01.31 +54:17:19.4 -- not a known variable star
23:24:52.43 +55:56:49.5 -- not a known variable star
23:26:15.13 +50:32:28.6 -- a known variable star
23:26:48.98 +50:31:18.7 -- not a known variable star
23:27:47.58 +56:18:34.6 -- not a known variable star
23:28:10.65 +54:38:43.2 -- not a known variable star
23:28:20.04 +54:25:58.1 -- not a known variable star
23:28:43.23 +54:29:16.1 -- not a known variable star
23:29:01.15 +52:35:57.0 -- not a known variable star
23:29:09.54 +54:20:30.1 -- not a known variable star
23:29:53.81 +51:18:40.8 -- not a known variable star
23:29:58.28 +51:51:22.8 -- not a known variable star
23:30:10.47 +55:15:36.5 -- not a known variable star
23:31:07.69 +53:45:00.8 -- not a known variable star
23:31:53.26 +53:31:50.7 -- not a known variable star
23:33:01.14 +54:05:03.0 -- not a known variable star
23:34:47.85 +54:35:22.1 -- not a known variable star
23:35:20.92 +56:14:00.8 -- not a known variable star
23:36:22.71 +56:42:22.7 -- not a known variable star
23:38:26.34 +53:46:04.4 -- a known variable star
23:39:20.01 +50:37:51.9 -- a known variable star
23:40:14.57 +54:54:05.9 -- not a known variable star
23:41:05.62 +55:10:27.1 -- not a known variable star
23:41:14.51 +55:32:48.9 -- not a known variable star
23:41:30.57 +54:11:00.8 -- not a known variable star
23:43:09.70 +50:24:26.4 -- not a known variable star
23:43:23.05 +50:04:13.0 -- not a known variable star
23:43:39.45 +56:10:00.2 -- not a known variable star
23:44:56.35 +55:59:43.5 -- not a known variable star
23:45:22.71 +56:43:53.7 -- not a known variable star
23:45:24.27 +54:41:14.8 -- not a known variable star
23:50:04.62 +56:30:38.1 -- a known variable star
23:53:12.90 +54:00:38.0 -- not a known variable star
23:54:19.31 +58:16:05.0 -- not a known variable star
23:54:56.15 +56:31:20.2 -- not a known variable star
23:55:07.55 +57:18:21.1 -- a known variable star
23:55:08.32 +52:30:39.7 -- not a known variable star
23:55:56.02 +56:02:00.6 -- not a known variable star
23:56:13.05 +54:27:18.9 -- a known variable star
23:56:47.04 +56:56:43.7 -- not a known variable star
23:57:42.81 +56:07:21.5 -- not a known variable star
23:57:46.95 +52:11:14.0 -- a known variable star
23:57:47.23 +56:40:16.1 -- not a known variable star
23:57:52.76 +56:48:31.4 -- not a known variable star
23:58:32.99 +58:03:58.5 -- not a known variable star
23:59:05.82 +55:40:58.7 -- not a known variable star
23:59:07.59 +54:15:14.3 -- a known variable star
23:59:26.09 +55:57:58.4 -- not a known variable star
Found 208 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
239 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 239 (excluding asteroids and hot pixels, 208 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)2461234.78742690 -observatory V36
07:24:19.82 +17:06:52.3 Mercury (5.6mag)
10:23:51.39 +11:22:46.1 Venus (-4.1mag)
04:32:52.71 +21:46:25.0 Mars (1.3mag)
08:19:20.77 +20:02:59.8 Jupiter (-1.8mag)
00:56:08.73 +03:21:27.3 Saturn (0.7mag)
04:07:47.25 +20:46:32.9 Uranus (5.8mag)
00:17:00.19 +00:20:22.7 Neptune (7.7mag)
20:30:38.64 -23:19:18.2 Pluto (14.4mag)
06:22:20.25 +26:43:57.7 Moon (-8.5mag)
-rw-r--r-- 1 apache apache 361 Jul 13 02:04 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461234.78742690:
08:19:16.33 +20:03:17.7 Io (6.1mag)
08:19:13.94 +20:03:27.0 Europa (6.3mag)
08:19:11.17 +20:03:33.7 Ganymede (5.6mag)
08:19:24.90 +20:02:40.2 Callisto (6.8mag)
08:17:44.24 +19:48:24.6 Himalia (15.7mag)
08:19:25.48 +20:02:42.3 Thebe (16.6mag)
08:17:05.03 +19:52:13.4 Elara (17.6mag)
08:22:58.35 +19:55:35.6 Pasiphae (17.8mag)
08:24:08.52 +20:08:30.4 Carme (19.0mag)
00:56:10.82 +03:20:56.5 Titan (8.5mag)
00:56:11.68 +03:21:33.1 Rhea (9.8mag)
00:55:35.12 +03:20:03.4 Iapetus (11.2mag)
00:56:05.17 +03:21:57.1 Hyperion (14.5mag)
00:56:05.53 +03:18:15.4 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jul 13 02:04 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461234.78742690:
17:50:20.60 -32:21:23.3 JWST
17:01:18.99 +43:50:11.7 Chandra
09:29:16.53 -53:48:23.7 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jul 13 02:04 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461234.78742690 -observatory V36
02:40:25.62 +14:46:30.9 17.9mag P/1996 R2 (Lagerkvist)
18:15:42.50 -34:26:27.1 13.7mag P/2010 H2 (Vales)
06:28:36.72 -68:11:16.3 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
06:01:49.38 +32:29:49.4 17.6mag C/2017 K2 (PANSTARRS)
02:03:58.41 +13:43:15.4 15.5mag P/2021 N1 (ZTF)
22:57:44.85 +32:16:35.3 17.3mag C/2022 E2 (ATLAS)
06:15:44.59 +26:53:58.5 16.7mag C/2022 N2 (PANSTARRS)
09:58:04.66 +29:38:58.0 16.9mag C/2022 QE78 (ATLAS)
09:11:37.99 +05:03:14.6 17.8mag C/2022 R6 (PANSTARRS)
18:05:26.55 +21:10:41.0 18.0mag C/2023 A3 (Tsuchinshan-ATLAS)
15:11:19.01 -11:27:22.5 17.7mag P/2023 B1 (PANSTARRS)
21:45:39.67 +67:35:40.8 17.8mag C/2023 H5 (Lemmon)
16:25:11.12 -10:23:04.9 13.9mag C/2023 R1 (PANSTARRS)
08:05:45.53 +65:52:02.6 17.9mag C/2024 A1 (ATLAS)
07:36:38.99 +30:09:08.0 14.7mag C/2024 E1 (Wierzchos)
15:14:56.20 +15:24:09.2 17.6mag C/2024 G6 (ATLAS)
19:37:33.18 +39:57:19.8 13.8mag C/2024 J3 (ATLAS)
21:44:30.20 +46:26:23.3 17.8mag C/2024 R4 (PANSTARRS)
04:52:24.27 -13:39:55.7 15.7mag C/2024 T5 (ATLAS)
06:36:59.79 +28:34:48.7 18.0mag C/2025 J1 (Borisov)
07:16:22.80 -13:09:11.2 16.6mag C/2025 R3 (PANSTARRS)
09:59:30.84 +22:18:34.5 17.6mag C/2025 V2 (Rankin)
12:45:37.25 +03:48:37.6 17.1mag C/2025 Y1 (ATLAS)
16:43:46.51 +79:09:53.1 17.3mag C/2026 A2 (Bok)
02:49:20.93 +45:21:56.8 16.7mag C/2026 B2 (Sun-Gao)
11:27:23.88 +05:03:31.0 17.0mag A/2026 E1
21:23:38.02 -16:08:40.2 7.2mag 10P/Tempel
11:14:50.54 -02:00:51.0 16.2mag 29P/Schwassmann-Wachmann
04:04:23.82 +29:52:16.7 17.9mag 47P/Ashbrook-Jackson
10:14:12.45 +13:04:29.5 17.0mag 63P/Wild
00:49:36.23 -05:03:46.5 15.5mag 65P/Gunn
04:34:29.87 +20:19:33.4 13.7mag 78P/Gehrels
02:27:03.18 +11:00:38.7 16.3mag 88P/Howell
06:44:15.16 +30:21:16.5 15.7mag 93P/Lovas
04:30:32.79 +31:14:06.5 16.8mag 114P/Wiseman-Skiff
08:15:52.25 +30:22:20.7 15.2mag 123P/West-Hartley
10:53:36.88 -00:00:24.6 16.8mag 124P/Mrkos
04:56:26.56 +20:53:41.3 16.2mag 128P/Shoemaker-Holt
05:41:47.33 +19:41:16.9 17.8mag 131P/Mueller
00:02:18.74 +03:02:48.5 17.9mag 139P/Vaisala-Oterma
07:24:18.28 +16:22:54.0 15.9mag 141P-D/Machholz
03:18:03.57 -20:51:51.0 15.3mag 161P/Hartley-IRAS
05:43:38.70 +34:34:04.0 15.4mag 162P/SidingSpring
18:56:33.40 +16:56:08.0 14.5mag 169P/NEAT
01:48:01.18 +07:55:21.6 17.7mag 220P/McNaught
16:35:37.79 -08:30:18.4 17.1mag 235P/LINEAR
08:51:28.00 +33:01:35.7 17.9mag 240P/NEAT
20:40:51.13 -50:12:06.0 17.8mag 259P/Garradd
02:07:32.24 +13:28:06.6 15.6mag 260P/McNaught
05:46:08.52 +37:04:15.0 17.4mag 295P/LINEAR
15:06:29.50 +05:47:36.7 17.6mag 391P/Kowalski
08:37:14.56 +19:33:25.1 17.9mag 450P/LONEOS
07:56:22.41 +38:58:19.0 18.0mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.6K Jul 13 02:04 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
11:06:55.46 -04:07:04.50 AT2026qqg 2026-07-5.01 16.82
19:07:23.69 -74:13:37.30 AT2026qly 2026-07-5.02 17.31
17:57:43.80 +27:18:40.10 ASASSN-26ea 2026-07-5.07 16.67
19:59:01.43 -32:07:34.30 ASASSN-26eb 2026-07-4.97 15.52
18:46:50.35 -57:44:13.20 SN 2026qqp 2026-07-5.03 -0.92
19:17:31.69 -39:55:29.90 ASASSN-26dz 2026-07-5.14 15.91
19:14:31.37 +12:03:52.90 AT 2026rdg 2026-07-3.43 11.81
04:05:50.09 -70:24:34.40 AT 2026qpr 2026-06-30.4 15.96
13:45:37.49 -05:59:35.80 SN 2026pub 2026-06-30.09 16.01
16:41:15.63 +39:17:14.70 SN 2026pel 2026-06-26.38 16.07
10:14:40.19 -35:38:21.30 ASASSN-26dy 2026-06-25.99 15.63
14:47:21.56 -40:15:51.30 ASASSN-26dv 2026-06-23.03 14.62
13:38:49.79 -77:21:06.70 ASASSN-26dw 2026-06-23.04 16.09
00:59:27.90 +33:08:13.20 SN 2026mke 2026-06-22.39 17.13
11:10:44.73 -30:20:45.50 SN 2026nmv 2026-06-22.06 16.56
21:36:15.68 -21:19:12.50 AT2026oxh 2026-06-22.15 17.14
17:31:38.38 -56:05:51.90 ASASSN-26dx 2026-06-22.02 14.72
14:10:13.44 -38:46:46.10 AT2026pvk 2026-06-22.06 16.53
20:56:47.23 -18:31:05.20 AT2026plb 2026-06-21.31 16.4
15:44:29.68 +21:00:59.30 SN2026ore 2026-06-21.29 17.57
23:50:05.98 -14:01:41.30 AT2026oxl 2026-06-21.52 17.64
17:36:54.73 -18:10:04.20 AT2026ouj 2026-06-20.92 15.15
00:34:04.08 -30:22:09.20 AT2026ntk 2026-06-18.09 17.34
20:49:13.39 +25:17:59.20 ASASSN-26du 2026-06-15.39 15.93
23:09:30.84 +32:40:42.00 SN2026oxc 2026-06-14.35 16.83
02:02:26.78 +32:04:21.30 AT2026ovz 2026-06-14.59 15.39
21:26:28.11 -72:31:19.50 AT2026nwc 2026-06-11 17.05
17:54:57.33 +26:32:34.20 SN 2026odc 2026-06-11.23 17.62
13:55:59.94 +17:30:37.20 SN 2026nyq 2026-06-11.1 16.24
00:50:45.14 -71:38:36.90 ASASSN-26dt 2026-06-11.13 10.22
14:42:19.73 +19:11:35.60 SN2026nyp 2026-06-10.3 16.32
12:23:23.92 +12:56:43.50 SN2026mta 2026-06-8.29 16.69
12:30:18.51 +47:12:33.20 SN2026oao 2026-06-9.32 17.02
10:51:05.21 -42:28:56.60 AT2026nvf 2026-06-8.12 16.75
13:50:22.48 -07:35:00.00 SN2026npn 2026-06-8.02 17.58
00:56:07.17 +43:01:43.20 ASASSN-26dq 2026-06-7.43 13.58
01:07:49.46 +41:59:43.70 SN 2026obc 2026-06-7.43 15.15
21:11:25.22 +14:14:31.90 ASASSN-26dr 2026-06-7.24 16.24
06:21:27.06 -65:16:42.00 ASASSN-26ds 2026-06-2.97 15.02
20:07:38.15 -21:07:05.40 SN2026mho 2026-05-25.18 -1.12
11:29:42.55 +79:01:03.10 AT2026min 2026-05-24.21 16.63
11:44:33.11 -68:48:32.90 ASASSN-26no 2026-05-24.03 8.35
19:00:42.82 -48:31:01.60 ASASSN-26dp 2026-05-22.31 -3.28
14:23:56.72 -58:37:47.60 ASASSN-26dn 2026-05-20.01 14.64
11:24:54.06 +47:57:01.60 AT2026nma 2026-05-20.29 15.46
21:27:08.58 +33:24:38.10 AT2026lli 2026-05-19.34 15.86
00:31:01.41 -13:38:51.70 AT2026nad 2026-05-19.39 15.34
15:16:06.61 -79:16:32.40 ASASSN-26dm 2026-05-19.03 14.44
11:24:25.21 -59:23:19.10 ASASSN-26dl 2026-05-18.02 13.55
13:45:51.52 -53:16:01.00 ASASSN-26dk 2026-05-18.16 12.96
02:05:49.69 -30:29:09.60 ASASSN-26dh 2026-05-18.43 15.37
17:50:22.87 -39:42:33.90 ASASSN-26dj 2026-05-17.05 15.7
01:13:11.60 -33:25:16.10 ASASSN-26dg 2026-05-13.41 16.8
16:44:31.77 -27:15:18.40 AT2026mhn 2026-05-12.33 15.8
09:46:31.08 -33:41:51.00 ASASSN-26di 2026-05-12.14 14.63
21:23:11.57 -19:09:45.00 AT2026kwu 2026-05-12.26 16.9
14:20:14.30 -30:20:51.90 AT2026ktm 2026-05-12.06 17.21
14:41:39.01 -37:13:46.40 AT2026lkm 2026-05-11.18 16.89
12:59:50.45 -10:58:38.80 SN2026kep 2026-05-9.06 17.5
13:37:29.61 -29:50:30.90 AT2026lkd 2026-05-9.09 17.23
09:46:42.01 -14:52:03.60 SN2026kmo 2026-05-8.99 17.51
15:03:05.28 +22:02:03.80 AT2026lxf 2026-05-8.34 13.72
10:23:49.41 -20:57:25.30 ASASSN-26df 2026-05-8.21 16.52
22:14:40.56 +05:04:51.60 2026lda 2026-05-7.56 16.2
21:35:33.81 -14:05:16.30 ASASSN-26de 2026-05-6.29 14.51
16:21:48.82 -61:36:13.20 ASASSN-26dd 2026-05-5.21 15.15
14:26:40.22 -24:48:37.50 AT2026lig 2026-05-4.27 14.63
13:17:51.04 +30:25:13.50 SN2026kcp 2026-05-4.46 16.43
11:27:55.57 -13:38:56.90 SN2026kza 2026-05-1.08 15.59
22:28:27.10 +30:17:54.30 SN 2026fov 2026-04-29.6 14.36
21:00:10.71 -32:17:03.90 AT2026kis 2026-04-27.36 16.15
14:32:57.37 -58:13:26.40 ASASSN-26dc 2026-04-27.27 13.42
15:32:05.35 -43:54:34.60 ASASSN-26db 2026-04-27.37 16.06
16:34:34.97 -54:34:58.00 ASASSN-26da 2026-04-25.32 16.11
10:06:55.04 -01:13:49.70 SN2026jsg 2026-04-24.99 16.28
15:15:57.17 +56:18:32.80 SN2026kid 2026-04-24.52 -3.65
07:58:28.45 +57:03:42.40 AT2026kcf 2026-04-24.2 16.89
11:38:21.80 -50:43:06.50 SN2026jkb 2026-04-24.24 15.38
10:06:11.41 -39:41:04.20 AT2026dil 2026-04-24.2 16.85
14:21:40.08 +13:13:46.30 SN2026jlm 2026-04-22.16 15.12
10:53:55.47 -16:06:07.00 ASASSN-26cz 2026-04-22.24 16.32
11:06:55.46 -04:07:04.50 2026-07-5.01 16.82
13:45:02.03 +15:17:14.50 ASASSN-26cy 2026-04-21.27 15.78
13:20:52.22 -35:57:03.60 AT2026jcm 2026-04-19.01 16.65
13:36:15.66 -36:53:48.40 SN 2026iqy 2026-04-18.92 17.31
06:34:01.33 -40:07:34.00 ASASSN-26cx 2026-04-19.07 16.16
23:33:57.97 -45:12:11.90 SN 2026idu 2026-04-19.41 15.9
12:10:50.92 +66:55:31.20 SN 2026icv 2026-04-17.14 16.03
21:36:59.06 -60:43:35.90 ASASSN-26cv 2026-04-17.35 -1.18
08:13:26.26 -27:07:30.50 ASASSN-26cw 2026-04-17.07 -1.01
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
11:06:55.46 -04:07:04.50 2026-07-5.01 16.82
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
-rw-r--r-- 1 apache apache 5.6K Jul 13 02:04 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
00:43:35.02 +41:46:28.0 PNV J00433502+4146280 2026-04-23.056 15.9mag
00:42:55.64 +41:14:12.2 PNV J00425564+4114122 2026-04-24.042 16.2mag
21:14:03.38 +56:46:44.1 TCP J21140338+5646441 2026-05-05.3534 16.7mag
15:03:05.19 +22:02:04.1 TCP J15030519+2202041 2026-05-08.3260 13.9mag
07:15:18.25 +47:53:16.7 TCP J07151825+4753167 2026-05-09.1599 14.4mag
16:00:18.44 -22:30:10.6 TCP J16001844-2230106 2026-05-09.6135 13.3mag
00:42:47.45 +41:16:58.5 PNV J00424745+4116585 2026-05-10.030 16.8mag
09:55:02.89 +69:02:13.8 PNV J09550289+6902138 2026-05-18.925 20.7mag
00:43:01.82 +41:18:16.6 PNV J00430182+4118166 2026-05-21.8651 18.83Cmag
00:42:51.20 +41:16:59.4 PNV J00425120+4116594 2022-10-26.135 19.3mag
12:24:25.10 +28:47:12.0 TCP J12242510+2847120 2026-05-31.6015 14.8mag
00:56:07.13 +43:01:40.6 TCP J00560713+4301406 2026-06-01.4135 12.2mag
00:42:41.64 +41:15:16.2 PNV J00424164+4115162 2026-06-02.029 17.4mag
00:42:38.68 +41:15:58.2 PNV J00423868+4115582 2026-06-05.1224 19.97Umag
19:00:42.95 -48:31:01.7 PNV J19004295-4831017 2026-05-25.0752 14.2mag
09:55:21.28 +69:02:52.6 PNV J09552128+6902526 2026-06-13.933 18.9mag
19:51:21.42 +37:06:40.0 TCP J19512142+3706400 2026-06-17.2942 16.8mag
19:57:03.87 +37:41:46.4 TCP J19570387+3741464 2026-06-18.2638 17.5mag
00:42:32.04 +41:10:28.3 PNV J00423204+4110283 2026-06-26.059 16.6mag
02:19:17.36 +28:57:15.8 TCP J02191736+2857158 2026-07-12.3549 12.5mag
-rw-r--r-- 1 apache apache 189K Jul 13 02:04 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
18:34:53.747 +37:29:26.70 AT 2026ton 2026-05-20.52 21.07
08:35:53.580 +06:18:21.24 AT 2026tom 2026-03-09.32 21.34
12:31:07.347 -01:35:38.60 AT 2026tol 2026-04-22.35 21.29
15:40:49.500 +03:40:01.11 AT 2026tok 2026-07-09.29 19.19
13:28:58.224 -31:39:58.70 AT 2026toj 2026-01-27.63 20.99
16:19:43.736 +12:53:16.12 AT 2026toi 2026-06-19.41 20.78
12:16:00.811 +13:52:30.28 AT 2026toh 2026-06-05.33 21.31
08:05:33.164 +19:53:59.86 AT 2026tog 2026-05-05.27 21.02
22:22:27.296 -01:16:48.01 AT 2026tof 2026-06-20.59 21.53
18:21:21.782 +34:34:12.08 AT 2026toe 2026-06-06.57 20.8
09:23:56.056 +15:48:10.98 AT 2026tod 2026-03-09.25 20.93
14:30:53.211 +02:37:48.55 AT 2026toc 2026-02-24.60 21.68
18:53:53.654 +37:31:27.95 AT 2026tob 2026-06-06.57 20.33
14:02:45.983 +27:31:29.38 AT 2026toa 2026-01-13.59 21.55
11:45:46.289 -15:58:14.20 AT 2026tnz 2026-04-19.34 21.32
17:01:06.389 +36:02:56.61 AT 2026tny 2026-06-22.29 20.16
14:21:15.460 +00:01:06.82 AT 2026tnx 2026-05-17.42 21.17
16:56:29.803 +29:23:52.18 AT 2026tnw 2026-06-06.48 20.57
13:19:42.648 +33:06:54.64 AT 2026tnv 2026-05-13.26 20.86
11:42:50.112 -20:30:52.08 AT 2026tnu 2026-02-14.47 20.76
-rw-r--r-- 1 apache apache 30K Jul 13 02:04 tns_transients_list.txt
